Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Veritas Resiliency Platform
 - About Resiliency Platform features and components
 - About Resiliency Platform capabilities
 - Replication in a Resiliency Platform deployment
 - About Veritas Resiliency Platform Data Mover
 - About managing VMware Storage vMotion in Resiliency Platform
 - About managing VMware snapshots in Resiliency Platform
 - About IPv6 network support in Resiliency Platform
 - About Continuous Data Protection (CDP)
 - About Elastic Networking Adapter (ENA) support in Resiliency Platform
 - Planning a resiliency domain for efficiency and fault tolerance
 - On-boarding with Resiliency Platform
 - About Resiliency Platform APIs
 
 - Recovery to cloud data center
 - Recovery to on-premises data center
- Recovering InfoScale applications
 - Recovering Applications using third-party replication technology
 - Recovering Hyper-V virtual machines using third-party replication technology
 - Recovering VMware virtual machines using third-party replication technology
 - Recovering VMware virtual machines from VMware to VMware using NetBackup
 - Recovering VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
 - Recovering physical machines to VMware virtual machines on an on-premises data center using Resiliency Platform Data Mover
 
 - Deployment checklist
- Checklist for recovery of virtual machines to AWS
- Checklist for recovery of VMware virtual machines to AWS
 - Checklist for recovery of physical machines to AWS using Resiliency Platform Data Mover
 - Checklist for recovery of Hyper-V virtual machines to AWS
 - Checklist of virtual machines for recovery from AWS to AWS
 - Checklist for recovery of VMware virtual machines to AWS cloud using NetBackup
 
 - 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
 - Prerequisites for vCenter server
 - Prerequisites for ESXi cluster nodes
 - Support matrix for RDM disk support (VMware)
 - Support matrix for Pass-through disk and shared disks in Hyper-V
 
 - Checklist for recovery of virtual machines to AWS
 - System requirements
- System resource requirements for Resiliency Platform
 - Network and firewall requirements
 - Ports required for Resiliency Manager
 - Ports required for IMS
 - Ports required for recovery of assets using NetBackup
 - Ports required for hosts
 - Ports required for recovery of assets to AWS or VMware in Cloud (VMC)
 - Ports required for recovery of assets to Azure or Azure VMware Solution (AVS)
 - Ports required for recovery of assets where both (source- target) data centers are cloud
 - Ports required for recovery of assets to Google Cloud Platform
 - Ports required for recovery of physical machines to on-premises data center
 - Ports required for recovery of assets to on-premises data center using Resiliency Platform Data Mover
 - Ports required for Replication Gateway used for recovery to cloud data center
 - Ports required for Replication Gateway used for recovery of physical machines
 - Ports required for Replication Gateway used for recovery of VMware virtual machines to on-premises data center
 - Ports required for recovery of assets to on-premises data center using third-party replication technology
 - Ports required for recovery of InfoScale applications
 
 - 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
- Downloading the virtual appliances for AWS
 - Downloading the virtual appliances for Azure
 - Downloading the virtual appliances for Google Cloud Platform
 - Downloading the virtual appliances for recovery using NetBackup
 - Downloading virtual appliances for recovery using InfoScale applications
 - Downloading virtual appliances using Resiliency Platform Data Mover
 - Downloading the virtual appliances using third - party replications
 - Downloading virtual appliances for recovery of physical machines to VMware virtual machines
 
 
 - Deploying the virtual appliance through VMware vSphere Client
 - Deploying the virtual appliance through Hyper-V Manager
 - 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
 - API permissions required for Google Cloud Platform
 - Uploading the OVA file using web-based method
 - Uploading the OVA file using command-line method
 - Creating Image using web-based method
 - Creating Image using command-based method
 - Launching the instances of virtual appliances
 
 
 - Deploying the virtual appliances in Google Cloud Platform using OVA files
 - About configuring the Resiliency Platform components
 - Virtual appliance security features
 - About hotfixes
 - References
 
 - Deploy and download the Resiliency Platform virtual appliances
 - Depoly virtual appliances through Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Permissions required in AWS Marketplace for IAM roles RM, IMS and Replication Gateway
 - Prerequisites for deploying the virtual appliances in AWS
 - Configuring Amazon VPC for deployment using CloudFormation Templates
 - Providing inputs for Resiliency Platform CloudFormation Templates
 - Uninstalling Resiliency Platform components when deployed through AWS Marketplace
 
 - Deploying the virtual appliances in Azure through Azure Marketplace
 - Deploy virtual appliances in Azure Stack using Azure Stack Marketplace
 
 - Deploying the virtual appliances in AWS through AWS Marketplace
 - Apply Updates
