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: Delete resiliency group operation
While performing the delete resiliency group operation, if the tasks fails at the delete Veritas Replication Set subtask, re-run the delete operation. If it fails again then you can perform the following steps to reclaim the resources.
Perform the following tasks on Replication Gateways on the production and Cloud data center using klish menu:
- Check for participating Veritas Replication Sets.
monitor datamover repl-sets
- Verify that replication is stopped on the gateway.
monitor datamover repl-sets
- Abort replication on gateway if replication is not stopped.
manage datamover operation abort
- Delete the Veritas Replication Sets.
manage datamover operation delete
Perform the following tasks on the hosts on the production data center
- Verify that the Veritas Replication Sets are deleted.
Linux host:
/opt/VRTSitrptap/bin/vxtapinfo status
Windows host:
C:\Program Files\Veritas\VRTSitrptap\cli\vxtapinfo status
- Delete the Veritas Replication Sets if the state is active.
Linux host:
/opt/VRTSitrptap/bin/vxtapaction stop -cg <CG_ID> /opt/VRTSitrptap/bin/vxtapconfigure delcg -cg <CG_ID> -force
Windows host:
C:\Program Files\Veritas\VRTSitrptap \cli\vxtapaction stop -cg <CG_ID> C:\Program Files\Veritas\VRTSitrptap \cli\vxtapconfigure delcg -cg <CG_ID> -force
- Verify that the journal disk is removed from each of the virtual machines on the production data center.
Size of the journal disk is usually 1 GB and naming format is:
[<datastore-name>] <vm-hostname>/drl-<uuid>/ITRPSRDRLDisk.vmdk
Remove the journal disk using vSphere client or Hyper-V UI.
Ensure that the file is deleted.
- For physical machines, you need to unsign the DRL disk:
Linux host:
Get the device name of DRL disk by executing the following command:
/opt/VRTSitrptap/bin/vxtapdrlfind
Execute the following command to unsign DRL disk:
/opt/VRTSitrptap/bin/vxtapdrlsign clear -drl_dev device_name
Where, device_name is the device name of the DRL disk.
Windows host:
Get the device name of DRL disk by executing the following command:
C:\Program Files\Veritas\VRTSitrptap\cli\vxtapdrlfind.exe
Execute the following command to unsign DRL disk:
C:\Program Files\Veritas\VRTSitrptap\cli\vxtapdrlsign clear -drl_dev device_name
Where, device_name is the device name of the DRL disk.
- Refresh the virtualization server if the resiliency group contains virtual machines.
- Delete the resiliency group using the web console.
Perform the following on cloud virtual machines:
Verify that the migrated cloud virtual machines are terminated and their volumes are deleted, including the Replication block tracking disk.
Note that the naming convention for Replication block tracking disk is
DRLVolume_RaaS_<GUID>
whereas for other disks the name starts withresiliency-group-name_virtual-machine-name
.Delete any snapshots for cloud volumes.
Detach the cloud volumes from the cloud gateway.
Remove the cloud virtual machines from the cloud IMS.
More Information