vxsfadm - Generic Utility which does various point in time copy operation for various applications using storage foundation features.

vxsfadm -s <service_type> -a <application-name> -o <operation>
[ -c config-file ]
[ -r Repository-host ]
[ service specific parameters ]
[ application specific parameters ]

vxsfadm [-s <service-type>] -a application-name> -o list
[ service specific parameters ]
[ application specific parameters ]

vxsfadm -s <service-type> -a application-name> -o setdefaults
[ service specific parameters ]
[ application specific parameters ]

vxsfadm is a single cli to execute the various point in time copy operation. Currently vxsfadm supports various services types such as flashsnap,filesnap,so snapshots,checkpoints. Currently supported application is oracle database. The utility works for multiple database configurations viz. single instance, High Available (VCS cluster), RAC configuration , dataguard and VVR configuration.

Following are the command line options for vxsfadm

-s Service_Type	Specifies service type for the operation. Supported service types are FileSnap - File level snapshots. Flashsnap - Volume level Snapshots. SOS - Space optimized volume level snapshots. Checkpoint - Filesystem checkpoints. This is a mandatory option.
-a Application-Name	Specifies the application for which point in time services should be used. Currently supported applications are Oracle and DB2. This is a mandatory option.
-o Operation	Specifies operation to be performed for the service_type. Different service types support different operation types. Please check vxsfadm-<service_type> man page for more details. This is a mandatory option. -o list List all the configurations/services for the specified application. If <service_type> is specified then all existing configurations for the specified <service_type> are displayed -o setdefaults Generates the default configuration which can be saved to a file, that can be used remainder of the operations
-c Configuration-File	All the command line options, specific to applications, apart from service_type, application_name and operations can be provided in Configuration file. Information in the configuration file should be in format <PARAMETER_NAME>=<VALUE>. Information about supported parameters are described in man pages for appropriate service types. This parameter is optional, if the application and service key is provided in command line.
<service specific parameters >	Service parameters are the parameters needed by the service for processing. The important and mandatory parameter all service is --<service>_name or simply --name. <service>_name parameter uniquely identifies the point in time copy for the application. For e.g. If a user wants to create a 3rd mirror breakoff type snapshot(flashsnap), service key parameter would be flashsnap_name=dailysnap or flashsnap_name=hourlysnap. This would create a unique identifier for a that copy which should be used for all operations on it. The service parameters can be entered in configuration file as <parameter>=<value> or on the command line as --<parameter> value or the same can be set in the environment. For more details please refer examples in man pages for services.
<application specific parameters >	Simmilar to service parameters the application parameters are the parameters needed by the application for processing. The important and mandatory parameter for teh application would be the one which uniquily identifieds the application. For e.g if there are two oracle databases running on the system, the oracle_sid and oracle_home parameters would uniquily identify teh oracle instance. This parameter should be used for all the point in time operation for specific application instance. The application parameters can be entered in the configuration file or on command line or the same can be set in the environment.For more details please refer examples in man pages for services.

By default all the logs are generated in /var/vx/vxdba/logs directory on the host where the command is executed. There are various log levels which can be set for better trouble shooting in case of any problem. Log levels can be set exporting environment variable SFAE_LOG_LEVEL before executing the command . Following log levels are supported

 export SFAE_LOG_LEVEL=DEBUG
 export SFAE_LOG_LEVEL=ERROR
 export SFAE_LOG_LEVEL=INFO
 export SFAE_LOG_LEVEL=WARN

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