Veritas™ Resiliency Platform 2.2 Deployment Guide
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
Applying update on Resiliency Managers
You can apply an update on a Resiliency Manager using the klish menu options. Applying update on a Resiliency Manager using the Resiliency Manager console is not supported.
If you have two Resiliency Managers in your resiliency domain then you need to apply the update on both the Resiliency Managers in synchronization.
For the purpose of upgrade, one of the Resiliency Managers is designated as import node and the other one as non-import node:
The first Resiliency Manager configured in the resiliency domain is called the import node. If the first Resiliency Manager is no longer in the resiliency domain, then the Resiliency Manager configured next in the domain is designated as the import node.
The other Resiliency Manager in the domain is called the non-import node.
If you do not remember the sequence in which the Resiliency Managers are configured in the domain, you can start applying the update on any one of the Resiliency Managers and the process will guide you about the import node and non-import node.
Note:
Upgrade to version 2.2 is not supported for a virtual appliance that has been configured as Resiliency Manager as well as IMS.
To apply update on Resiliency Managers
- Start the process of applying update on the non-import node. Wait until upgrade on the non-import node reaches to a stage where you are prompted to switch to the import node.
- Start the process of applying update on the import node. Once the upgrade process completes successfully, verify that all the Resiliency Manager services are running on the import node by running following klish command on the import node:
manage> services rm show
If the upgrade on the import node fails, you need to stop all the Resiliency Manager services to avoid the data loss by running following klish command on the import node:
manage> services rm stop ALL
- Now switch to the non-import node and resume the upgrade there.
In case the upgrade on import node had failed, you need to take the non-import node offline as soon as the upgrade on the non-import node completes, irrespective of success or failure of the upgrade.