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
- About Elastic Networking Adapter (ENA) support in Resiliency Platform
- Recovery to cloud data center
- Recovering virtual machines to AWS
- Recovering virtual machines to Azure
- Recovering virtual machines to Google Cloud Platform
- Recovering virtual machines to vCloud Director
- Recovering virtual machines to Orange Recovery Engine
- Recovering physical machines using Resiliency Platform
- Recovery to on-premises data center
- Deployment checklist
- Checklist for recovery of virtual machines to AWS
- Checklist for recovery of virtual machines to Azure
- Checklist for recovery of virtual machines to Orange Recovery Engine
- Checklist for recovery of virtual machines to Google Cloud Platform
- Checklist for recovery of virtual machines to vCloud Director
- Checklist for recovery to on-premises data center using Resiliency Platform Data Mover
- Checklist for recovery of virtual machines using NetBackup
- Checklist for recovery of virtual machines using third-party replication technology
- Checklist for recovery of application using third-party replication technology
- Checklist for recovery of virtual machines to AWS
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploy and download the Resiliency Platform virtual appliances
- About deploying the Resiliency Platform virtual appliances
- Downloading the Veritas Resiliency Platform virtual appliances
- Deploying virtual appliances in AWS
- Deploying virtual appliances in Azure
- Deploying virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Prerequisites for deploying the virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Deploying virtual appliances in vCloud Director
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Deploy and download the Resiliency Platform virtual appliances
- Depoly virtual appliances through Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Prerequisites for deploying the virtual appliances in AWS
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Apply Updates
- About applying updates to Resiliency Platform
- Step 1: Prepare for upgrade
- Step 2: Upgrading the Resiliency Platform (Detach / attach the disk)
- About applying updates to Resiliency Platform
- 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
- Recovering virtual machines to premises target data center
- Recovering virtual machines to cloud target data center
- Support for NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault as storage account
- Integrating with InfoScale clusters
- Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform
- Configuring InfoScale clusters in Resiliency Platform
- Managing the custom application or replication type in Resiliency Platform
- 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 NetBackup primary pairing
- Manage Recovery Readiness Bundle
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- Managing network objects in Resiliency Platform
- Network objects in Resiliency Platform
- DNS server configuration settings
- Managing network pairs
- Mapping network objects (Production and Rehearsal mapping)
- Manage networks
- Section VI. Managing settings
- Manage settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Managing user authentication and permissions
- Configuring authentication domains
- Managing settings for alerts and notifications and miscellaneous product settings
- Manage settings
- Section VII. Working with resiliency groups
- Organize assets
- Editing a resiliency group
- Deleting a resiliency group
- Viewing resiliency group details
- Manage virtual business services
- About virtual business services
- Organize applications
- Managing service objectives
- Organize assets
- Section VIII. 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) from AWS region to AWS region
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) from Azure to Azure
- 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) to Google Cloud Platform
- 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
- Managing the virtual machines for recovery to Azure using NetBackup MSDP-C.
- 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 IX. Managing disaster recovery
- Perform DR operations for virtual machines
- About Rehearse operation
- Performing the rehearsal operation for virtual machines
- Performing the recover operation for resiliency group
- Recovering virtual machines with multiple recovery points
- About Rehearse operation
- 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 X. Managing certificates
- Section XI. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Section XII. Using Resiliency Platform APIs
- Section XIII. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Troubleshooting: NetBackup issues
- Resolving the Admin Wait state
- Troubleshooting: IP customization
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
Replacing a Replication Gateway from a gateway pair
Using the Resiliency Platform console you can replace an existing Replication Gateway from a pair irrespective of whether the gateway is healthy or faulted.
To replace a gateway, you must go to the data center having the gateway and perform the replace gateway operation. In this case the peer gateway must be healthy.
If you want to replace both the gateways, then after replacing the first gateway wait till the operation is successfully completed before you replace the other gateway. If both the Replication Gateways are faulted, you cannot perform the replace Replication Gateway operation. You need to remove them and create a new pair.
Note:
1. Make sure you do not replace the Replication Gateway and its peer gateway from the Replication Gateway pair simultaneously. This may lead to replace Replication Gateway failure and you will have to delete the Replication Gateway, the gateway pair and its associated resiliency groups.
2. While replacing the Replication Gateway on the VMware environment, DRS automation level for the existing Replication Gateway and new Replication Gateway should be set to manual or should be disabled.
3. If you have replaced a Replication Gateway which is associated with a resiliency group which is protecting a physical workload, it is mandatory to perform resync operation once the replace gateway operation is successful.
Also, you can replace a gateway with another gateway only if it is configured to use the same mode of replication. For example, you cannot replace a gateway that is configured to use Direct mode of replication with the one that is configured to use Object Storage mode of replication.
When you replace a gateway, all the Veritas Replication Sets are moved to a new gateway and the Replication Gateway pairs are reconfigured. If the existing Replication Gateway is configured as a PXE boot server or as a DHCP server, then the new gateway is reconfigured as a PXE Boot server or a DHCP server.
Note that after replacing a gateway, irrespective of the replaced gateway being faulted or healthy, the replication resumes from the last successfully replicated update set.
Before you replace a replication gateway, if any of the resiliency groups that are associated with the gateway are in offline state, because the migrate or take over operation has failed, then you need to start the resiliency group before replacing the gateway. Ensure that you select the Refresh storage, network, compute and customizations check box in the start resiliency group wizard.
If the staging disk attached to the Replication Gateway is corrupted or removed, you need to shutdown the gateway and then perform the replace gateway operation.
After replacing a gateway, the Server Gateway attribute is inherited from the previous pair. If the Replication Gateway being replaced itself is the Server Gateway, then the attribute is updated to point to the new gateway. Ensure that the networking constraints between the two gateways are maintained with the new gateway.
Replace Replication Gateway operation is not supported in the following scenarios:
When recovering VMware virtual machines from an on-premises data center to vCloud Director.
When recovering virtual machines from vCloud Director to vCloud Director.
From version 3.5, you can configure the resiliency group for Continuous Data Protection (CDP) by selecting the Enable Continuous Data Protection checkbox while selecting the appropriate gateway pair.
To replace a Replication Gateway from a gateway pair
- Navigate to Settings (menu bar) > Infrastructure > Details View
You can also access this page from the Quick Actions menu.
- Click Data Mover > Resiliency Platform Data Mover tab.
- In the Replication Gateways table, right-click the Replication Gateway which you want to replace, and select Replace Gateway.
- From the list of gateways, select the replacement gateway, and click Next to initiate the replace operation.
The replace Replication Gateway operation may fail if there are any resiliency groups in configuration failed state, that are associated with the gateway. You then need to delete the Veritas Replication Sets, then delete the resiliency groups, and then retry the replace gateway operation.
While replacing a Replication Gateway having CDP storage attached, make sure that the datastore on which the CDP storage resides is accessible to new Replication Gateway.
More Information