Volume Replicator 7.4.1 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)
Best practices for setting up replication
Certain best practices can be used when setting up replication.
Note:
The Volume Replicator Advisor (VRAdvisor), a tool to collect and analyze samples of data, can help you determine the optimal size of the Replicator Log.
Some best practices regarding setting up replication are as follows:
Create the Primary data volumes with drive letters. Plan the size and layout of the data volumes based on the requirement of your application. You must configure the Primary and Secondary data volumes with the same name.
If you create the Replicator Log volume manually, then make sure that you do not assign a drive letter to the Replicator Log volume. Veritas recommends that you create the Replicator Log volume as a mirrored volume. For better performance, Replicator Log should be a mirrored-striped volume.
To improve write performance configure the data volumes and the Replicator Log volume on different physical disks.
Veritas recommends that you create a Replicator Log volume of the same size on the Primary and Secondary. Size the Replicator Log appropriately to avoid overflow.
As Volume Replicator uses Replicator Log volumes, Veritas recommends that you do not format these volumes with any file system. When a volume is assigned for use as a Replicator Log volume, the existing file system and data is lost.
Plan the bandwidth of the network to be used, based on your requirement.
If you plan to replicate data over cloud, ensure that you satisfy the following network requirements to establish connectivity between the on-premises and cloud networks, or in between the same or different cloud regions:
A non-overlapping IP address space for network subnets is available on the primary and the secondary datacenters.
A virtual network (VNet) is set up in Microsoft Azure network.
The Volume Replicator
tunable is set to True. This tunable determines whether or not DHCP IPs can be used while configuring Volume Replicator.DHCP IP addressess are assigned to the virtual machines that are created in an Azure environment. To identify the DHCP IP addresses, DHCP_IP tunable must be set to True.
Run the following command line to enable the tunable:
vxtune dhcp_ip_support true
To set up replication from an on-premises datacenter to a cloud datacenter, a virtual private network (VPN) gateway and a local network gateway is set up in the cloud network. This enables to set up a communication tunnel between the machines that are located in the on-premises datacenter to the machines that are located in the cloud datacenter.
Alternatively, you may configure Microsoft ExpressRoute to establish a connection between datacenters.
For more details refer to Microsoft documentation.
To set up replication between any two regions on cloud, a virtual private network (VPN) gateway is set up over the virtual network, and a connection is established between the VPN gateways for the virtual machines to communicate with each other.
To set up replication within a same region on cloud, a VNet Peering is set up between the two virtual networks in which the machines are configured.
Alternatively, you may set up a VPN gateway between the two virtual networks.
Note:
While provisioning storage for setting up replication in Microsoft Azure environment, do not configure multiple network paths to the storage disks. Microsoft Azure does not support storage configuration with multiple network paths.
You can choose to use either the UDP, TCP, or STORAGE protocol for network communication between the Primary and Secondary during replication. You can use the STORAGE protocol only for a Bunker Secondary if the storage on the Bunker Secondary is visible from the Primary host.
Make sure that the Secondary volumes are not formatted and no other application uses these volumes. If you use these volumes for replication, all the original data on these volumes is lost.
Avoid using RDS and RVG names with special characters with the exception of the hyphen (-) or an underscore (_). The names can have a maximum of 31 characters and can begin with a hyphen (-) or underscore (_) character.
If you want to replicate encapsulated volumes, ensure that the volume names and sizes on the Secondary are the same as the corresponding volume names and sizes on the Primary. The volume name is auto generated while encapsulating the volume.
Enable the ports and services that are used for inbound and outbound communication.
For a list of required ports and services,