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 from on-premise to Azure cloud
The following diagram illustrates the sample configuration for setting up replication between an on-premise data center to Azure cloud (on-cloud data center):
Note:
For the ease of use, the machines, whether virtual or physical are commonly mentioned as virtual machines. Your on-premise data center may include physical machines instead of the virtual machines. In any case, the steps to set up replication from on-premise data center to on-cloud data center remain the same for physical and well as virtual machines.
Figure: Sample configuration for setting up replication between an on-premise data center to on-cloud data center
Replication between an on-premise data center to on-cloud data center involves the following high-level steps:
Prepare the setup at on-premise data center
Prepare the setup at on-cloud data center
Establish a tunnel from on-premise data center to on-cloud data center
Deploy setup
The following sections provide details about performing each of these steps.
Perform the following steps to prepare the setup at on-premise data center:
- Enable the ports that are used for inbound and outbound communication.
- Create a subnet and a local VPN gateway.
- Note the address space that is allotted for the subnet and the public IP address that is allotted for the local VPN gateway.
Perform the following steps to prepare the setup at on-cloud data center:
- Using Microsoft Azure portal, create a resource group.
- Create a VNet in the resource group created and specify an IP address space for the VNet.
The IP address range must be diff on the on-premise subnet and on the on-cloud subnet.
- Create a gateway subnet.
- Create a VPN gateway and associate it with the created VNet.
Note the public IP address that is allotted for the on-cloud VPN gateway.
- Create a local network gateway.
When you create the local network gateway, you must provide the on-premise subnet IP address range and the public IP address of the on-premise local VPN gateway.
- Establish a tunnel from on-cloud to on-premise network.
To establish the tunnel, create a connection of type Site-to-Site (IPSec) and choose the on-cloud VPN gateway and the local network gateway.
- Provide a shared key (alpha-numeric key).
A shared key is a pass-phrase. This pass-phrase is required when you establish a tunnel from on-premise data center to cloud data center.
To establish a tunnel from on-premise data center to on-cloud data center, use the following parameters:
Public IP address that is allotted for the on-cloud VPN gateway
Shared key (alpha-numeric key) that was provided while establishing a tunnel from on-cloud data center to on-premise data center
On-cloud VPN gateway configuration type (Policy based or Route based)
Perform the following steps to deploy the setup (in both the data centers):
- Create virtual machines in the subnets created.
- Provision storage.
- Install InfoScale Storage/InfoScale Enterprise.
- Create VxVM disk groups, VxVM volumes, 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)