Veritas™ Resiliency Platform 2.2 Solutions for VMware
- Section I. Overview of Resiliency Platform
- Overview of Resiliency Platform
- Overview of Resiliency Platform Data Mover
- Overview of recovery to on-premises data center
- Managing assets protected by NetBackup
- Overview of Amazon Web Services
- Overview of vCloud
- Section II. Preparing your environment
- Using array-based replication
- Using Veritas Resiliency Platform Data Mover
- Managing disaster recovery network mapping
- Managing Replication Gateway pairs
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing resiliency groups
- Section IV. Managing disaster recovery
- Rehearsing DR operations to ensure DR readiness
- Performing disaster recovery operations
- Rehearsing DR operations to ensure DR readiness
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activities
- Managing evacuation plans
- Appendix A. General troubleshooting
- Resolving the Admin Wait state
- Appendix B. Sample policy and trust relationships for AWS
About Veritas Resiliency Platform Data Mover architecture
Veritas Resiliency Platform Data Mover uses the VMware vSphere APIs for I/O Filtering (VAIO) framework. It provides an I/O filter for replication that has been certified by VMware. VAIO enables filtering of a virtual machine's I/Os. The filter runs inside an ESXi server and intercepts I/O requests moving between a guest operating system and virtual disks.
Veritas Resiliency Platform Data Mover deploys a user-land module, called vtstap, on the ESXi host where the protected VMs are running. This module is built using the VMware VAIO APIs. It intercepts and replicates I/Os from the virtual machines. When you configure disaster recovery with Resiliency Platform Data Mover, the configuration process installs this module on the ESXi hosts for the selected virtual machines on the source data center. It also installs this module on the ESXi hosts in the selected cluster on the target data center. After a migrate or takeover operation is performed, the platform ensures that data is available in the target data center.
After Veritas Resiliency Platform Data Mover filters I/Os in the user land of the ESXi host where virtual machines are running, the I/O goes through the following path within the Replication Gateway at the source data center before it is replicated to the target data center.
Each Replication Gateway includes four daemons that run when replication is enabled:
I/O receiver
Continuously receives the virtual machine I/Os that were tapped and sent by the vtstap module in the ESXi host where virtual machines are running in a continuous fashion.
Transceiver
Transfers and receives data over the WAN link periodically.
Applier
Applies the data to the storage after it is received on the target gateway.
Scheduler
Manages and schedules data transfer between gateways.
Engine
Maintains the state of replication and also coordinates with all other components.
The virtual machines on the target (recovery) data center are provisioned only when a disaster recovery operation (such as migrate) is run in Resiliency Platform. The disaster recovery operation then can bring the virtual machines online in the recovery data center. This avoids unnecessary resource utilization and accounting when the workload is running in the other data center.
To use Veritas Resiliency Platform Data Mover, the source Replication Gateway and the target Replication Gateway are linked together into a Replication Gateway pair, which establishes the replication channel between the source and the target. A Replication Gateway pair is a one-to-one mapping of the source Replication Gateway to the target Replication Gateway. You can choose to encrypt the communication between gateways, unless you are using a dedicated VPN link.