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 snapshots using the vxsnap command
The vxsnap command can be used to create synchronized snapshots on the Primary and Secondary. These snapshots can be very useful in recovering data to a consistent data point on the Secondary if the data is corrupt and the Primary had a disaster. This section focuses on how you can use the vxsnap command options for creating synchronized snapshots.
For any additional information about the vxsnap command and the other options available with this command, see Storage Foundation Administrator's Guide Chapter "Command Line Interface".
The following table lists the vxsnap command keywords and related descriptions.
Table: Keywords for the vxsnap command
Keywords | Description |
---|---|
prepare | Creates the snapshot mirrors of the volumes in the specified component. The component in consideration is the Exchange storage group. The snapshot mirrors remain attached to and synchronized with the original volumes. Note: Either the prepare or snapstart keyword may be used in the CLI, however prepare is recommended. |
create | Creates simultaneous snapshots of all the volumes in the specified Exchange storage group component on the Primary, with simultaneous synchronized snapshots on the Secondary providing a point-in-time and up-to-date snapshot set. This parameter must be used with the sechosts parameter for creating synchronized snapshots. |
reattach | Reattaches and resynchronizes an existing snapshot set to the original database volumes. |
The following table lists the vxsnap command attributes.
Table: Attributes for the vxsnap command
Attributes | Description |
---|---|
component=<ComponentName> | Name of the component; for Exchange, this is the storage group name found in the Exchange System Manager, for example, "First Storage Group". |
writer=<WriterName> | Unique ID of the VSS writer, for example, in Exchange this is, "Microsoft Exchange Writer". |
source=<Volume> | Indicates the source volume for the snapshot mirror that is specified by a drive letter, drive path (mount point), or volume name of the form "device\harddiskDMVolumes\DynamicGroup\volume1". Repeat this parameter for each volume that is associated with the specified component (for example, Exchange storage group). |
sechost=<sec host list> | Specifies a comma-separated list of Secondary host names on which you want to create synchronized snapshots. |
harddisk=<Harddisk> | Name of the disk where the mirror is to be created, for example, harddisk2. |
[/plex=<PlexName>] | Specifies the name of the mirror or plex that is to be detached. Use this parameter if there are multiple snap plexes for which you need to create snapshots. |
[/DriveLetter=<DriveLetter>] | Specifies the drive letter to be assigned to the new snapshot volume. |
[/DrivePath=<DrivePath>] | Specifies the drive path to be assigned to the new snapshot volume. The drive path must reference an empty local NTFS folder, which was created beforehand. The path must include the drive letter and folder to be mounted, for example, C:\DB1VOL. |
[/Label=<VolLabel>] | Volume label that can be assigned to new snapshot volume. |
[/Newvol=<NewVolName>] | Specifies the name for the new snapshot volume that is to be created. If no name is specified using this option, then a snapshot with the default naming format "SnapVolume01" is created. The full device path then becomes: \Device\HarddiskDmVolumes\<DiskGroupName>\<NewVolName> |
backuptype=<Backuptype> | Specifies the type of backup, either a Full or Copy. If no option is specified then Copy is the default. Copy backup creates a copy of the database and transaction logs volumes. Full backup creates a copy of the database and transaction logs volumes, runs Eseutil to check for consistency. If the copy is consistent, Full backup truncates the transaction logs. |