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
Performing the resync operation for virtual machines
When disaster strikes on a production data center, the takeover operation is invoked to start the resiliency groups on the recovery data center.
Since the production data center is not working, the data replication between the two sites does not happen. After the production site is back up and running, you need to prepare the production site for the next failover or for a migration operation. This preparation includes cleaning up any residue and resuming the replication from the recovery to the production site.
Use the Resync operation on the Resiliency Platform console to automate these steps for the required resiliency groups. This operation cleans up the residue which includes stopping physical and virtual machines, unregistering virtual machines, unmounting file systems, datastores, etc.
In Microsoft Failover Cluster environments, the Resync operation may fail in the first step to cleanup the virtual machine residue. You can manually cleanup the virtual machine residue and proceed.
See Manually cleaning up virtual machines.
Consider the following if you have configured your assets for recovery to vCloud Director without adding the VMware vCenter server or Hyper-V server:
You need to perform the resync operation after Migrate or Takeover. In the Activities panel, if the workflow is in Paused state for "Resync Replication" subtask, then you need to manually start the physical and virtual machines. Ensure that the physical and virtual machines boot from PXE OS of the replication gateway that is configured as PXE server. You can verify the virtual machines boot progress from vCenter or Hyper-V console by checking the virtual machine console. When the boot is complete, click so that the workflow proceeds with synchronzing data from the disks on recovery datacenter to those on the on-premises data center. After Resync operation is complete, do not shut down the virtual machines, otherwise the subsequent Migrate or Takeover operations fail.
Performing the resync operation
- Prerequisites
If the target (recovery) data center is on-premises, and the last performed operation was takeover, then you may need to restart the Hyper-V server or the ESX server. Although the Resync operation cleans up any residue on the source data center before resuming replication, there could be some residues that can be cleaned up only by restarting the hypervisors.
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.
Prerequisites for resync operation of physical workloads
The resiliency group must be configured for DR and migrated to the recovery datacenter.
Ensure that PXE boot server is configured on the on-premises Replication Gateway.
Ensure to set network boot (PXE boot) as the first boot priority in the system BIOS.
If you are not using 3rd party DHCP server, then configure DHCP server on the PXE Boot server that is configured on the on-premises Replication Gateway.
- Navigate to Assets (navigation pane) > Resiliency Group(s) tab
- Double-click the resiliency group to view the details page. Click Resync.
- In the Resync panel, select the production data center name from the drop-down list, and click Next.
If the Resync operation fails, check
to know the reason and fix it. You can then launch the operation. The operation restarts the resync 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.After completing takeover from cloud and resync, the resiliency group details page shows entries for deleted or unavailable virtual machines on cloud data center. To remove these stale entries, after resync is complete, edit the resiliency group with Edit Configuration intent. You may submit the wizard without making any changes.