Uninstalling matrix recovery management, Setting up networking – HP Matrix Operating Environment Software User Manual
Page 9
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
if you configure a logical server to use a different IP or subnet at each site in the Matrix recovery
management configuration.
•
When running on physical targets (VC hosted) or non VMware ESX virtual targets (VM hosted),
Matrix recovery management does not ensure that logical servers use the same MAC addresses
at both sites. When running on VMware ESX hosted virtual targets, Matrix recovery
management does ensure that logical servers use the same MAC address at both sites. Your
Network Administrator needs to plan for this in the networking configuration for DR Protected
logical servers, if you are using DHCP.
NOTE:
For MAC address details for cross-technology logical servers (logical servers that
are capable of running on both VC hosts and VM hosts), see
.
•
When running on HP Virtual Connect hosted physical targets, the Portable Images Network
Tool (PINT) must be used to prepare the server image to execute on targets with different
network interface configurations and MAC addresses. To use PINT, the Local and Remote
Sites must be on the same network, and the OS image must be a Linux version that is supported
by Matrix recovery management. PINT ensures that the static network configuration from the
source server is successfully transferred to the destination server network interfaces, despite
the different environment. The executables and README are in the <SMP>/PI/PINT folder,
where <SMP> is the folder where HP Insight Control server migration is installed. Copy the
executable cp011231.exe to the physical server where the image is currently running. Run
cp011231.exe
to install PINT and start the PINT service.
For information on supported Linux versions and HP Insight Control server migration, see the
HP Insight Management 7.1 Support Matrix at
Setting up Networking
9