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 integrating NetBackup with Resiliency Platform
NetBackup version should be 8.1.2 or later, or NetBackup Appliances 52XX version 3.1.2 or later.
The NetBackup primary server must be online.
Resiliency Platform supports recovery of VMware virtual machines backed up by NetBackup using VMWARE type of policies only.
The nbwebsvc user and nbwebgrp group must be configured. For more information, refer to
Veritas NetBackup Installation Guide
.You need to add the following settings in the DNS server to set up the communication between NetBackup primary server and Resiliency Platform components which are configured with IPv6 address or IPv4 and IPv6 address:
When the NetBackup primary server which is configured with an IPv4 and IPv6 address, and the Resiliency Manager is configured only using IPv6 address, the DNS server should only have entry of IPv6 hostname of the Resiliency Manager.
When the NetBackup primary server is configured with only IPv6 address and the Resiliency Manager and IMS are configured with both IPv4 and IPv6 address, to discover the NetBackup primary server into IMS, ensure that DNS server should only have only the entry of the IPv6 hostname configured for the NetBackup primary server.
Resiliency Platform can manage only those virtual machines that are backed up with No disk(s) excluded type of policy.
To enable trusted secure communication with NetBackup, refer See Enable trusted communication with external entities.
See Adding NetBackup primary server.
You can recover VMware virtual machines to AWS cloud using NetBackup images stored in AWS S3 buckets by the on premises with either NetBackup CloudCatalyst / MSDP-C with Image Sharing feature. This feature is available from NetBackup version 8.2 onwards.
The NetBackup server administrator must perform the following configuration tasks on the on-premises NetBackup primary server, and on the NetBackup Cloud Recovery Server (CRS) in the cloud to enable the recovery to cloud data center.
For the on-premises NetBackup domain, setup the CloudCatalyst or MSDP-C for taking backups in the desired target AWS S3 bucket.
When you have configured the virtual machines for recovery to AWS environment for disaster recovery of workloads using NetBackup Image Sharing and , if you have selected instance type which supports ENA as customization target, you need to install the ENA drivers manually.
Ensure that nvme is present in the workload's folder initrd/initramfs
Configure backup policies to backup the workload images to S3 bucket with this configuration.
Resiliency Platform supports recovery of VMware virtual machines backed up by NetBackup using VMware type of policies only.
Resiliency Platform can manage only those virtual machines that are backed up with No disk(s) excluded type of policy.
Ensure that the backup type is full or accelerated incremental.
Deploy the NetBackup CRS in the cloud data center.
Configure the CRS with the same S3 bucket where backups from on-premises data center are getting stored.
Add the CRS in the cloud data center. Do the following:
Navigate to
> view, locate the cloud data center, click the environment card to navigate to the tab.
Ensure the following:
The account used for the cloud data center configuration in Resiliency Platform and the account used for the NetBackup Cloud Recovery Server configuration should be the same. This allows Resiliency Platform to access the AMI restored using NetBackup Image Sharing APIs when provisioning EC2 instances.
The region for the cloud data center configured in Resiliency Platform must be same as the region of the S3 bucket configured for the NetBackup Cloud Recovery Server. This is because the Infrastructure Management Server (IMS) deployed in the cloud data center needs access to the AMIs that are created by the NetBackup Cloud Recovery Server. These AMIs are created in the region of the S3 bucket configured in the NetBackup Cloud Recovery Server.
You must add the following settings in the DNS server to set up the communication between NetBackup primary server and Resiliency Platform components which are configured with IPv6 address, or IPv4 and IPv6 address:
When the NetBackup primary server which is configured with an IPv4 and IPv6 address, and the Resiliency Platform is configured only using IPv6 address, the DNS server should only have the entry of IPv6 hostname of the Resiliency Platform.
When the NetBackup primary server is configured with only IPv6 address and the Resiliency Platform and IMS are configured with both IPv4 and IPv6 address, to discover the NetBackup primary server into IMS, ensure that DNS server should only have the entry of the IPv6 hostname configured for the NetBackup primary server.