Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM)

Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM)
6
8. If you had stopped the HP Capacity Advisor Data Service, start it now. After 5-10 minutes, data collection for all of the
VMs should have started. You can verify that data is being collected for all of the VMs by issuing the following
command:
capprofile –ld
Review the output and make sure that there is a profile for each VM and that the date and time are after the time you
started the HP Capacity Advisor Data Service.
SRM Disaster Recovery failover steps when using one CMS
A Disaster Recovery failover would be done when there are problems with one or more of the ESXi hosts on the protected
site (e.g. ESXi host crash, SAN access problem) or some other problem in the environment.
1. If you are using HP Capacity Advisor to collect performance information for your virtual machines, stop the HP Capacity
Advisor Data Service Windows service.
Note
This step must be done prior to initiating the failover operation. Failure to do this step may cause database
inconsistencies that will prevent future data collection for one or more VMs.
2. In SRM, click on Recovery in the Recovery Plans screen, and then select the Disaster Recovery option to failover from
the protected site to the recovery site.
Note
Errors will occur when trying to shut down the VMs on the protected site if any of the ESXi hosts are down or if the
hosts cannot access their datastores. This is expected. SRM will ignore these errors and the VMs will still be powered
up on the recovery site. Although the VMs are running again on the recovery site, they will not be protected by SRM at
this point.
SRM will inform you that once the problems on the protected site are corrected, you must do another Recovery
operation to complete the failover successfully.
3. IMPORTANT: In certain situations, Matrix OE is unable to know which is the “live” VM and will not know the correct host
and storage location of the VM. Therefore, it is necessary to do the following.
A. If one or more hosts are disconnected or offline, DO NOT bring them back online until you are ready to complete
the SRM Recovery operation.
B. If one or more hosts in a cluster cannot access their datastores, ALL of the hosts in that cluster MUST be shut
down until the problem is resolved and you are ready to complete the SRM Recovery operation.
4. In the Matrix Operating Environment, select Tools -> Logical Servers -> Refresh, and then select SIM and VMM
resources.
5. In the Matrix OE Logical Server perspective, click on the green refresh symbol (double arrows) to refresh the display.
Verify that all of the logical servers are displayed correctly as indicated below.
A. All are active.
B. None are inoperable or active on unknown host.
C. All have the correct host name or IP address.
D. All have the icons normally displayed for VM logical servers.
E. Click on the logical server details icon to verify that the logical server details reflect the correct host and storage
location as shown in vCenter.
If there are any issues, resolve them before continuing to the next step. Refer to the section “Resolving Matrix
inconsistencies after a failover.”