- About applying updates to Resiliency Platform
- Pre-upgrade tasks
 - Step 1: Prepare for upgrade
 - Step 2: Upgrading the Resiliency Platform (Detach / attach the disk)
 - Step 3: Start the automatic bootstrap process
 - Steps to replace the Replication Gateway appliance
 - Rollback steps in AWS environment
 - Rollback steps in Azure environment
 - Rollback steps in VMware environment
 - Rollback steps in Hyper-V environment
 
 - Applying upgrade to Resiliency Platform for managing InfoScale clusters
 - Applying updates to the hosts
 - Applying update on Resiliency Managers
 - Applying updates to the Veritas Data Gateway
 
 - About applying updates to Resiliency Platform
 
 - Deploy and configure
 - Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Setting up the resiliency domain
 - Connecting to the Resiliency Platform web console
 - Getting started with a new Resiliency Platform configuration
 - Managing Resiliency Managers
- Adding a Resiliency Manager to an existing resiliency domain
 - Viewing the status of a Resiliency Manager in a data center
 - Performing data resync on a Resiliency Manager
 - Renaming a Resiliency Manager
 - Removing a Resiliency Manager from a resiliency domain
 - Resiliency Manager outage impact on configuration and operations
 
 - Managing Infrastructure Management Servers
 - Managing on-premises data centers
 - Adding Azure Stack private cloud configuration
 - Managing cloud configurations
 - Managing private cloud configurations
 
 - Integrating with NetBackup
- About NetBackup and NetBackup Appliances
 - About protecting assets with NetBackup using Resiliency Platform
 - Prerequisites for integrating NetBackup with Resiliency Platform
 - Recovering virtual machines to premises target data center
 - Recovering virtual machines to cloud target data center
 - Fetch Resiliency Platform certificates
 - Support for NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault as storage account
- Configuring NetBackup Cloud Recovery Server (CRS) with Veritas Alta Recovery Vault storage account in Resiliency Platform
 - Editing the NetBackup Cloud Recovery Server (CRS) configured with Veritas Alta Recovery Vault storage account
 - Removing the NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault storage account
 - Refreshing the NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault storage account
 
 
 - Integrating with InfoScale clusters
- Support matrix for InfoScale applications
 - Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform
 - Configuring InfoScale clusters in Resiliency Platform
 - Reconfiguring InfoScale clusters in Resiliency Platform
 - Removing the InfoScale clusters in Resiliency Platform
 - Refreshing 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
- Adding the asset infrastructure
 - Managing host assets
 - About adding host assets
 - Prerequisites for adding hosts
 - Adding application hosts
 - Refreshing host discovery information
 - Removing hosts
 - Uninstalling the host package from a Linux host
 - Uninstalling the host package from a Windows host
 - Reasons for add host operation failure
 - Preparing host for replication
 - Refreshing the replication host
 - Moving the replication host to another IMS
 - Removing the replication host
 
 - Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- VMware vCenter Server privileges: configuring ESX servers
 - VMware vCenter Server privileges: basic monitoring of assets
 - VMware vCenter Server privileges: using third party replication
 - VMware vCenter Server privileges: replication using Resiliency Platform Data Mover in Hypervisor mode
 - VMware vCenter Server privileges: replication to cloud data center
 - VMware vCenter Server privileges: replication using in-guest mode of Resiliency Platform Data Mover
 - VMware vCenter Server privileges: using NetBackup
 - VMware vCenter Server privileges: for recovery of physical machines to VMware
 
 
 - Prerequisites for adding VMware virtualization servers
 - Adding VMware virtualization servers
 - Editing a VMware virtualization discovery configuration
 - Viewing the details of a VMware virtualization discovery configuration
 - Removing a VMware vCenter Server discovery configuration
 - Refreshing VMware vCenter Server discovery information
 
 - Managing VMware virtualization servers
 - Manage Veritas Replication VIB
 - Manage Hyper-V assets
 - Manage Gateways
