Filesnap service usage using the vxsfadm utility.

vxsfadm -s filesnap -a <application-name> [ <options> ] -o <operation>

 Options are:

 [ -c <config-file> ]
 [ -r <Respository-host> ]
 [ --filesnap-name=<value> | --name=<value>]
 [ --clone-name=<value> ]
 [ <Other application specific options> ]

For application specific options, please see the application specific man pages for filesnap.

The filesnap service can be used to create point-in-time copies/ snapshots of an application using VxFS file-level snapshots. A filesnap snapshot can then be used to create multiple application clones or serve to restore the application files from the snapshot.

Below is an explanation of the generic configuration parameters supported by the filesnap service. Application specific configuration parameters are documented in the vxsfadm-oracle-filesnap(1M) man page. Configuration parameters may be specified in one of three ways:

1. On the command line.
2. In a configuration file.
3. In the environment.

Parameters provided on the command line take precedence over those in the configuration file or in the environment. Parameters provided in the configuration file take precedence over those in the environment.

FILESNAP_NAME | FILESNAP-NAME | NAME	This is the name of the filesnap snapshot to be created. The snapshot is stored in the same namespace as the application files inside a hidden directory. For example, if the path for a file is ’/oradata/mydb/users01.dbf’, and the snapshot is called snap1, then the file snapshot is stored at ’/oradata/mydb/.dbed_snapshots/snap1/users01.dbf’. This is a mandatory parameter.
CLONE_NAME | CLONE-NAME	This is the name of the application clone to be created. The application clone is a replica of the original application and its data, but has a different identity. A clone may be directly created along with a new snapshot or may be created from an existing snapshot. Multiple clones may be created from a single snapshot.

list	This operation lists the snapshots/ clones for an application taken using the Filesnap service. Example: vxsfadm -s filesnap -a oracle --oracle-sid=mydb -o list
snap	This operation creates a filesnap snapshot for the application specified. Currently, only Oracle is supported. Example: vxsfadm -s filesnap --filesnap-name=snap1 -a oracle --oracle-sid=mydb -o snap
destroysnap	This operation deletes the specified snapshot. Before a snapshot can be destroyed, all application clones based on the snapshot must be destroyed. Example: vxsfadm -s filesnap --filesnap-name=snap1 -a oracle --oracle-sid=mydb -o destroysnap
clone	This operation clones the application. The clone application identity must be specified with the --clone-name parameter. Multiple clones can be created from a single snapshot. Example: vxsfadm -s filesnap --filesnap-name=snap1 -a oracle --oracle-sid=mydb --clone_name=clone1 -o clone
destroyclone	This operation deletes the specified clone. Example: vxsfadm -s filesnap --filesnap-name=snap1 -a oracle --oracle-sid=mydb --clone-name=clone1 -o destroyclone
restore	This operation can be used to restore the application files from the snapshot. As an extra caution, this operation requires that the application be manually shut down before the restore is performed. This operation only restores the application files but does not do any application-level recovery. Any application-level recovery needs to be done manually. Example: vxsfadm -s filesnap --filesnap-name=snap1 -a oracle --oracle-sid=mydb -o restore

vxsfadm(1M), vxsfadm-oracle(1M), vxsfadm-oracle-filesnap(1M)

vxsfadm-flashsnap(1M), vxsfadm-sos(1M), vxsfadm-checkpoint(1M) vxsfadm-oracle-flashsnap(1M), vxsfadm-oracle-sos(1M), vxsfadm-oracle-checkpoint(1M)