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
Upgrading Veritas Replication VIB
When you apply the Resiliency Platform update to Resiliency Platform components in an environment where VMware virtual machines are configured for recovery to on-premises data center, you need to upgrade the Veritas Replication VIB on all the ESXi clusters using the Veritas Resiliency Platform web console.
During the process of applying the update, the hosts are required to be in maintenance mode. If automatic DRS is enabled for the cluster, VMware vCenter automatically puts all the ESXi hosts in maintenance mode in a sequence by moving the virtual machines to other available ESXi host (based on the policy or capacity) and then update Veritas Replication VIB. If DRS is not enabled, then you need to manually put all the ESXi hosts in maintenance mode to perform the operation.
Steps to automatically upgrade the Veritas Replication VIB
- Prerequisites
Ensure that the DRS is properly configured. Also ensure that the DRS automation level is set to 'Fully Automated' on the ESXi Cluster.
- Navigate
Settings (menu bar) > Infrastructure > Details View
You can also access this page from the Quick Actions menu.
- Select the data center and click Data Mover.
- On Resiliency Platform Data Mover tab, in Replication ESXi Clusters table, do one of the following:
Click Upgrade Veritas Replication VIB. In the Upgrade Veritas Replication VIB on ESXi Cluster wizard, select one or more clusters where you want to upgrade Veritas Replication VIB.
In the list of clusters listed under Replication ESXi clusters, right click the cluster where you want to upgrade the Veritas Replication VIB.
- Select Use SORT URL to upgrade Veritas Replication VIB if you want to use the direct link of SORT URL to upgrade the Veritas Replication VIB on the clusters. In this case, you need to ensure that the SORT URL is accessible from the vCenter server.
Alternatively, you can use IMS to upgrade Veritas Replication VIB on the ESXi clusters.
- Click Next to initiate the process of upgrade on the clusters.
Note:
If the ESXi hosts are upgraded from 6.x version to 7.x, upgrade the Veritas Replication VIB immediately.
It may happen that the DRS is not configured properly and you need to manually put all the ESXi hosts in the maintenance mode to perform the operation. If some of the virtual machines in the cluster are running on local storage and DRS is not properly configured, you need to manually upgrade the Veritas Replication VIB using following steps. The below steps are performed to manually upgrade the Veritas Replication VIB using the below example with assumptions - Two ESXi hosts in source cluster: ESXi-1 host and ESXi-2 host
Steps to manually upgrade the Veritas Replication VIB
- Login to source vCenter server.
- Keep DRS mode enabled and DRS Automation mode as Manual on the ESXi cluster which needs VIB upgrade.
- Login to RM console and try to upgrade VIB on ESXi cluster. The Upgrade VIB operation fails along with error 'Host cannot be into maintenance mode to complete VIB installation' and this is expected because the DRS Automation mode is Manual.
- The VIB status on the ESXi cluster changes from Installed to Partially Installed. This is expected behaviour as the cluster has a new version of VIB and ESXi has older version of VIB installed.
You need to ensure the SORT URL is accessible from the vCenter server. Alternatively, you can use IMS to upgrade the Veritas Replication VIB on the ESXi clusters.
- Migrate all the virtual machines from ESXi-1 to ESXi-2 using VMware vMotion or power off the virtual machine, if no host machine is available for migrate. Do not keep any virtual machine running on the ESXi-1.
- Manually put the ESXi-1 into maintenance mode from the vCenter server. Later, the VIB upgrade will be automatically triggered on that ESXi by the vCenter server itself.
Note:
In case of upgrade VIB is not getting triggered on the ESXi automatically by vCenter server, execute the Resolve and Verify operation on the ESXi cluster from RM console which upgrades the VIB on that ESXi.
- Once upgrading the VIB is complete on the ESXi-1, exit from the maintenance mode for ESXi-1.
- Migrate all the virtual machines from ESXi-2 to ESXi-1 using VMware vMotion, or power off the virtual machines if no host is available for migrate.
- Manually put ESXi-2 into maintenance mode from the vCenter server. The VIB upgrade is automatically triggered on the ESXi by vCenter server itself.
Note:
In case upgrade VIB is not getting triggered on ESXi automatically by vCenter server, execute the Resolve and Verify operation on the cluster from RM console which upgrades the VIB on that ESXi.
- Once the VIB upgrade is complete on ESXi-2 , exit from the maintenance mode for ESXi-2.
- Login into RM console and execute the Resolve and Verify operation on the cluster which should change the VIB status from Partially Installed to Installed.
For the cluster with more than two ESXi's, repeat the steps 5 to step 10 to complete the upgrade for all the hosts in the cluster before moving to the next cluster. Repeat the steps 1 to 11 to manually upgrade the VIB on the target ESXi cluster.
Following steps has to be followed to upgrade VIB in stateless ESX. These steps has been validated with a cluster of two stateless ESX hosts booted using an Image (for example ImgProf_Org). As an example, following steps uses VRP VIB 3.4 and 3.5 but the steps are same for any other version as well.
Steps to upgrade the Veritas Replication VIB in stateless ESX
- A cluster with two stateless ESX hosts is up using an Image Profile (ImgProf_Org).
- Clone ImgProf_org to ImgProf_VIB3.4 and include VIB 3.4 VIB by editing the software package.
- Clone ImgProf_org to ImgProf_VIB3.5 and include VIB 3.5 VIB by editing the software package.
- Create deploy rule AD_VIB3.4 and include image profile ImgProf_VIB3.4 and HP_vtstap in it.
- Create deploy rule AD_VIB3.5 and include image profile ImgProf_VIB3.5 and HP_vtstap in it.
- Activate AD_VIB3.4 on both the hosts.
- Reboot both ESX hosts in the cluster.
- Install VIB 3.4 using Resiliency Platform interface (This will install VIB on the cluster).
- Upgrade Resiliency Platform to 3.5 version.
- Upgrade VIB from 3.4 to 3.5 using Resiliency Platform interface (This will upgrade VIB on the cluster)
- Activate AD_VIB3.5 for on both the hosts.
- Reboot both the ESX hosts in the cluster.