- Managing Replication Gateways
 - Adding a Replication Gateway
 - Refreshing a Replication Gateway
 - Removing a Replication Gateway
 - Moving a Replication Gateway to another IMS
 - Viewing Replication Gateways
 - About Replication Gateway pair
 - Creating a Replication Gateway pair
 - Modifying encryption for a Replication Gateway pair
 - Replacing a Replication Gateway from a gateway pair
 - Removing a Replication Gateway pair
 - Viewing Replication Gateway pairs
 - Configuring PXE on Replication Gateway
 - Configuring the Replication Gateway as a DHCP Server
 - Unconfiguring PXE boot server from a Replication Gateway
 - Unconfiguring DHCP server from a Replication Gateway
 - Managing Data Gateway
 
 - Manage enclosure assets
- About the discovery host for enclosures
 - Adding a discovery host
 - Refreshing a discovery host
 - Removing a discovery host
 - Configuration prerequisites for adding storage enclosures to an IMS
 - Adding storage enclosures
 - Adding RecoverPoint appliance for replication
 - Editing the discovery configuration for an enclosure
 - Removing the discovery configuration for an enclosure
 - Refreshing enclosure discovery information
 - Manage SSH host keys panel
 
 - 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
- Creating network pairs between source and target data centers
 - Mapping network objects (Production and Rehearsal mapping)
- Network pairs for recovering virtual machines to AWS
 - Network pairs for recovering virtual machines from AWS region to AWS region
 - Network pairs for recovering virtual machines to Azure
 - Network pairs for recovering virtual machines from Azure to Azure
 - Network pairs for recovering virtual machines to Google Cloud Platform (GCP)
 - Network pairs for recovering machines to on-premises data center (For NetBackup, third-party replication or Resiliency Platform Data Mover)
 - Network pairs for recovering physical machines to VMware
 - Network pairs for recovering physical machines to AWS
 - Network pairs for recovering physical machines to Azure
 
 - Deleting a network pair
 
 - Support for NIC teaming / bonding for physical machines
 - Example of command for Windows keytab file
 
 
 - Manage networks
 - Section VI. Managing settings
- Manage settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Adding, modifying, or deleting email settings
 - Adding, modifying, or deleting SNMP settings
 - Throttling the notifications
 - Downloading the MIB file
 - Setting up rules for event notifications
 - Adding, modifying, or removing Syslog server
 - Modifying the purge setting for logs and SNMP traps
 - Enabling or disabling telemetry collection
 - Showing domains on login screen
 - Downloading log files
 
 - Managing user authentication and permissions
- About user authentication in the web console
 - About user permissions in the web console
 - Predefined personas
 - Configuring authentication domains
 - Unconfiguring authentication domains
 - Editing authentication domains
 - Configuring user groups and users
 - Assigning permissions to user groups and users
 - Adding custom personas
 - Predefined jobs that can be used for custom personas
 - About limiting object scope for personas
 - Configuring Windows global user
 
 
 - Managing settings for alerts and notifications and miscellaneous product settings
 
 - Manage settings
 - Section VII. Working with resiliency groups
- Organize assets
- Viewing your assets
 - Managing resiliency groups
 - About resiliency groups with assets
 - Configuring a resiliency group for basic monitoring
 - Editing a resiliency group
 - Deleting a resiliency group
 - Starting a resiliency group
 - Stopping a resiliency group
 - Placing a resiliency group in maintenance mode
 - Editing a resiliency group in maintenance mode
 - Viewing resiliency group details
 
 - Manage virtual business services
- Managing virtual business services
 - About virtual business services
 - Creating a virtual business service
 - Editing a virtual business service
 - Deleting a virtual business service
 - Refreshing a virtual business service
 - Displaying virtual business service details
 - Starting and stopping a virtual business service
 
 - Organize applications
