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
Troubleshooting: Migrate operation
Following are some issues that you may encounter while migrating a resiliency group consisting of virtual machines.
After performing the migrate operation, if the network interface card (NIC) is in disconnected state, you need to connect it manually. This is applicable when you migrate VMware and Hyper-V virtual machines to an on-premises data center and the replication technology is 3rd party.
If the Migrate operation fails while creating the network interface card (NIC) on Azure with the error Could not get IP data for NICs <network card name>, you need to create appropriate network mapping and launch the
operation.While migrating from cloud to on-premises data center, if the migrate operation fails with 'host not added to Infrastructure Management server' error then ensure that the host is added to the cloud IMS.
See Reasons for add host operation failure.
While migrating to the cloud data center if the operation fails before the reverse replication stage, then depending on where you want the virtual machine to be online do one of the following:
Virtual machine should be migrated to target data center: Run the Retry operation.
Virtual machine should remain online on the source data center: Run the Start resiliency group operation and select the Refresh storage, network, compute and customizations option.
While migrating to the cloud data center if the operation fails after the reverse replication stage, then you cannot bring the virtual machines up on the source data centre. You can only bring the virtual machines up on the target data centre. To bring the virtual machines up on the target data center, do one of the following:
Run the Retry operation.
Run the Start resiliency group operation and select the Refresh storage, network, compute and customizations option.
The migrate workflow ensures that there is no data loss during the migrate operation. So there are checks to ensure the data consistency of protected host with VRP Data Mover. If these checks fails then that results in failure and the workflow aborts.
If the migrate operation fails in
subtask of step, you should check the following:Connectivity between the protected host and source gateway.
Whether the protected host was powered off and not shutdown properly.
In such cases perform Start operation and select the Refresh storage, network, compute, and customizations option. Once the protected host is powered on, ensure that the host can communicate to the gateway, and then retry the migrate operation.
If the migrate operation fails in
subtask of step, you should check the following:If the connectivity between the source gateway and target gateways is intact. If the two gateways cannot communicate that implies a probable chance of data loss and so the workflow aborts.
In this case ensure that the two gateways can communicate with each other.