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
About managing VMware snapshots in Resiliency Platform
Resiliency Platform behavior with VMware vSphere virtual machine snapshots is different for different replication technologies. Refer to the following table to understand how the snapshots are handled before and after the disaster recovery operations.
Table: Behavior of Resiliency Platform with VMware snapshots
Scenario | 3rd party replication technology | Recovery to on-premises data center using Resiliency Platform Data Mover | Recovery to any cloud data center |
---|---|---|---|
Virtual machines have snapshots on source data center | Create resiliency group operation is allowed. | Cannot create resiliency group due to VMware limitation. | Cannot create resiliency group. The operation is blocked. |
If you take, revert, or remove snapshot on source data center after resiliency group is created | No operation is impacted or blocked | Cannot delete resiliency group. See note below. | No operation is impacted or blocked |
Snapshot tree is replicated and maintained on the target data center | Yes | No | No |
After migrate or takeover operations, the virtual machine on the target data center is in the same place in the snapshot tree as on the source data center | Yes | No | No |
When a virtual machine is on the target data center, taking, reverting or removing its snapshot from source data center | Yes, this is supported | Yes, this is supported | No, this is not supported |
Updating the snapshot tree on source data center if snapshots are created on target data center | Yes | No | No |
After migrating or taking over a virtual machine back to the source data center, the virtual machine is placed in the same position in snapshot tree as on the target data center | Yes | No | No |
Note the following:
After successful completion of rehearsal operation, do not delete or modify existing snapshots on target data center. Else cleanup rehearsal operation fails. You may create new snapshots as well as delete them on the target data center, but do not delete or modify the existing snapshots.
When recovering to on-premises data center using Resiliency Platform Data Mover or recovering to any cloud data center: For a virtual machine in a resiliency group, if a snapshot is reverted, then perform the Resync operation on the respective resiliency group. Resync operation synchronizes the data on the target data center.
After configuring a resiliency group for recovering to on-premises data center or cloud data center using Resiliency Platform Data Mover, if you create any snapshots, then Delete resiliency group operation is blocked. You need to first remove the snapshots from the vCenter server, refresh the vCenter server using Resiliency Platform console, and then delete the resiliency group.
For more information on VMware snapshots feature, refer to VMware documentation.
More Information