Volume Replicator 7.4 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
- Setting up replication in cloud environments
- 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)
Setting up replication within same Azure region
In an Azure cloud environment, in a single region, you can provision your setup across virtual networks (VNets) or within a VNet.
The following diagram illustrates the sample configuration for setting up replication between the same VNet:
The following diagram illustrates the sample configuration for setting up replication across VNets:
Perform the following steps to set up replication in the same VNet, within the same region
- Enable the ports that are used for inbound and outbound communication.
- Using Microsoft Azure portal, create a VNet and specify an IP address space for the VNet.
- Create a subnet in the VNet created.
For details about creating a VNet, specifying an IP address space, and creating a subnet, refer to Microsoft documentation.
- Create two virtual machines within the subnets and provision storage.
- Install InfoScale Storage/InfoScale Enterprise on both the virtual machines.
- Create VxVM disk groups, VxVM volumes, Storage Replicator Log (SRL), Replicated Volume Group (RVG), and RLinks.
- Flush the iptables on both the virtual machines.
# iptable -F
- Set up replication between the virtual machines using the private IP address or the virtual IP address.
- Verify the replication status.
# vradmin -g dg_name repstatus rvg_name
Ensure that the replication status shows:
Replication status: replicating (connected)
Perform the following steps to set up replication across the VNets, within the same region
- Using Microsoft Azure portal, create two VNets and specify an IP address space for each VNet.
- Set up VNet Peering between the two VNets.
- Create a subnet in each VNet.
- Create a virtual machine in each subnet and provision storage.
- Install InfoScale Storage/InfoScale Enterprise on both the virtual machines.
- Create VxVM disk groups, VxVM volumes, Storage Replicator Log (SRL), Replicated Volume Group (RVG), and RLinks.
- Flush the iptables on both the virtual machines.
# iptable -F
- Set up replication between the virtual machines using the private IP address or the virtual IP address.
- Verify the replication status.
# vradmin -g dg_name repstatus rvg_name
Ensure that the replication status shows:
Replication status: replicating (connected)