Uninstalling matrix recovery management, Setting up networking, Installing and licensing matrix recovery – HP Matrix Operating Environment Software User Manual
Page 9
NOTE:
•
It is assumed that networking and storage replication links are present between the Local Site
and the Remote Site.
•
When planning for disaster recovery solution using Matrix recovery management with VMware
hypervisor based IO services, proper planning is required to ensure the hosts at both the
primary and the remote sites match. For example, the hosts that have visibility to the replicated
volume that the IO service uses and can be selected to activate the replica services at the DR
site must be running a version equal to or higher than the primary site host on which the
original IO service was created. For example, if primary IO service was created on an ESX
5.5 host, the DR site ESX servers that have the replicated datastore mapped must be running
ESX5.5 or newer.
Installing and licensing Matrix recovery management
1.
Install the HP Matrix Operating Environment and dependent software on the Central
Management Server (CMS) at the Local Site and the Remote Site.
2.
Discover the managed infrastructure at each site from HP Systems Insight Manager.
3.
Apply the license for Matrix recovery management using the Insight managed system setup
wizard.
For more information, refer to the HP Matrix Operating Environment 7.2 Getting Started Guide
and the HP Insight Managed System Setup Wizard 7.2 Getting Started Guide available at
.
Uninstalling Matrix recovery management
Use the Windows Add/Remove Programs feature as follows:
1.
Select recovery management, then click Remove.
2.
Wait until the Matrix recovery management product no longer appears in the list.
Setting up Networking
It is assumed that networking links are present between the Local Site and the Remote Site. You
can use Matrix recovery management in a variety of networking configurations, but it is important
that you take note of the following Matrix recovery management networking configuration
parameters:
•
In a Matrix recovery management configuration, workloads can be running on DR Protected
logical servers at both sites. A Recovery Group can only be activated (workloads running) on
one site at any time, but it can be activated at either site such that workloads associated with
different Recovery Groups can be running at both sites simultaneously. For this reason, network
services such as DNS, DHCP, WINS, and AD must be available locally at both sites. If one
site becomes inoperative due to a disaster, network services continue to be available at the
other site based on the native disaster recovery capability in these services. This ensures that
workloads can be failed over from the failed site to the other site in the Matrix recovery
management configuration. Matrix recovery management must not be used to failover network
services.
NOTE:
The Matrix recovery management “startup order” feature is intended to start up
critical applications first, not to ensure that startup dependencies are met between applications
and infrastructure services such as networking.
•
Matrix recovery management does not perform DNS updates or update the IP configuration
of recovered logical servers during a failover operation. Your Network Administrator is
responsible for making the necessary modifications to ensure that network services are available
Installing and licensing Matrix recovery management
9