Volume Replicator 7.4.2 Administrator's Guide - Windows
- Understanding Volume Replicator
- About Volume Replicator
- Basic Volume Replicator terms
- Building blocks of Volume Replicator
- Understanding replication in the Volume Replicator environment
- Modes of replication
- Understanding data flow in Volume Replicator asynchronous mode
- Managing data during failure and recovery
- Replication concepts
- About using Volume Replicator as a disaster recovery tool
- Understanding how Volume Replicator logs writes to the Replicator Log
- Understanding replication settings for a Secondary
- Measures to protect log overflow and replication latency
- Pausing the replication
- Synchronizing the Secondary
- Understanding Volume Replicator support for FlashSnap
- About Synchronized Snapshots
- Understanding Bunker replication
- Understanding Volume Replicator Support for TCP Multi-Connection
- About Volume Replicator memory monitoring and control support
- About Volume Replicator Graphs
- Setting up replication
- Security considerations for Volume Replicator
- Setting up replication using the Setup Replicated Data Set wizard
- Setting up the Bunker RVG for replication
- Using the VEA Console for Volume Replication Operations
- Monitoring replication
- Interpreting the information in the Volume Replicator views
- Monitoring replication using the VEA console
- Checking replication performance using vxrlink stats
- Administering Volume Replicator
- Adding volumes
- Administering the RVG
- Administering replication
- Managing checkpoints
- Pausing replication using Volume Replicator
- Creating snapshots for the data volumes
- Creating synchronized snapshots using the VSS Snapshot wizard
- Administering Bunker replication
- Performing disaster recovery operation
- Deleting Volume Replicator objects
- Accessing data on Secondary host
- Performing automated system recovery (ASR)
- Alternative methods to synchronize the Secondary faster
- Obtaining statistical information through Volume Replicator Graphs
- Using the command line interface
- Administering the RDS using the vxrds command
- Resizing the data volumes
- Displaying the network statistics for the RLINK
- Administering the RVGs using the vxrvg command
- Displaying information using the vxprint command
- Creating snapshots using the vxsnap command
- Administering replicated volumes using the vxvol command
- Displaying and changing replication ports using the vrport command
- Administering the RVG using the vxedit
- Administering the RVG using the vxassist command
- Tuning Volume Replicator
- Examples: Using the command line
- Example 1: Setting up replication using the command line interface
- Example 3: Using Bunker node for disaster recovery
- Example 4: Using synchronized snapshots to restore data
- Configuring Volume Replicator in a VCS environment
- Components of a VCS cluster
- Illustrating a highly available Volume Replicator setup
- How the agents work
- Configuring the agents
- Working with existing replication service groups
- Configuring Volume Replicator with Hyper-V
- Advanced settings in Volume Replicator
- Troubleshooting Volume Replicator
- Recommendations and checks
- Recovering from problems in a firewall or NAT setup
- Recovering from problems during replication
- Error when configuring the VxSAS Service
- Operation time-out errors
- Problems when configuring Volume Replicator in a VCS environment
- Problems when setting performance counters
- Appendix A. Services and ports
- Appendix B. Using the vxrsync utility
- Appendix C. VR Advisor (VRAdvisor)
Creating Synchronized Snapshots
The vxsnap create command creates snapshots of all volumes in the Exchange storage group or the SQL database components on the Primary and Secondary hosts, at the same point of data consistency. You can specify a name of your choice for the xml file that stores the snapshot metadata. If nothing is specified, then the snapshot is named according to a default naming convention.
Warning:
If you have created the RVG on the Primary and Secondary using the vxrvg command and created the RLINKs using the vxrlink command, then you must ensure that the RVG, disk group names, and volume names are the same before creating the RLINK. Having different component names can cause the snapshot command to fail.
Note:
Separate the source volumes and attributes with forward slashes, not spaces. Source and snapshot volume attributes are paired. You must specify the source volume if you choose to specify the snapshot volume plex, drive letter, drive path, label, or volume name.
Syntax for vxsnap create command
vxsnap -x <filename> create source=<volume> [/DriveLetter=<driveLetter>][/DrivePath=<drivePath> [/Label=<volLabel>][/Newvol=<newVolName>][/Plex=<plexName>] ...[ writer=<writerName>] [component=<componentName>][backuptype=<backuptype>] [-E] [-O] [secHosts=<Secondary hosts>]
The following table lists the output parameters of the vxsnap create command.
Table: Output parameters for the vxsnap command
Parameter | Description |
---|---|
-x <Filename> | Indicates the name to be assigned to the XML metadata file that the vxsnap create command creates. The file name must include the ".xml" extension. By default, the file is stored at: C:\Documents and Settings\All Users\Application Data\Veritas\VxSnapExchangeBackup If you want to place the file in another directory, specify a full path before the file name, for example J:\XML\Image1.xml. |
-E | Runs the Eseutil consistency check for the Exchange database and log files. Eseutil is run automatically with a full backup, but must be optionally specified for a copy backup. |
-o | Allows an existing XML file of the same name to be overwritten. If -O is not specified the vxsnap create command does not overwrite an existing XML file of the same name and the operation fails. |