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
Prerequisites for configuring applications for disaster recovery
To be able to perform disaster recovery (DR) operations on the applications in the data center, ensure that the following requirements are met.
If applications are installed on VMware virtual machines, you need to configure the VMware vCenter for discovery. Similarly if the applications are installed on Hyper-V virtual machines, you need to configure the Hyper-V server for discovery.
The replicated storage provided to the application hosts from the storage arrays is discovered if you have configured the discovery hosts and the enclosures.
Replicated storage can be provisioned to the application in numerous ways. For applications installed inside virtual machines, Resiliency Platform discovers storage that is provisioned to the virtual machines in raw mode (e.g. VMware RDM mode) from the hypervisors. Raw mode can also be achieved by using NPIV HBAs and provisioning storage (LUNs) directly from the arrays to the Virtual HBA Ports assigned to the virtual machines.
If the storage is provisioned to the application virtual machines using hypervisor, then you need to provision appropriate snapshot devices to the virtual machines in the same manner as the replicated devices. This is required to perform the rehearsal operation successfully.
For NetApp SnapMirror and HP 3PAR Remote Copy, the snapshot devices do not exist beforehand and are created as a part of the Rehearsal operation. These snapshot devices should be mapped to the application hosts. As part of the Rehearsal operation, Resiliency Platform maps the snapshot devices to the same hosts to which the replicated LUNs are mapped. If the replicated LUNs are mapped through the hypervisor, then Resiliency Platform cannot further provision them to the application virtual machines.
As a result, Rehearsal is not supported with these replication technologies when the application is installed in virtual machines with replicated storage mapped as raw LUN by the hypervisor.
Applications must be members of the same Veritas Replication Set.
They must use the same replication technology.
Application binaries should be stored on local storage and data files on replicated storage.
The DNS server settings should be configured for both data centers. DNS settings are required for binding a host name to different IP addresses on the DR site. This is required only if you plan to use the Resiliency Platform for performing DNS updates.
Ensure that you have disabled the 'Quick removal' policy for disks in Windows Server 2008 R2 and disabled the 'write-cache' policy for disks in Windows Server 2012 R2.
Applications should be preconfigured at the recovery data center before creating resiliency groups and proceeding with the DR operations. Discovery of these applications on the recovery data center must be complete and status should be offline. Ensure that the application instance name should be same at the production and recovery data center.
Linux LVM Volume Group used for data file storage of an application should not be in exported state.
On Linux application hosts, the data mount point of the application should be present in
/etc/fstab
file.For more information on configuring applications for remote recovery using EMC SRDF, RecoverPoint, and NetApp SnapMirror replication see the following topics:
See Configuring applications for disaster recovery using EMC RecoverPoint replication.
See Configuring applications for disaster recovery using NetApp SnapMirror replication.
More Information