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
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- 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
- Integrating with InfoScale Operations Manager
- 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 Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. 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) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- 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) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- 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 VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- 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 IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
About applying updates to Resiliency Platform
Updates to Veritas Resiliency Platform provide significant benefits, such as improved functionality, performance, security, and reliability.
In Veritas Resiliency Platform, you can apply updates to the following:
Veritas Resiliency Platform virtual appliance
Veritas Resiliency Platform add-ons
Host packages on the assets that are added to the Infrastructure Management Server (IMS) as a host
Veritas Replication VIB
Veritas Resiliency Platform 3.2 is the minimum version supported for upgrade to version 3.4.0.0. If your installed version is older than minimum supported version, then you should first upgrade to your latest available version.
Appliances should be upgraded in following sequence:
All RM appliances
All IMS appliances
All GW appliances
All managed hosts
Following are some considerations for applying update to the Resiliency Platform components:
It is recommended to power off and take a snapshot of the appliances before applying the updates on the Resiliency Manager and IMS virtual appliances. Do not take a snapshot of the Replication Gateway appliance.
You must apply the update to all the Resiliency Platform components to take the complete advantage of the changes available in the updates.
All the updates should be downloaded and stored in a common Document Root of the YUM repository server.
While applying updates, ensure that the virtual appliance remains powered on. Restarting the appliance during the process of applying updates may adversely affect the functionality and the virtual appliance may go into an irrecoverable condition. Also ensure to set keep-alive setting for the client if you are using SSH to connect to the virtual appliances.
During the process of upgrade, the appliance may get restarted if there are kernel updates involved.
After applying updates, you can access the Resiliency Manager web user interface through the NIC that is used for communication with other Resiliency Manager.
You can change the NICs that are used to access product user interface. Use network > nic-for-UI klish command to add additional existing configured NICs for UI access.
For applying updates to Resiliency Platform, you need to set up a repository server and download the updates to the repository server. Then, you assign the repository server to the Resiliency Platform virtual appliance, where you want to apply the update. The following figure shows how a repository server is used to apply the updates to Resiliency Platform:
The following is an overview of the process of applying updates in Veritas Resiliency Platform:
Table: Applying updates to Resiliency Platform
Step | Task | Steps to perform the task |
---|---|---|
1 | Before upgrade, you may need to perform certain operations for certain scenarios. | See Pre-upgrade tasks. |
2 | Download the update. | |
3 | Do one of the following:
| For setting up your own repository server: For using the YUM server as repository: |
4 | Apply update to the Resiliency Manager. In case of multiple Resiliency Managers in the domain, the update needs to be applied on all the Resiliency Managers in synchronization. Note that if you apply update to the resiliency Manager, then you must apply update to the IMS as well. If you do not update the IMS, the IMS stops data reporting to the Resiliency Manager. | For applying update on Resiliency Manager: |
5 | Apply update to the IMS at production data center and then to the IMS at recovery data center. you can use either klish menu or Resiliency Manager console for applying the update. You must apply update to the IMS if you have applied update to the Resiliency Manager. | For applying update on IMS: See Applying updates to virtual appliance using klish menu. See Applying updates to virtual appliances using the console. |
6 | After upgrading from 3.1 to a later version, AES256-GCM-SHA384 is the only available encryption scheme. Hence if AES128-GCM-SHA256 is applied to any Replication Gateway, you need to modify. The encryption scheme can be modified after the Resiliency Manager is updated and must be done before Replication Gateway is updated. | For modifying the encryption See Modifying encryption for a Replication Gateway pair. |
7 | Apply update to the Replication Gateway at recovery data center and then to the Replication Gateway at production data center. If the IMS associated with the Gateway has any version below 3.0, then the host package and the add-ons also need to be updated. | For applying update on Replication Gateway: See Applying updates to virtual appliance using klish menu. See Applying updates to virtual appliances using the console. For updating the host packages and add-ons on Replication Gateway: |
8 | Apply update on the host packages. You must apply update to the Control Host after you apply update to the IMS. | |
9 | In case of InfoScale environment, apply update to the add-on. | |
10 | In case of recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover, If you had configured a resiliency group before applying update to IMS, you need to apply update to the Data Mover bundle. | |
11 | Post upgrade you may need to perform certain operations for certain scenarios. | See Post upgrade tasks. |
You also have an option of applying a private hotfix, if Veritas support provides you one.