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

ManualsBrandsHP ManualsSoftwareHP Matrix Operating Environment w/Insight Control 24x7 Supp Flexible Lic

Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM)

Technical white paper

Matrix Co-Existence with

VMware vCenter Site Recovery

Management (SRM)

Table of contents

Introduction .................................................................................................................................................................................... 2

SRM high-level overview ............................................................................................................................................................. 2

What happens during a failover operation .......................................................................................................................... 2

Configuring protection after a failover ................................................................................................................................. 3

Tested configuration .................................................................................................................................................................... 3

Known issue when using HP Capacity Advisor ................................................................................................................... 3

Limitations when using a two CMS configuration .............................................................................................................. 3

VMs with RDM disks not tested .............................................................................................................................................. 4

Configuration changes required before using Matrix with SRM .......................................................................................... 4

Edit the hpio.properties file .................................................................................................................................................... 4

Edit the vmmController.properties file and the lsa.properties file ................................................................................ 4

Failover processes in a one CMS configuration ...................................................................................................................... 5

SRM Planned Migration failover steps when using one CMS ........................................................................................... 5

SRM Disaster Recovery failover steps when using one CMS ........................................................................................... 6

Complete SRM Disaster Recovery and return environment back to normal state when using one CMS.............. 7

Failover processes in a two CMS configuration ...................................................................................................................... 8

SRM Planned Migration failover steps when using a two CMS configuration .............................................................. 8

SRM Disaster Recovery failover steps when using a two CMS configuration .............................................................. 8

Complete SRM Disaster Recovery when using a two CMS configuration ..................................................................... 9

Resolving Matrix inconsistencies after a failover ................................................................................................................. 10

Corrective steps ....................................................................................................................................................................... 10

Procedures to Identify an ESXi host .................................................................................................................................... 11

Capturing HP Capacity Advisor data from VMs on secondary site .................................................................................... 11

For more information ................................................................................................................................................................. 12

Resources, contacts, or additional links............................................................................................................................. 12

Summary of content (12 pages)

PAGE 1
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) Technical white paper Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) Table of contents Introduction .................................................................................................................................................................................... 2 SRM high-level overview ....................................................................................
PAGE 2
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) Introduction The Matrix Operating Environment 7.3 Update 2 release provides co-existence with VMware vCenter Site Recovery Manager (SRM). This white paper documents the necessary steps to follow for the Matrix Operating Environment to co-exist with SRM. Prior to using SRM and Matrix together, there are some minor configuration steps that must be done.
PAGE 3
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) After the recovery failover operation is complete, the VMs will be running on the recovery site and the VMs are no longer being protected by SRM. Configuring protection after a failover In the case of a Planned Migration failover, after the Recovery operation completes SRM will inform you that it’s necessary to configure protection again.
PAGE 4
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) 1. If you add a new disk to the VM, IO will not be aware of it when you fail back to the primary site. 2. If you add a new VM: 3. A. Matrix will recognize that the VM exists when you failback to the primary CMS; however it will not be recognized as a logical server or as part of an IO service. B. If the VM meets the criteria, it can be imported as part of a new IO service. C.
PAGE 5
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) Failover processes in a one CMS configuration After an SRM Recovery operation (i.e. failover) has been completed, the VMs are powered on and accessible on the recovery site. However, to synchronize Matrix and to use the functionality of Matrix prior to the automatic and periodic component refresh operations, you must perform the steps outlined below.
PAGE 6
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) 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.
PAGE 7
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) 6. In the Matrix OE Physical and Virtual perspective, verify that the “live” VMs are displayed under the correct ESXi host as shown in vCenter. Do not be concerned about the hosts or VMs on the protected site (where the VMs were running prior to the DR failover) until after the Recovery/Reprotect operations have been completed. If there are any issues, resolve them before continuing to the next step.
PAGE 8
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) 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.
PAGE 9
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) 1. In SRM, click on Recovery in the Recovery Plans screen, and then select the Disaster Recovery failover 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.
PAGE 10
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) Resolving Matrix inconsistencies after a failover After an SRM failover, it is important to synchronize Matrix with vCenter and to resolve any errors or inconsistencies within Matrix itself. You may observe one or more of the following errors. • In the Matrix OE Logical Servers perspective: – One or more logical servers may appear as inactive, inoperable, or active on unknown host.
PAGE 11
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) 5. E. In the Matrix OE Logical Server perspective, click on the green refresh symbol (double arrows) to refresh the display. F. Verify that the logical server is now displaying the appropriate icons. Once all the logical server issues are resolved, verify that all VMs are associated with their correct ESXi host in the Matrix OE Physical and Virtual perspective.
PAGE 12
Technical white paper | Matrix Co-Existence with VMware vCenter Site Recovery Management (SRM) For more information Resources, contacts, or additional links For more information about the HP Matrix Operating Environment, see the documentation at: www.hp.com/go/matrixoe/docs For more information about VMware vCenter Site Recovery Management, see the documentation at: https://pubs.vmware.com/srm-51/index.jsp?topic=%2Fcom.vmware.ICbase%2FWelcome%2Fwelcome.html Learn more at hp.