Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Resiliency Platform features and components
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Integrating with InfoScale Operations Manager
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Prerequisites for adding hosts
- Removing hosts
- Preparing host for replication
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- About Replication Gateway pair
- Managing Data Gateway
- Manage enclosure assets
- Adding a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- AWS Customization options panel
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- Managing virtual machines for remote recovery (DR) to Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Preparing Hyper-V virtual machines for using array-based replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- About custom script
- Perform DR operations for virtual machines
- Section IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
How Resiliency Platform Data Mover handles DR operations
Migration refers to a planned activity involving graceful shutdown of virtual machines at the source data center and bringing virtual machines up at the target data center and vice-versa. In this process, replication ensures that consistent virtual machine data is made available at the source and target data center.
When you migrate a resiliency group, the Data Mover Connection Status should be Connected, Data State should be Consistent, and Replication State should be Active. When you initiate a Migrate operation, Veritas Resiliency Platform checks whether the virtual machines and source data center Replication Gateways are up. The migrate operation involves stopping virtual machines, detaching disks from virtual machines and attaching them to the gateway.
The migrate operation is similar to the takeover operation, except that the migrate operation is used when the virtual machines can be gracefully shut down. The takeover operation is used in case of disaster, when the source virtual machines are not reachable. The migrate operation involves shutting down the virtual machine from within the guest machine, whereas, the takeover operation involves only stopping the virtual machines.
There is difference between migrate and takeover operations. The migrate operation allows reverse replication, whereas the takeover operation does not allow reverse replication. After takeover, the resync operation is required to bring back data or workload onto the source data center.
Takeover is an activity initiated by a user when the source data center is down due to a disaster, and the virtual machines need to be brought up at the target (recovery) data center to provide business continuity.
The replication includes any changes to the boot disks of the virtual machines. As a result, bootable copies of the source virtual machines can be brought up on the recovery data center.
Since it is an unplanned event, the data available at the recovery data center may not be up-to-date. You need to evaluate the tolerable limit of data loss. If the available data is within the acceptable limits, perform the takeover operation to bring up the source workloads in the recovery data center. The takeover operation provisions and brings up the virtual machines at the recovery data center using the latest data on the recovery data center storage.
The takeover activity operates on an entire resiliency group, even if the disaster affects only certain workloads in the resiliency group.
After a takeover, the virtual machine in the recovery data center runs the application and writes to the storage in the recovery data center.
A takeover operation as a result of a disaster event moves the workloads from a source (production) data center to a target (recovery) data center. You must plan for how to restore the workloads back to a production data center once it is up and running.
The first step in the process is to use the resync operation to ensure that the data in the target data center is synchronized to the source data center storage. The resync operation performs the full synchronization between the storage on the target and the source data centers. After the synchronization is complete, you can use the migrate operation to restore the virtual machines to the source data center.
Both the resync and migrate operations are performed for an entire resiliency group.