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 DNS server settings for a data center
You may have one or more DNS servers across your data centers. When a virtual machine is migrated from one data center to another, its IP address may change depending on the network settings. You may want the DNS records to be updated, so that the same host name is mapped with different IP address after the migrate or take over operation. To let Resiliency Platform update the DNS records, you need to configure DNS server details in Resiliency Platform for each data center.
While configuring the resiliency group for disaster recovery, you can select the DNS customization option for enabling the DNS record updates.
When you may have one or more DNS servers across your data centers and a virtual machine is migrated from one data center to another, its IP address may change depending on the network settings. Resiliency Platform requires DNS server so that it can resolve IP address and Hostname from DNS server. You may need to register newly assigned IP address to the virtual machine with DNS server so that Resiliency Platform can manage it.
Using the Resiliency Platform console, you can add DNS servers for the data center or remove the settings for servers that were previously added.
Command to generate the keytab file and the privileges required:
Run the below mentioned command on Windows DNS to generate keytab file:
ktpass.exe -princ <User Name>@<DNS DOMAIN> -mapuser <User Name>@<DNS DOMAIN> -pass <User Password> -ptype <Principal Type> -out <Keytab File Name>
-princ : Enter the service principal name in the form <user name>@<DNS DOMAIN> . Provide domain name in capital letters.
-mapuser: Maps the name of the Kerberos principal which is specified by the princ parameter, to the specified user account. Provide domain name in capital letters.
-pass: Enter the password for the principal user name that is specified by the princ parameter.
-ptype: Enter the principal type. KRB5_NT_PRINCIPAL is the recommended principal type.
-out: Enter the name and location where the keytab file should be generated.
Ensure that you have the required privileges in Windows DNS to update Forward and Reverse Lookup zones. Forward and Reverse Lookup zones should have 'Dynamic Updates' setting enabled. Refer to the Microsoft documentation for more details.
See Example of command for Windows keytab file.
Command to generate key and private file, and the privileges required:
Run the below mentioned command on Linux Bind to generate key and private file:
dnssec-keygen -a <Algorithm> -b <Keysize> -n <Name Type> <Key Name>
-a: Enter the encryption algorithm. For TSIG, HMAC-MD5 is mandatory. Algorithm is case-insensitive.
-b: Enter the number of bits in the key. For the HMAC-MD5 algorithm, key size must be between 1 and 512 bits.
-n: Enter the host for TSIG transaction authentication for dynamic updates. Nametype is case-insensitive.
Ensure that you have the required privileges in Bind to update Forward and Reverse Lookup zones. Forward and Reverse Lookup zones should have 'Dynamic Updates' setting enabled. Refer to Linux documentation for more details.
Below is an example of the command:
dnssec-keygen -a HMAC-MD5 -b 128 -n HOST example.com.
To configure DNS server settings for a data center
- Prerequisites
You must have the following information:
Only IP needs to be provided here. Host name does not work.
The domain name should be in ALL CAPS. The user name should not contain domain\username but user name and in same case as the keytab was generated.
FQDN is needed here. Short name does not work.
- Navigate
Settings (menu bar) > Infrastructure > Details View
You can also access this page from the Quick Actions menu > Settings > Manage Asset Infrastructure > Details View
- Expand the data center > Access Profile
- Click the Bind or Windows DNS tab.
DNS servers already added for the data center are listed in the table. You can remove or add a new DNS server.
- To add a new DNS server for the data center click + New DNS.
- Specify the IP address for the DNS server and select the purpose, either Rehearsal or Production.
- Add one or more domains for the DNS server:
Fill in the domain name and the authentication type. For TSIG, browse to the key and private files. For GSSAPI, enter the user name and browse to the keytab file.
Enter a test host name and IP address and select Test. If the test is successful, that is the DNS configuration is validated, the Add button is enabled.
Select Add.
- If you are done adding domains, select Next.
- To remove a DNS server, right-click the required DNS server in the table and select Remove.