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
- 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 Google Cloud Platform
- 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
- 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 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
Adding VMware virtualization servers
You can add VMware vCenter servers to Veritas Resiliency Platform for discovery by an Infrastructure Management Server (IMS). The VMware discovery provides the following information:
Information on the vCenter Server
Information on the ESX servers that the vCenter Server manages
When adding a vCenter Server, you have the option to automatically discover all ESX servers registered to the vCenter Server or select which of the available ESX servers to discover.
Information on the virtual machines that are configured on the ESX servers
Note:
If there is more than one IMS in a data center, you can add the same vCenter Server to more than one IMS. For example, you may want to split up the ESX server discovery between multiple IMSs. To accomplish this, you first add the vCenter Server to one IMS for one set of ESX servers. Then once discovery is complete, you use the Edit option to add another IMS and select a different set of ESX servers. This is applicable only if the recovery is to an on-premises data center.
You can add a VMware vCenter server based in cloud in either a normal Data Center or a Data Center of type Cloud, created with the appropriate cloud credentials.
To add VMware virtualization servers
- Prerequisites:
- Navigate
Settings (menu bar) > Infrastructure > Details View
You can also access Manage Asset Infrastructure from the Quick Actions menu.
- Expand the data center > Virtualization and Private Cloud > VMware tab.
- Launch the + vCenter wizard.
- In the wizard, specify the following information and click Next.
Specify the fully-qualified hostname of the vCenter Server that you want to discover along with its port number. The default port is 443.
Support for IPv6 address is enabled. You can configure vCenter server using IPv6 address or hostname registered with DNS server.
When entering login credentials, an administrative vCenter Server user account is required.
If the data center has more than one IMS, a list of IMS names is shown. Select the IMS that you want to use to discover and monitor the vCenter Server and ESX servers.
- Choose to automatically discover all ESX servers or select ESX servers to discover. If multiple clusters are available, you can use Group By to sort the list of ESX servers by cluster. Click Next. It is recommended to select all ESX servers within a cluster.
If you choose the auto discover option, all currently available ESX servers are discovered. In addition, ESX servers later added to the vCenter Server are automatically discovered. However if some of the ESX servers associated with the vCenter Server are disconnected, then the auto discovery option is disabled.
If you are adding a vCenter server based in cloud, you have to select the auto discovery option as the ESX cluster membership changes are frequent and automatically initiated by the cloud provider.
- Review the configured vCenter Server, ESX servers, and IMS on the verification screen and submit the configuration.
The wizard notifies you of any issues.
The vCenter Server that has been added is listed on the VMware tab. Discovery of the ESX servers occurs in the background. You can view the progress on the Activities page.
For a vCenter server configured, if any of following changes are made in vCenter server after adding it to Resiliency Platform then,
Any ESX server that is configured in Resiliency Platform is removed and re-added into vCenter server.
Any existing ESX/Datastore cluster is destroyed and recreated.
After such a change in vCenter server, user should edit vCenter configuration in Resiliency Platform without any changes to the ESXs that were configured earlier. This allows the VMware NRT daemon in Resiliency Platform to start monitoring the objects that were re-added/re-created in vCenter server.
If changes are made on the virtualization servers after the IMS discovery is complete, you need to refresh the discovery of the vCenter Server.