HP Matrix Operating Environment Software - Manual (Page 23)

NOTE:
•
When you use Matrix recovery management to DR protect VMware ESX based IO services
that have been deployed from an IO template using an ICVirt template or a VM template
on the vCenter server at the Local Site, an ICVirt or VM template with same name must
be available at the Remote Site before you perform a Matrix recovery management import
operation to import the site configuration. If an ICVirt or VM template with the same name
is not available at the Remote Site, DR protected IO services will not be imported.
•
When you use Matrix recovery management to DR protect Microsoft Hyper-V based IO
services that have been deployed from an IO template using an ICVirt template on the
CMS at the Local Site, an ICVirt template with same name must be available at the Remote
Site before you perform a Matrix recovery management import operation to import the
site configuration. If an ICVirt template with the same name is not available at the Remote
Site, DR protected IO services will not be imported.
6. Add IO services to Matrix recovery management Recovery Groups. Recoverable IO services
can be selected from a drop-down menu when you configure IO services Recovery Groups.
For more information, see the Recovery Groups tab in the Matrix recovery management GUI.
7. Export site configuration at Local Site. For more information, see “Matrix recovery management
export and import operations” (page 20) .
8. Import site configuration at Remote Site. For more information, see “Matrix recovery
management export and import operations” (page 20) .
Configure IO properties
To enable DR Protection for IO services, edit the following hpio.properties and
dr.properties
files located in C:\Program Files\HP\Matrix infrastructure
orchestration\conf directory:
hpio.properties
•
Enable DR Protection for IO services: enable.dr.protection = true
•
Specify the datastore used for provisioning DR Protected IO services:
At the Local Site, specify the volumes to use for DR Protected IO services, for example:
volume.dr.list =
/vmfs/volumes/ds_1;C:\\ClusterStorage\\Volume3;C:\\ClusterStorage\\Volume4
◦
◦ At the Remote Site, specify the volumes to use for replica IO services, for example:
volume.dr.replica.list =
/vmfs/volumes/ds_1;C:\\ClusterStorage\\Volume3;C:\\ClusterStorage\\Volume4
NOTE: If one datastore is specified in volume.dr.list, the DR Protected IO services are
provisioned on the datastore specified.
If multiple datastores are specified in volume.dr.list, the DR Protected IO services are
provisioned on the datastore in volume.dr.list that is both available for that server pool
and also has the most free disk space.
If multiple datastores are specified in volume.dr.list, and the IO template specifies one
of the datastores in volume.dr.list, the DR Protected IO services are provisioned on the
datastore specified in the IO template.
•
Set the static.ip.replica.list property to reserve static IP addresses for replica IO
services at the Remote Site. For example if the networks configured in IO at the Remote Site
are subnetX and subnetY, one or more IP addresses can be reserved for replica services:
static.ip.replica.list =
subnetX:192.16.0.10;subnetX:192.16.0.15-192.16.0.20;subnetY:192.16.0.30-192.16.0.40
DR protection for IO services 23