- Managing applications using Resiliency Platform
 - About resiliency groups with applications
 - Providing inputs for partially discovered applications
 - About application bundles
 - Installing an application bundle on selected application hosts
 - Enabling and disabling application bundle on selected application hosts
 - Managing auto-deploy for an application bundle
 - Uninstalling an application bundle from selected hosts
 - Removing an application bundle
 - Editing the discovery schedule for an application type
 - Viewing the details of application types
 - Viewing the applicable host details
 - About resiliency groups with InfoScale applications
 - Viewing InfoScale applications details
 - Managing applications for basic monitoring
 
 - Managing service objectives
 
 - Organize assets
 - Section VIII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Understanding the role of resiliency groups in disaster recovery operations
 - About ensuring the disaster recovery readiness of your assets
 - How Resiliency Platform configures disaster recovery protection for virtual machines
 - How Resiliency Platform Data Mover handles DR operations
 - Support for 128 SCSI disks for Replication Gateway of hardware version 14
 - About manual intervention
 - Limitations for virtual machine disaster recovery
 - Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
 - Prerequisites for configuring Hyper-V virtual machines for recovery to AWS
 - Replication Gateway pair selection options
 - Volume type selection options
 - Enable reverse replication option
 - AWS Customization options panel
 - Network customization options
 - Prerequisites for network customization
 
 - 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
- Prerequisites for recovering VMware virtual machines using Resiliency Platform Data Mover in Hypervisor mode
 - Prerequisites for recovering VMware virtual machines using Resiliency Platform Data Mover in In-guest mode
 - Replication Gateway pair selection options for on-premises data center
 - Target Infrastructure Selection options
 
 - Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
 
 - Configure using NetBackup
- Prerequisites for configuring VMware virtual machines for recovery using NetBackup images
 - Support for NetBackup Classic AIR configurations
 - Support for NetBackup Instant Access to recover a resiliency group
 - Managing VMware virtual machines for remote recovery using NetBackup images
 - Managing VMware virtual machines for remote recovery to AWS cloud using NetBackup images
 - Managing the virtual machines for recovery to Azure using NetBackup MSDP-C.
 - Support for NetBackup MSDP-C and Resiliency Platform Data Mover for configuring resiliency group
 
 - Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Configuring VMware virtual machines for disaster recovery using EMC SRDF replication
 - Configuring VMware virtual machines for disaster recovery using EMC RecoverPoint replication
 - Configuring VMware virtual machines for disaster recovery using NetApp SnapMirror
 - Configuring VMware virtual machines for disaster recovery using Hitachi True Copy replication
 - Configuring VMware virtual machines for disaster recovery using HPE 3PAR Remote Copy replication
 - Configuring VMware virtual machines for disaster recovery using IBM SVC Global Mirror replication
 - Configuring VMware virtual machines for disaster recovery using IBM XIV Remote Mirror replication
 
 - Preparing Hyper-V virtual machines for using array-based replication
- Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
 - Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
 - Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
 - Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
 - Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
 - Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
 - Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
 - Configuring Hyper-V virtual machines for disaster recovery using Infinidat replication
 
 - Managing virtual machines for remote recovery (DR) using 3rd party replication technology
 - Managing applications for remote recovery (DR)
- Prerequisites for configuring applications for disaster recovery
 - Prerequisites for configuring InfoScale applications for disaster recovery
 - Prerequisites for creating a remote recovery resiliency group for Oracle database replicated by Data Guard
 - Configuring applications for disaster recovery using EMC RecoverPoint replication
 - Configuring applications for disaster recovery using NetApp SnapMirror replication
 
 
 - 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
- Rehearse operations for VMware virtual machines - array-based replication
 - Rehearse operations for Hyper-V virtual machines - array-based replication
 - Performing the rehearsal operation for virtual machines
 - Performing the rehearsal operation using NetBackup images
 - Performing the rehearsal operation on virtual machines from VMware to AWS using NetBackup Image Sharing
 - Performing rehearsal operation on resiliency groups configured with multiple recovery points
 
 - Performing cleanup rehearsal for virtual machines
 - Migrating a resiliency group
 - Performing the resync operation for virtual machines
 - Performing the recover operation for resiliency group
