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 removing a Resiliency Manager from a resiliency domain
In some cases you may want to remove a Resiliency Manager node from a resiliency domain.
Before removing a Resiliency Manager node, you should first remove the Resiliency Manager from the resiliency domain using the Leave Domain operation in the Veritas Resiliency Platform web console. Completing this operation ensures that the Resiliency Manager is cleanly decommissioned and that all references to it are removed from the Resiliency Manager database and no longer appear in the web console user interface. The Leave Domain operation has prerequisites that are documented in the procedure topic.
See Removing a Resiliency Manager from a resiliency domain.
The following gives more details for trouble scenarios, for example, if the Resiliency Manager you want to remove is not online or if the operation does not complete successfully.
Unable to bring the Resiliency Manager online | The Leave Domain operation requires that both Resiliency Managers be online. However, if you are unable to bring the Resiliency Manager you want to remove online, there is no problem with leaving it in a down state. The resiliency domain and other infrastructure components continue to function. If an Infrastructure Management Server (IMS) was connected to the Resiliency Manager that was down, the IMS will automatically reconnect itself to another Resiliency Manager in the same domain. In addition, you can add another Resiliency Manager and join it to the domain. |
Unable to complete Leave Domain operation | The Leave Domain operation is a multistep process. First the Resiliency Manager decommissions itself. Then all references to it are removed from the Resiliency Manager database. Finally any IMS connected to the decommissioned Resiliency Manager is rerouted to another Resiliency Manager. You can use the Activities pane to verify that the Leave Domain operation completes. If the process fails before all steps are complete, the partially removed Resiliency Manager no longer operates. However, the resiliency domain continues to function. |