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
Configuring the Replication Gateways
After the virtual appliance deployment, when you log into the virtual appliance console for the first time using the admin user credentials, the bootstrap process is automatically invoked. This bootstrap process is used to set up or configure the Resiliency Platform component for the first time.
The default network protocol for virtual appliance is Dynamic Host Configuration Protocol (DHCP). If the appliance detects DHCP during the first boot or before the completion of bootstrap process, the appliance network automatically gets configured. After the network configuration, you can either use the virtual appliance console or Secure Shell (SSH) to log in as admin user and complete the bootstrap process.
If DHCP is not configured in your environment, you have an option to use a static IP for the appliance. Since the appliance network is not automatically configured in this case, you can only use the console to log into the virtual appliance.
To configure a Replication Gateway
- Prerequisites:
See Prerequisites for configuring Resiliency Platform components.
The Replication Gateway configuration requires an extra disk of at least 50 GB, to be used as a staging disk. You can attach this disk before configuration or during the configuration. The default disk size of 50GB lets you protect up to 8 virtual machines and each additional virtual machine requires a disk of 6GB size. You can increase the size of the disk by using lvm option of the klish commands:
In any non-AWS environment, log in to the virtual appliance console or SSH using the following credentials:
Username: admin
Password: P@ssw0rd
Note:
In Azure environment, the password would be the one provided during deployment.
After a successful login, you are prompted to change the password of the admin user.
See Password policies for Resiliency Platform virtual appliance.
If you are logged in to SSH, you will be logged off the SSH session after the password change and you need to again log in to complete the rest of the steps of the bootstrap process. If you are logged in to the virtual appliance console, you can continue and complete the rest of the steps of the bootstrap process.
In AWS environment, do one of the following:
From a Linux client system:
Use SSH with the private key from the key-pair that you had selected while launching the instance in AWS. For example:
ssh -i private_key_file admin@ip_address_of_aws_instance
Ensure to modify the permissions for the private key file as 600 before using the file.
From a Windows client system:
Follow the documentation of AWS to connect to the Linux instance from a Windows system using PuTTY.
- Accept the End User License agreement (EULA) to proceed with the configuration.
- In the Host Network Settings section, you can configure the appliance network by using DHCP or static IP.
- In the Appliance Settings section, do the following:
Press the Enter key to confirm the use of an NTP server for configuring the date and time.
You are required to select the time zone. Follow the instructions as displayed on the virtual appliance console or SSH session to select the correct time zone.
Enter the FQDN or IP address of the NTP server. The appliance verifies the NTP server details. If there are any issues, details are displayed on the screen and you are prompted to enter the details again.
You can reset the timezone and NTP server at a later point of time using klish menu. Changing the system settings can affect the product functionality if incorrect values are set.
- In the Product Settings section, the virtual appliance is configured as Replication Gateway.
- You are prompted to confirm if you want to enable FIPS for the Replication Gateway appliance.
See About FIPS enablement for Replication Gateway appliance .
Note:
If you confirm to enable FIPS for the appliance, the appliance will be restarted after finishing the bootstrap process.
- You are prompted to attach an extra disk to the appliance. If you have already attached the extra disk, press Enter to confirm. If you have attached more than one extra disk, all disks are listed and you need to select the extra disk that you want to use. If you have not already attached the extra disk, attach the extra disk and then confirm or select the extra disk to be used. Ensure that you attach a thick provisioned disk.
While attaching the extra disk to the Replication Gateway appliance in AWS, use the full device path and use the format xvdb[a-z] instead of sd[a-z]. For example use /dev/xvdba instead of just xvdba.
- After a successful product configuration, a confirmation message will be displayed and you will be logged out of the virtual appliance console.
If the bootstrap is in AWS environment, you must log in once again using the SSH key and set the admin user password. You need to use this password for adding the gateway to the resiliency manager.
- Add the Replication Gateway to an IMS using the Resiliency Manager console.