- Recovering a resiliency group using replication-based recovery
 - Recovering data using NetBackup to on-premises data center
 - Recovering virtual machines with multiple recovery points
 - Recovering virtual machines to cloud (AWS) using NetBackup Image Sharing
 - Recovering virtual machines to cloud (Azure) using NetBackup MSDP-C
 
 - Clearing outage
 
 - About Rehearse operation
 - Perform DR operations on a VBS
 - Perform DR operations for applications
 - Evacuate assets
 - Manage Resiliency Plans
- Managing resiliency plans
 - About resiliency plans
 - Creating a new resiliency plan template
 - Editing a resiliency plan template
 - Deleting a resiliency plan template
 - Viewing a resiliency plan template
 - Creating a new resiliency plan
 - Editing a resiliency plan
 - Deleting a resiliency plan
 - Executing a resiliency plan
 - Viewing a resiliency plan
 - Instances to invalidate the R-Plan
 - Creating a schedule for a resiliency plan
 - Editing a schedule for a resiliency plan
 - Deleting a schedule for a resiliency plan
 - Viewing a schedule for a resiliency plan
 - About manual task
 - Using manual tasks in 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
- Adding, modifying, or deleting email settings
 - Adding, modifying, or deleting SNMP settings
 - Throttling the notifications
 - Downloading the MIB file
 - Setting up rules for event notifications
 - Adding, modifying, or removing Syslog server
 - Modifying the purge setting for logs and SNMP traps
 - Modifying the purge setting for reports
 - Modifying the purge setting for activities
 - Enabling or disabling telemetry collection
 - Showing domains on login screen
 
 
 - Section XII. Using Resiliency Platform APIs
 - Section XIII. Troubleshooting and Using command line interface
- Troubleshoot
- Troubleshooting: Google Cloud Platform issues
 - Troubleshooting: Disaster recovery from AWS region to AWS region
 - Troubleshooting: Automated disaster recovery to Azure using NetBackup MSDP-C
 - Recovery of Resiliency Platform components from disaster scenarios
 - Troubleshooting : Issues occurred while prepare host for replication or while configuring resiliency group.
 - Troubleshooting: Resync/repair replication issues for resiliency group configured using Multi-RPO recovery of hosts service objective
 - Troubleshooting: NetBackup issues
 - Troubleshooting: Removing a Resiliency Manager from a resiliency domain
 - Resolving the Admin Wait state
 - Troubleshooting: Delete resiliency group operation
 - Troubleshooting: Deployment of virtual appliances in Azure
 - Troubleshooting: Copy file into the virtual appliance
 - Troubleshooting: Copy file from the virtual appliance
 - Manually cleaning up virtual machines
 - Troubleshooting: IP customization
 - Configure DR operation fails with an integration services error
 - Resiliency Platform fails to attach storage policy to virtual machines
 - Resiliency Platform fails to create storage policy
 - Troubleshooting: Discovery of assets
 - Troubleshooting: Hosts not added to IMS after migration to cloud data center
 - Troubleshooting: Connection between Resiliency Managers in a resiliency domain
 - Troubleshooting: DR operation failure with error message cannot change host configuration at VMware detach disk(s) subtask
 - Troubleshooting: If datastores are renamed
 - Troubleshooting: Migrate operation
 - Troubleshooting: Recover operation
 - Troubleshooting: Recover operation in case of add/remove disks
 - Troubleshooting: Failure to add IMS
 - Troubleshooting: Replace Replication Gateway operation
 - Troubleshooting: klish commands for Resiliency Manager, IMS, or Replication Gateway
 - Troubleshooting: In Hyper-V guest environment writeable disk is shown as Read-only
 - Troubleshooting: Steps to manually remove addon from hosts managed under Resiliency Platform
 - Troubleshooting: Aborting the on-going activities / tasks
 - Troubleshooting: AWS marketplace deployment with Data Gateway
 - Troubleshooting: Cleaning up of stale Resiliency Platform configurations
 - Troubleshooting: Preparing appliance for upgrade
 - Troubleshooting : Issues while detaching and attaching data disk
 - Troubleshooting: Issue while uploading the correct root certificate in vCloud Director
 - Troubleshooting: Replication Gateway appliance
 - Troubleshooting: Evacuation plan failed with exceptions raised by ERS.
 
 - Use klish menu
 - Use Application Enablement SDK
 
 - Troubleshoot
 - Glossary
 
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.