Certain requirements apply when implementing a snapshot solution with a VCS, Microsoft clustering, and Volume Replicator environment.
The XML metadata file for each snapshot set along with files that store snapshot schedule information are created in a folder on the local drive by default. In a cluster environment, store these files on shared storage so that the files are available from all nodes in the cluster.
If you use the Quick Recovery Configuration Wizard or the VSS SQL Snapshot Wizard to create the snapshot set, you can use either wizard to specify the file path to the appropriate volume.
Use either the Quick Recovery Configuration Wizard or the VSS SQL Snapshot Wizard to create the snapshot set. After creating the snapshot set, you can store the XML files in a location of your choice using either the Quick Recovery Configuration Wizard which provides an option for specifying the path (by modifying the default populated path) or by the following method: Use a text editor to create a text file named "
redirect.txt." This text file should contain a single text line specifying the Universal Naming Convention (UNC) path to the location of the metadata file, for example,
\\ServerName\SharedFolderName. Save the
redirect.txt file in the default VSS XML file directory
C:\Program Files\Veritas\Veritas Volume Manager\VSSXML on each node of the cluster.
When using vxsnap utility commands that require the filename attribute, specify the full path to the location of the XML metadata file.
If you plan to use the Quick Recovery or VSS Snapshot Scheduler wizard to specify scripts (commands) to be run before or after a snapshot, store the scripts on shared storage so that they are available to all nodes.
If you set up a snapshot schedule with the Quick Recovery wizard and later add a node to the cluster, you can run the wizard again to synchronize schedules on the existing nodes with the new node.
In a Volume Replicator environment, observe the following precautions:
Store the XML metadata file and other snapshot related files on a volume that is included in the replicated data set so that the metadata file is available at the secondary site. Additionally, if VCS is used, store the metadata file on a volume in the cluster disk group associated with the database so that the metadata file is available from all nodes in the cluster.
During a point-in-time recovery, the volumes on the secondary site lose write-order fidelity. DCM automatically becomes active to ensure data consistency between the primary and secondary sites. While DCM is active, the volumes cannot be expanded by either manual or AutoGrow operations. You must perform a manual resynchronization of the secondary to deactivate DCM.