Veritas™ Resiliency Platform 2.2 Solutions for VMware
- Section I. Overview of Resiliency Platform
- Overview of Resiliency Platform
- Overview of Resiliency Platform Data Mover
- Overview of recovery to on-premises data center
- Managing assets protected by NetBackup
- Overview of Amazon Web Services
- Overview of vCloud
- Section II. Preparing your environment
- Using array-based replication
- Using Veritas Resiliency Platform Data Mover
- Managing disaster recovery network mapping
- Managing Replication Gateway pairs
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing resiliency groups
- Section IV. Managing disaster recovery
- Rehearsing DR operations to ensure DR readiness
- Performing disaster recovery operations
- Rehearsing DR operations to ensure DR readiness
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activities
- Managing evacuation plans
- Appendix A. General troubleshooting
- Resolving the Admin Wait state
- Appendix B. Sample policy and trust relationships for AWS
Troubleshooting discovery of assets
When asset infrastructure is added to the Infrastructure Management Server (IMS), or when changes are made to the infrastructure, the IMS discovers and correlates the asset information and displays the information on the Assets page of the Resiliency Platform console. The discovery can take some time before the information is updated on the console. Until discovery is complete, some information needed to configure resiliency groups may be missing from the Assets page on the console.
If changes have been made to the asset infrastructure, you can use the Refresh operation on the assets to speed up discovery so that updated asset information is displayed more quickly in the console. To use the Refresh operation, right-click the asset and select Refresh.
Note:
Occasionally, the data discovered from the Infrastructure Management server (IMS) may not be updated properly in the Resiliency Manager database. This situation may result in displaying incorrect information about the resiliency group state, replication state, and replication type. In such a case, refresh the appropriate assets in both the data centers.
If you are configuring replication using storage arrays in a VMware vCenter Server environment, you can use the following guidelines to speed up discovery or to troubleshoot information that is not being updated:
Table: Configuring asset infrastructure in IMS for storage arrays in VMware environment
Situation | Troubleshooting/best practices |
---|---|
Adding storage arrays as enclosures to IMS | Ensure that the storage arrays that are added to the IMS are the ones that provide storage to the ESX servers managed by the vCenter Server that is added to the IMS. |
More than one IMS in data center | Ensure that the vCenter Server that is managing the ESX servers, and the enclosure providing storage to those servers, are added to the same IMS. |
Refreshing the IMS after a change in infrastructure | Ensure that you use the Refresh operation on the correct vCenter Servers and enclosures where the change was made. |
Refreshing the IMS after a change in infrastructure, where there is more than one IMS | Ensure that you use the Refresh operation in the correct IMS. |
In the VMware and EMC SRDF environment, the general guideline is to add/refresh the enclosure before adding/refreshing the VMware vCenter Server.
Table: Configuring or refreshing asset infrastructure in IMS for VMware and EMC SRDF environment
Situation | Recommended sequence |
---|---|
You have not yet added the asset infrastructure. | Add the enclosure information in the IMS and let the discovery complete before adding the vCenter Server to the IMS. |
You later provision new storage from an enclosure that is already configured in the IMS and mount datastores from the new storage. | Refresh the enclosure in the IMS, let the refresh task on the enclosure complete, and then refresh the vCenter Server in the IMS. |
You provision storage from a new enclosure. | Add the new enclosure in the IMS and then refresh the vCenter Server after the enclosure discovery completes. |
You are provisioning storage from an enclosure that is already configured in the IMS to new ESX servers managed by a vCenter Server. | Refresh the enclosure first, then add the vCenter Server to the IMS or refresh it if it is already added to the IMS. |
In the VMware and NetApp SnapMirror environment, the general guideline is add/refresh the vCenter Server first, then add/refresh the NetApp enclosure.
Table: Configuring or refreshing asset infrastructure in IMS for storage arrays in VMware and NetApp SnapMirror environment
Situation | Recommended sequence |
---|---|
You have not yet added the asset infrastructure. | Add the vCenter Server to the IMS first and let the discovery complete before you add the NetApp enclosure. |
You later provision storage from an existing NetApp enclosure and mount NFS datastores on ESX servers. | Refresh the vCenter Server first in the IMS, let the discovery complete and then refresh the NetApp enclosure. |
You later provision storage from a new NetApp enclosure and mount NFS datastores on that ESX servers. | Refresh the vCenter Server first in the IMS, wait for the vCenter Server discovery to complete, and then add the new NetApp enclosure. |
The recommended sequence for adding or modifying asset infrastructure for application discovery in the NetApp SnapMirror replication environment is as follows: Ensure that discovery of the hosts is complete before you add or refresh the NetApp enclosures.
For more information on adding asset infrastructure and on the refresh operation in the IMS, refer to the Deployment Guide.