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
- Recovering virtual machines to AWS
- Recovering virtual machines to Azure
- Recovering virtual machines to Google Cloud Platform
- Recovering virtual machines to vCloud Director
- Recovering virtual machines to Orange Recovery Engine
- Recovering physical machines using Resiliency Platform
- 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 Orange Recovery Engine
- Checklist for recovery of virtual machines to Google Cloud Platform
- Checklist for recovery of virtual machines to vCloud Director
- 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
- Deploying virtual appliances in vCloud Director
- Deploying the virtual appliances in Orange Recovery Engine
- 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 Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- 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
About applying updates to Resiliency Platform
Updates to Veritas Resiliency Platform provide significant benefits, such as improved functionality, performance, security, and reliability.
Updating the Resiliency Platform (Resiliency Manager and IMS) involves saving configuration to the data disk of the previous version appliance and then attaching the data disk to a new, freshly deployed virtual appliance.
For more details, refer the below topics:
About deploying the Resiliency Platform virtual appliances About deploying the Resiliency Platform virtual appliances
Deployment workflows Deployment workflows
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 10.0 is the minimum version supported for upgrade to version 10.3. If your installed version is older than minimum supported version, then you should first upgrade to your supported upgrade version.
Appliances should be upgraded in following sequence:
All Resiliency Manager appliances
All IMS appliances
All Replication Gateway appliances
All managed hosts
Table: Upgrade path for Veritas Resiliency Platform 10.3
Current version | Can upgrade to |
---|---|
v10.1.0.0 | v10.3 |
v10.2.0.0 | v10.3 |
Following are some considerations for applying update to the Resiliency Platform components:
The minimum version of the virtual appliances should be 10.1 or 10.2 to upgrade to Resiliency Platform 10.3.
You must apply the updates on Resiliency Manager and IMS to take the complete advantage of the changes available in the updates. You need to replace the Replication Gateway to reflect the new upgrade changes in version 10.3.
Ensure that no workflow or resiliency plans are running in the background.
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.
A pre-upgrade checklist is integrated with the prepare-for-update command to validate the virtual appliance. This checklist is applicable to Resiliency Manager only. For more details, refer Pre-upgrade checklist
The Resiliency Platform upgrade process is divided into 3 main parts. The upgrade process is applicable for the following platforms:
Upgrading Resiliency Platform in AWS environment
Upgrading Resiliency Platform in Azure environment
Upgrading Resiliency Platform in VMware environment
Upgrading Resiliency Platform in Hyper-V environment
The detail steps are mentioned according to the respective topics based on the environments. The high level overview of the process for applying updates to the virtual appliances of the Resiliency Platform in version 10.3 is mentioned below:
Using KLISH commands, prepare the virtual appliances for upgrade.
Detach the data disk of the existing virtual appliance and attach the data disk of the virtual appliance to the new 10.3 appliance.
Boot the virtual appliance to start the automatic bootstrap process based on the environment you want to upgrade.
In case of Replication Gateway upgrade, you need to replace the existing Replication Gateway with the newer version Replication Gateway.
Before applying updates, ensure that you have performed pre-upgrade tasks for specific scenarios:
See Pre-upgrade tasks.
The following table consists of the topics you need to refer to the steps mentioned above for applying updates in Veritas Resiliency Platform:
Table: Applying updates to Resiliency Platform
Step | Task | Steps to perform the task |
---|---|---|
1 | Prepare for update using Klish commands. Prepare the virtual appliances for update using Klish commands. | |
2 | Detach / attach data disk. You need to perform following steps:
Choose the environment from the list on which you wish to upgrade the Resiliency Platform. | Step 2: Upgrading the Resiliency Platform (Detach / attach the disk) |
3 | Start Automatic bootstrap process. After the bootstrap process is complete, the upgrade process should automatically start. | |
4 | Replace the Replication Gateway appliance | Steps to replace the Replication Gateway appliance For modifying the encryption: |
5 | Apply update to the single or multiple Resiliency Managers in a domain. 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. |
Apart from upgrading the Resiliency Platform virtual appliances, you need to update following other components too:
Table: Applying updates to other components of Resiliency Platform
Task | Steps to perform the task |
---|---|
Apply update on the host packages. You must apply update to the Control Host after you apply update to the IMS. | |
Apply update on the InfoScale environment In case of InfoScale environment, apply update to the add-on. | Applying upgrade to Resiliency Platform for managing InfoScale clusters |
Upgrading the Veritas Replication VIB 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. | |
Applying updates to the Veritas Data Gateway |
You also have an option of applying a private hotfix, if Veritas support provides you one.
See About hotfixes.