Veritas™ Resiliency Platform 2.2 Solutions for VMware
- Section I. Overview of Resiliency Platform
- Overview of Resiliency Platform
- Overview of Resiliency Platform Data Mover
- About Veritas Resiliency Platform Data Mover
- Supported environments for Resiliency Platform Data Mover with VMware VAIO
- How Resiliency Platform Data Mover works
- About Veritas Resiliency Platform Data Mover architecture
- About full synchronization with Veritas Resiliency Platform Data Mover
- How Veritas Resiliency Platform Data Mover handles virtual machine writes
- Using Resiliency Platform Data Mover for recovery to premises- an overview
- 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
- Supported replication technologies with Veritas Resiliency Platform
- Protecting VMware virtual machines using array-based replication - an overview
- Configuring VMware virtual machines for disaster recovery using EMC SRDF replication
- Configuring VMware virtual machines for disaster recovery using EMC RecoverPoint replication
- Configuring VMware virtual machines for disaster recovery using NetApp SnapMirror
- Configuring VMware virtual machines for disaster recovery using Hitachi True Copy replication
- Configuring VMware virtual machines for disaster recovery using HPE 3PAR Remote Copy replication
- Configuring VMware virtual machines for disaster recovery using IBM SVC Global Mirror replication
- Configuring VMware virtual machines for disaster recovery using IBM XIV Remote Mirror replication
- Using Veritas Resiliency Platform Data Mover
- Managing disaster recovery network mapping
- Managing Replication Gateway pairs
- About Veritas Replication Gateway pairs
- How Resiliency Platform Data Mover supports encryption for data replication
- Creating a Veritas Replication Gateway pair
- Modifying encryption for a Veritas Replication Gateway pair
- Viewing Veritas Replication Gateways
- Viewing Veritas Replication Gateway pairs
- Removing a Veritas Replication Gateway pair
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- About resiliency groups
- Guidelines for organizing resiliency groups
- About service objectives
- Managing virtual machines for basic monitoring
- Starting a resiliency group
- Stopping a resiliency group
- Displaying resiliency group information and status
- Viewing resiliency group details
- Editing a resiliency group
- Deleting a resiliency group
- Configuring resiliency groups for remote recovery
- Understanding the role of resiliency groups in disaster recovery operations
- How Resiliency Platform configures disaster recovery protection for virtual machines
- Prerequisites for configuring VMware virtual machines for disaster recovery
- Limitations for virtual machine disaster 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 virtual machines for remote recovery (DR) in vCloud
- Managing VMware virtual machines for remote recovery using NetBackup images
- Verifying the replication status for Veritas Resiliency Platform Data Mover
- Managing resiliency groups
- Section IV. Managing disaster recovery
- Rehearsing DR operations to ensure DR readiness
- About ensuring the disaster recovery readiness of your assets
- Rehearse operations - array-based replication
- Rehearse operations - Resiliency Platform Data Mover
- Prerequisites for rehearsal operation
- Performing the rehearsal operation
- Performing the rehearsal operation using NetBackup images
- Performing cleanup rehearsal
- Performing disaster recovery operations
- Rehearsing DR operations to ensure DR readiness
- Managing resiliency plans
- About resiliency plans
- Creating a new resiliency plan template
- Editing a resiliency plan template
- Deleting a resiliency plan template
- Viewing a resiliency plan template
- Creating a new resiliency plan
- Editing a resiliency plan
- Deleting a resiliency plan
- Executing a resiliency plan
- Viewing a resiliency plan
- Creating a schedule for a resiliency plan
- Editing a schedule for a resiliency plan
- Deleting a schedule for a resiliency plan
- Viewing a schedule for a resiliency plan
- Monitoring risks, reports, and activities
- Managing evacuation plans
- Appendix A. General troubleshooting
- Viewing events and logs in the console
- Events in VMware virtual machines disaster discovery
- Troubleshooting discovery of assets
- Log files to troubleshoot Veritas Resiliency Platform Data Mover
- Managing tunable parameters
- Resiliency Platform fails to attach storage policy to virtual machines
- Resiliency Platform fails to create storage policy
- Resolving the Admin Wait state
- Troubleshooting NetBackup issues
- Troubleshooting delete resiliency group operation
- Appendix B. Sample policy and trust relationships for AWS
- Glossary
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.