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)
About Volume Replicator support for IPv6 and dual stack
Volume Replicator includes support for IPv6 addresses. When you configure replication, you can specify IPv6 addresses for the primary and the secondary systems. You can also configure replication with system that have both IPv4 and IPv6 (dual stack) enabled.
Note the following:
Verify whether the IP version preference is set before you configure replication.
If you specify host names when you configure replication, Volume Replicator resolves the host names with the IP addresses associated with them. This setting determines which IP version Volume Replicator uses to resolve the host names.
Use one of the following methods to set the IP preference:
Veritas Enterprise Administrator (VEA) GUI - select the appropriate options on the Control Panel > VVR Configuration > IP Settings tab.
Run the vxtune ip_mode [ipv4 | ipv6] command at the primary site as well as the secondary site.
Using the Replicated Data Set (RDS) wizard, you can specify IPv6 addresses that are associated with the Primary and Secondary host names.
Using the VVR Security Service Configuration Wizard, you can specify IPv6 addresses for hosts on which you want to configure the VxSAS service.
Volume Replicator commands that use an IP address, either as an input parameter or as an output, now support IPv6 addresses.
For example, the vxrds changeip command that is used to change the host name or IP address of the Primary or Secondary RLINKs now accepts IPv6 addresses as input.
Volume Replicator does not support replication in cases where the Primary and Secondary systems in an RDS use different IP addresses. For example, if the Primary host uses an IPv4 address and the Secondary host uses an IPv6 address, this configuration is not supported.
In cases where the Primary host uses only an IPv4 address, and the Secondary host uses both IPv4 and IPv6 addresses, Volume Replicator automatically selects an IPv4 address for the Secondary.
You can configure Volume Replicator in one of the following combinations based on the IP family:
Primary | Secondary |
---|---|
IPv4 | IPv4 |
IPv6 | IPv6 |
Dual stack | Dual stack |
IPv4 | Dual stack |
IPv6 | Dual stack |
Dual stack | IPv4 |
Dual stack | IPv6 |
Note that the communication happens between the IPs of same family.
The vxrlink command works only if the primary and the secondary nodes have the same IP configuration - IPv4, IPv6, or dual stack. The GUI equivalent of this command is the Change Replication Settings dialog box, and the same limitation also applies to the operations that you can perform with the GUI.
In a dual-stack configuration, if the active network fails, the failover does not take place automatically. Perform the following tasks to trigger the failover manually:
Make sure that all the nodes are configured with the available network. For example, if the IPv6 network fails, configure IPv4 on all the nodes.
Set the new IP addresses or host names that you want to use for replication. To do so, follow the steps to upgrade the network.
See Migrating VVR to support IPv6 or dual stack.
For example, if the IPv6 network fails, perform these tasks to set the IPv4 addresses or host names for replication.