Veritas™ Resiliency Platform 2.2 Deployment Guide
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
About Veritas Replication Gateway pairs
To use the Resiliency Platform Data Mover feature, you must deploy at least one Replication Gateway on both the source and target data center. The source and target Replication Gateways must be paired before replication is enabled.
Starting from version 2.1, Resiliency Platform supports the asymmetric pairing of Replication Gateways. This feature facilitates deployment of only the required number of gateways on each side, based on data transfer rate and technology specific limits.
One Gateway on production site can be paired with multiple Gateways on recovery site and vice versa. One gateway can be paired with up to 16 gateways on the peer site.
For each Gateway pair, you can choose to apply an encryption scheme to the data replication.
When you protect virtual machines using Resiliency Platform Data Mover, you select the Gateway pair to use for the replication. Once the DR configuration is complete, the Replication Gateway at the source data center starts replicating the data to the paired Gateway at the target data center.
If the recovery data center is Amazon Web Services (AWS) cloud, then ensure that the virtualization server storage (datastore and volumes) on which the virtual machines reside are available to the Replication Gateway on the production data center.