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
Post upgrade tasks
After upgrading to 3.2, you may need to perform certain operations in certain scenarios.
Taking over a resiliency group from cloud data center is supported in version 3.1. After upgrading to 3.1, if the below risk is displayed for a resiliency group, then you need to do the following:
Edit the resiliency group using edit configuration intent. Please ensure that resiliency group is online in premise datacenter.
If the resiliency group is online on the on-premises data center, then edit the resiliency group using the Edit Configuration intent. You may click next on each panel and submit the operation without making any changes.
If the resiliency group is online on cloud data center, you need to migrate the resiliency group to on-premises data center. And then edit the resiliency group using the Edit Configuration intent. Do not perform the Takeover operation for bringing the resiliency group to on-premises data center.
After upgrade to 3.1 Update 1, for Hyper-V virtual machines replicated using HPE 3PAR Remote Copy replication technology, you need to refresh the 3PAR enclosure. Refresh is required after performing the Rehearsal operation and before performing the Cleanup Rehearsal operation.
For a Hyper-V virtual machine if the default location of the virtual machine configuration files is different than the location which is set at Hyper-V server level. Then after upgrading to 3.1 Update 1 or later, you need to edit the resiliency group. Edit the resiliency group using the Edit Configuration intent. Continue through the wizard without making any changes and click
. This is applicable if you are using any 3rd party replication technology.If you are protecting your assets using NetBackup, then after upgrading to version 3.2 or later, you need to upgrade to NetBackup version 8.1.
If you are protecting your assets using NetBackup, then after upgrading to version 3.2 or later, ensure that you add the NetBackup master server using the host name.
If any 3rd party replication technology is used, then you need to edit the resiliency group for the following scenarios:
If the virtual disks are moved manually to another datastore before upgrading to version 3.2 or later.
If Distributed Resource Scheduled (DRS) was enabled and Storage vMotion was completed before upgrade.
If virtual machine snapshot is taken before upgrading to 3.2 or later, you need to edit the resiliency group.