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
Migrating a resiliency group
Migration refers to a planned activity involving graceful shutdown of physical and virtual machines at the source data center and starting them at the target data center. In this process, replication ensures that consistent data of the assets is made available at the target data center which could be the on-premises or cloud data center. In Veritas Resiliency Platform, the migration of assets is achieved by grouping them in a resiliency group, configuring disaster recovery for the resiliency group, and thereafter performing the migrate operation on this resiliency group.
Consider the following:
If you perform the takeover operation, then you must perform the Resync operation before you migrate back to the production data center.
If the Enable reverse replication option is not selected, then before migrating the virtual machines to the target data center and after migrating back to the source data center, you need to perform the Resync operation.
If the recovery data center is Azure cloud, then after you migrate from the cloud data center to the on-premises data center, you need to refresh Azure cloud to rediscover the cloud-based objects.
During the migrate operation, virtual machines on the source data center are gracefully shut down. If you manually shut down the virtual machine before performing the migrate operation, and if the shut down was not graceful, then the migrate operation may fail. This is applicable when the replication technology is Resiliency Platform Data Mover and the target data center is in cloud.
When you upgrade from an earlier version to version 3.2 or later, then after performing the migrate operation, a risk is raised. This risk is regarding the changes in NIC configuration when you migrate to any cloud data center. Suppress this risk while the resiliency group is online on cloud. Migrate back to the on-premises data center and then edit the resiliency group to fix the NIC configuration.
Ensure that the Data Mover connection status is Connected, Data State is Consistent, and Replication State is Active.
It is recommended to stop or disable NetworkManager on RHEL hosts having multiple NICs. This is required if the recovery data center is AWS, Azure, OpenStack cloud, or HUAWEI CLOUD.
For VMware virtual machines, ensure that the network mapping of all the required port groups, or subnets across the data centers is complete.
For Hyper-V virtual machines, ensure that the network mapping of all the required virtual switches across the data centers is complete.
See Creating network pairs between source and target data centers.
If the recovery data center is in AWS , Azure, or HUAWEI CLOUD, then ensure that the network mapping of all the required subnets across the data centers is complete.
If the recovery data center is in cloud, then you need to set the SAN policy to either OnlineAll or OfflineShared based on whether you have shared or non-shared disks. For more details refer to Microsoft Documentation.
If the status of the virtual machine on the recovery data center is not correctly displayed, then you need to refresh the cloud discovery or the virtualization server discovery.
To migrate a resiliency group
- Navigate
Assets (navigation pane) > Resiliency Group(s) tab
- Double-click the resiliency group to view the details page. Click Migrate.
- Select the target data center and click Next.
If the Migrate operation fails, check
to know the reason and fix it. You can then launch the operation. The operation restarts the migrate workflow, it skips the steps that were successfully completed and retries those that had failed.Do not restart the workflow service while any workflow is in running state, otherwise the
operation may not work as expected.For more information on troubleshooting specific scenarios,
More Information