Veritas™ File System Programmer's Reference Guide - Solaris
- Veritas File System software developer's kit
- File Change Log
- About the File Change Log file
- Record types
- File Change Log tunables
- Application programming interface for File Change Log
- API functions
- File Change Log record
- Copying File Change Log records
- Veritas File System and File Change Log upgrade and downgrade
- Reverse path name lookup
- Multi-volume support
- Named data streams
- Veritas File System I/O
- Caching advisories
- Extents
- Thin Reclamation
Off host processing
In some scenarios, a user application may choose to save the bandwidth of the actual production server and outsource the job of processing the FCL to a different system. For off-host processing, the FCL file needs to be shipped to the off-host system. Since the FCL file is not a regular file, a command such as cp or ftp does not work.
To be "shippable," the FCL file must first be dumped into a regular file using the fcladm dump command. The file can then be sent to the off-host system using normal file transfer programs. See the following example.
$ fcladm -s savefile dump mount_point$ rcp savefile offhost-path
On the off-host system, the FCL file must be then restored using the restore option through the fcladm command. Unlike the original FCL file, the restored file is a regular file.
$ fcladm -s savefile restore restorefile
The restored FCL file can be passed as an argument to vxfs_fcl_open for further use with the FCL API.
Warning:
The reverse name lookup API does not work on the off-host system. The off-host processing mechanism should only be used when the application can work with the inode number and generation count, or when it has an independent method to determine the filenames from the inode number.