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)
Starting replication using the vxrds startrep command
Use the vxrds startrep to start the replication to the normal or Bunker Secondary host in the RDS, to which the RVG belongs. The sec_host parameter is the name of the Secondary host that is displayed in the output of the vxrds printrvg command.
The startrep command attaches the Secondary host to the Primary to establish a communication link and start replication.
If the Primary becomes unavailable due to a disaster, then use the
vxrds startrep command with the -b option to start replication from the Bunker Primary to the Secondary. In this scenario the vxrds startrep command also switches the RLINKs to point to the Bunker Primary instead of the original Primary.
Syntax for vxrds startrep command
vxrds [-g <diskgroup>] -c <checkpoint>| -f | -forceatt |-autosync| |-a|-b startrep <local_rvg> <sec_host>
Example
vxrds -g vvrdg -forceatt startrep rvg sec_host
The following table describes the attributes that you can specify with the vxrds startrep command.
Table: Attributes for vxrds startrep command
Option | Description |
---|---|
-autosync or -a | Use this option to automatically synchronize the Secondary data volumes. |
-b <startrep> | Use this option to replay pending updates from Bunker Primary to Secondary. |
-c <checkpoint> | Use this option to attach the Secondary to the Primary with the specified checkpoint Note: This option is not supported when synchronizing a Bunker RVG with the Primary RVG. |
-forceatt or -f | Use this option to start replication if the Secondary data volumes contain exactly the same data as the Primary data volumes and therefore there is no need to synchronize the Secondary data volumes. If the data volumes are not synchronized then the -f option can cause data corruption as replication is started immediately and the Secondary may miss the writes that may have been present on the Replicator Log but did not reach the Secondary. Because there is no way of knowing whether the Replicator Log had some pending writes that have not yet been sent to the Secondary, use this option only if you know that the Secondary is completely up-to-date. Note: This option is not supported when synchronizing a Bunker RVG with the Primary RVG. |
These attributes are mutually exclusive and only one of these options can be used with the startrep command. The function of these options is similar to the function of the same options available with the vxrlink att command.