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
Preparing host for replication
To enable the replication in Resiliency Platform using Resiliency Platform Data Mover, you need to add the asset and prepare it for replication. Asset can be a physical machine or a virtual machine.
To prepare a host for replication
- Ensure that you understand the use cases and prerequisites for adding hosts to an IMS.
Note:
After you add a new data disk to a Windows host and attach it to an IDE controller, you need to initialize the disk. This needs to be done before performing the Prepare Host for Replication task.
- Navigate to Settings (menu bar) > Infrastructure > Details View.
You can also access this page from the Quick Actions menu.
- Go to the on-premises data center and click Data Mover.
- Under Resiliency Platform Data Mover, click Prepare host for replication.
- In the wizard, select the type of host to be added.
Discovered Virtual Machines: Choose this option to select one or more virtual machines that are already discovered from your virtualization environment.
Non-discovered hosts (no-hypervisor configured or physical hosts): Choose this option to add virtual machines which are not yet discovered or which are physical hosts. You can import multiple hosts from a simple comma separated text file using this option.
- Choose the desired configuration mode from the following options:
Using VRP Console: You can configure a host using the username and password of the host. Resiliency Platform automatically installs the appropriate host agent packages on the host.
Using pre-deployed VRP Host Agent Packages: Choose this option if you do not have the username and password of the host or if you require full control for deploying the host agent packages using your tools and then configure the host without providing the username and password from the Resiliency Platform console. The VRP host agent packages can be downloaded from the IMS.
See Downloading Resiliency Platform host agent packages from IMS.
See Configuring Resiliency Platform host agent packages manually.
Note:
Ensure that you choose the same IMS to add this host from which you chose to download the VRP host agent package bundle to install and configure on that host.
- Select the IMS to which you want to add a host and click Next
- Based on the selected Host Type and Configuration Mode specify the following inputs:
Host Type
Configuration mode
Required Inputs
Discovered Virtual Machines
Using VRP console
Select one or more Virtual Machines and click Next. You can filter the virtual machines based on environment or on the virtualization server they are running on, or search them using their virtual machine name, family type, or host name.
Review the discovered Hostname for the virtual machine and modify it, if necessary.
Enter the username and password for each virtual machine in the table.
See Prerequisites for adding host for information about using non- root user accounts to add Linux hosts.
Click
to delete a row.
See Prerequisites for adding hosts . for information about using non- root user accounts to add Linux hosts.
Discovered Virtual Machines
Using a pre-deployed VRP Host Agent
Select one or more Virtual Machines and click Next. You can filter the virtual machines based on environment or on the virtualization server they are running on, or search them using their virtual machine name, family type, or host name.
Review the discovered Hostname for the virtual machine and modify it, if necessary.
Non-discovered hosts Physical hosts
Using VRP console
Type the host name and user credentials information in the table row. Use the following options to add information for multiple hosts.
Use the Add new rowoption to add a blank table row.
Use the Import from a text file option to import information from a text file with comma separated values. To do this, select the desired text file and click Load host details.
Use the
icon to copy the details of the elected table row. You can edit the details of the newly added row.
Use the
icon to delete the desired row.
See Prerequisites for adding hosts . for information about using non- root user accounts to add Linux hosts.
Non-discovered hosts or Physical hosts
Using a pre-deployed VRP Host Agent
Type the host name in the table row. Use the following options to add information for multiple hosts.
Use the Add new rowoption to add a blank table row.
Use the Import from a text file option to import information from a text file with comma separated values. To do this, select the desired text file and click Load host details.
Use the
icon to copy the details of the selected table row. You can edit the details of the newly added row.
Use the
icon to delete the desired row.
- Once you are done with entering the data for all the hosts, click Submit to initiate the Prepare Host for Replication activity for each host.
- Click the Status column value to navigate to the respective activity details view for a host to check if the activity is in progress or has failed.
The host is listed in the table for Replication Hosts on the Resiliency Platform Data Mover tab with Status column as Connected when the activity completes successfully.
When the recovery environment is AWS Cloud, the cloud storage and network drivers must be installed on the host in following conditions:
Windows Paravirtual (PV) drivers to recover Windows hosts
Xen block storage and networking drivers to recover SUSE Linux 11.4 hosts
If the compatible drivers are not installed already, the bundled versions of the required drivers are installed automatically when the hosts are added to resiliency group.
The bundled versions of the driver are located at:
For SUSE Linux platform:
/var/opt/VRTSsfmh/spool/addons/store/
<VRTSitrptapversion_of_the_release>/AWSPVDriver
Refer to the Readme.txt
file in this directory for version information of the bundled drivers.
If a VMWare virtual machine is already protected with Veritas Standalone Replication and has in-guest component then you cannot provision another virtual machine with the same BIOS ID as that of the protected virtual machine unless the protected virtual machine is upgraded to version 3.5.
See Troubleshooting: Cleaning up of stale Resiliency Platform configurations.
More Information