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
Troubleshooting the connection between Resiliency Managers in a resiliency domain
Multiple Resiliency Managers that are part of the same domain synchronize their databases using built-in replication. Each Resiliency Manager has its own web console but because the data is synchronized, all consoles show the same data. Operations can be performed from any console and the results show in all the consoles in the resiliency domain.
In some cases the connection is lost between Resiliency Managers. In such a case, if you login to the console, a message is displayed to warn you about this and request that you confirm whether the other Resiliency Manager is down (outage).
If the Resiliency Manager administrator confirms that the other Resiliency Manager is down, you can click the confirmation on the message box and continue working on the console. When the other Resiliency Manager is brought up, the changes are synchronized.
However, if you check and the other Resiliency Manager is not down, the problem is in the network connection. In this case, you should not attempt to work in the Resiliency Manager console until the network connection is restored.