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
- Setting up the resiliency domain
- About the web console
- Connecting to the Resiliency Platform web console
- Getting started with a new Resiliency Platform configuration
- Adding a Resiliency Manager to an existing resiliency domain
- Removing a Resiliency Manager from a resiliency domain
- Viewing the status of a Resiliency Manager in a data center
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- About NetBackup and NetBackup Appliances
- About protecting assets with NetBackup using Resiliency Platform
- Using NetBackup - an overview
- Prerequisites for integrating NetBackup with Resiliency Platform
- Adding NetBackup master server
- Adding IMS to NetBackup master server as an additional server
- Editing the NetBackup master server
- Removing the NetBackup master server
- Removing IMS from NetBackup master server
- Refreshing the NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- About Veritas InfoScale Operations Manager
- Resiliency Platform support for InfoScale applications
- Managing InfoScale applications using Resiliency Platform
- Support matrix for InfoScale applications
- Prerequisites for managing Veritas InfoScale Operations Manager server using Resiliency Platform
- Adding a Veritas InfoScale Operations Manager server
- Regenerating registration URL for a Veritas InfoScale Operations Manager server
- Deleting a Veritas InfoScale Operations Manager server
- Editing the details of a Veritas InfoScale Operations Manager server
- Reconnecting the Veritas InfoScale Operations Manager to a Resiliency Manager
- Managing Resiliency Platform Data Mover gateway pairing
- Viewing Veritas Replication Gateways
- About Veritas Replication Gateway pairs
- How Resiliency Platform Data Mover supports encryption for data replication
- Creating a Veritas Replication Gateway pair
- Removing a Veritas Replication Gateway pair
- Viewing Veritas Replication Gateway pairs
- Modifying encryption for a Veritas Replication Gateway pair
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Asset infrastructure use cases
- Adding asset infrastructure for Hyper-V virtual machines
- Adding asset infrastructure for VMware virtual machines
- Adding asset infrastructure for application discovery on Hyper-V virtual machines
- Adding asset infrastructure for application discovery on VMware virtual machines
- Adding asset infrastructure for application discovery on physical systems
- Adding the asset infrastructure
- Managing host assets
- Managing Hyper-V assets
- Managing VMware virtualization servers
- Managing enclosure assets
- Preparing and maintaining host assets
- About adding host assets
- Prerequisites for adding hosts
- Adding a Windows Install host
- Installing the host package on a Windows host
- Adding application hosts
- Preparing host for replication
- Removing hosts
- Refreshing host discovery information
- Uninstalling the host package from a Linux host
- Uninstalling the host package from a Windows host
- Managing Hyper-V virtualization server assets
- About Microsoft Hyper-V virtualization discovery
- Prerequisites for Microsoft Hyper-V virtualization discovery
- Adding Hyper-V virtualization servers
- Removing Hyper-V virtualization servers
- Refreshing Hyper-V virtualization servers
- Configuring asset infrastructure for replication for Hyper-V virtual machines
- Managing VMware virtualization server assets
- Prerequisites for adding VMware virtualization servers
- VMware vCenter Server privileges required for implementing Resiliency Platform Data Mover
- About near real-time discovery of VMware events
- Setting up near real-time discovery of VMware events
- Configuring the VMware vCenter Server to generate SNMP traps
- About adding a host for discovery of VMware 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 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
- Editing the discovery configuration for an enclosure
- Removing the discovery configuration for an enclosure
- Refreshing enclosure discovery information
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Managing user authentication and permissions
- About user authentication in the web console
- About user permissions in the web console
- Predefined personas
- About limiting object scope for personas
- Configuring authentication domains
- Editing authentication domains
- Unconfiguring authentication domains
- Showing domains on login screen
- Configuring user groups and users
- Assigning permissions to user groups and users
- Adding custom personas
- Predefined jobs that can be used for custom personas
- Configuring Windows global user
- Managing service objectives
- Managing reports
- Managing settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Adding, modifying, or deleting email settings
- Adding, modifying, or deleting SNMP settings
- 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
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- About updating Resiliency Platform
- About applying updates to Resiliency Platform
- Prerequisites for a repository server
- Downloading the Resiliency Platform update
- Using YUM virtual appliance as YUM server
- Setting up the repository server
- Adding a repository server in Resiliency Platform
- Assigning a repository server in Resiliency Platform
- Applying updates to virtual appliances using the console
- Applying updates to virtual appliance using klish menu
- Applying update on Resiliency Managers
- Applying update for InfoScale environment
- Applying updates to Resiliency Platform Data Mover bundle
- Applying updates to the hosts
- Removing an update from the repository server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Viewing events and logs in the console
- Accessing Resiliency Platform log files
- Displaying risk information
- About the Resiliency Manager services
- Components of Resiliency Platform virtual appliance
- Troubleshooting discovery of assets
- About the frequency of asset information discovery
- Troubleshooting the connection between Resiliency Managers in a resiliency domain
- Troubleshooting removing a Resiliency Manager from a resiliency domain
- Manually recovering the replication gateway
- Using Veritas Services and Operations Readiness Tools to find a Unique Message Identifier description and solution
- Troubleshooting and maintenance
- Section VIII. Reference
- Glossary
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.