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 AWS cloud
In this scenario, data is replicated from an on-premise data center to an on-cloud data center.
You must meet the following requirements before setting up replication from an on-premise data center to an on-cloud data center.
Required ports are open for communication between an on-premise data center and an on-cloud data center.
The virtual private IP addresses are plumbed on both the nodes.
The virtual private IP addresses are configured within the subnets.
The following diagram illustrates a sample configuration for setting up replication from an on-premise data center to an on-cloud data center.
Perform the steps in the following procedure to set up replication from an on-premise to an on-cloud data center.
To set up replication from on-premise to on-cloud data centers
- Using AWS portal, create a Virtual Private Cloud (VPC) with a valid CIDR block, for example 10.239.0.0/16.
- Create a subnet in the VPC created and assign it to an Availability Zone.
- Create an EC2 instance and associate it with the VPC created.
- Configure a virtual private gateway and associate it to the VPC.
- Configure a gateway in the on-premise data center.
- Create route table entries.
- Associate the subnet with the route table.
- Enable route propagation to automatically propagate the routes to the table.
On the Route Propagation tab in the details pane, choose Edit, and select the virtual private gateway that you created.
- Create a VPN connection.
- Download the VPN configuration file.
- Create a VPN tunnel between the on-premise network and the on-cloud network.
- Install InfoScale Storage/InfoScale Enterprise on EC2 instances in both the data centers
- Create VxVM disk groups, VxVM volumes, Replicated Volume Group (RVG), and RLinks.
- Set up replication between the on-premise and on-cloud instances.
- Verify the status of replication.
# vradmin -g dg_name repstatus rvg_name
Ensure that the replication status shows:
Replication status: replicating (connected)