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

Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM)
8
7. In the Matrix Operating Environment, execute the C:\ioexec sync logicalservers command on the CMS.
8. (Optional) In SRM, do an SRM Planned Migration failover back to the original (primary) site. Follow the steps
documented in the section “SRM Planned Migration failover steps when using one CMS.”
Failover processes in a two CMS configuration
The process for doing an SRM failover (Planned Migration or Disaster Recovery) is the same in SRM whether you have one or
two CMS systems. However, due to the limitations of a two CMS configuration, there are fewer steps to do in Matrix.
SRM Planned Migration failover steps when using a two CMS configuration
As previously stated, a Planned Migration failover would typically be done when there are no problems on the protected site
that are requiring the failover to take place. This operation could be done to test the SRM failover process or to move the
workloads to the other site in order to do some type of maintenance activity or load balancing.
1. In SRM, click on Recovery in the Recovery Plans screen, and then select the Planned Migration failover option to failover
from the protected site to the recovery site.
2. In SRM, click on Reprotect in the Recovery Plans screen to configure protection again after Recovery operation
completes.
Note
This reverses which site is considered to be the protected and recovery site. Also note that the datastore names will
have been changed when using 3PAR arrays.
3. In the Matrix Operating Environment, select Tools -> Logical Servers -> Refresh, and then select SIM and VMM
resources.
Even though the VMs are not recognized as logical servers, this operation will cause SIM and VMM to refresh their
information about the ESXi hosts and VMs running on them.
4. In the Matrix OE Physical and Virtual perspective, verify that the protected (or live) VMs are displayed under the correct
ESXi host as shown in vCenter.
Note
There will be no visibility from the secondary CMS to the ESXi hosts or the placeholder shadow VMs on the primary site.
If there are any issues:
A. Do an Identify operation on the affected ESXi hosts. In SIM, select Options -> Identify Systems.
B. Do another Logical Servers Refresh.
C. In Matrix Operating Environment, select Tools -> Logical Servers -> Refresh, and then select SIM and VMM
resources.
5. When you are ready, do an SRM Planned Migration failover back to the primary site. Refer to the earlier section “SRM
Planned Migration failover steps when using one CMS.” The steps are the same.
If you are using HP Capacity Advisor to collect performance data for the VMs, after failing back to the primary site it is
necessary to do some manual steps to capture the performance data collected for the VMs while they were running on
the secondary site and to integrate it with the data on the primary site. Refer to the section entitled “Capturing HP
Capacity Advisor data from VMs on secondary site.”
SRM Disaster Recovery failover steps when using a two CMS configuration
As stated previously, 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. system crash, SAN access problem) or some other problem in the environment.