HP Matrix Operating Environment Software - Manual (Page 15)

Example invocations of Matrix recovery management User Defined adapter implementation
•
During Storage Management Server configuration in Matrix recovery management:
<Matrix recovery management installed
directory>/STORAGE/EMC/validatesms.cmd sms_name=EMC_SMS1
sms_username=admin
•
During Storage Replication Group configuration in Matrix recovery management:
<Matrix recovery management installed
directory>/STORAGE/EMC/validatesrg.cmd sms_name=EMCSE1
sms_username=admin local_storage_id=emc_id1 remote_storage_id=emc_id2
srg_name=SRG1
•
During an Activate operation in Matrix recovery management:
<Matrix recovery management installed
directory>/STORAGE/EMC/failoversrg.cmd local_sms_name=EMC_SMS1
local_sms_username=admin local_storage_id=emc_id1
remote_sms_name=EMC_SMS2 remote_user_name=admin
remote_storage_id=emc_id2 srg_name=SRG1 use_non_current_data=yes
Command return code
Commands must return 0 on successful completion and a non-zero error code indicates failure.
Notes
Matrix recovery management supports multiple User Defined storage adapters to co-exist in a
Matrix recovery management configuration. For each User Defined storage adapter type, you can
create a new subdirectory and place your implementation of the three commands for that storage
type. For example, to add a storage adapter named EMC, create an EMC subdirectory under
<Matrix recovery management installed directory>/STORAGE
and copy all three
commands to the newly created directory:
•
<Matrix recovery management installed
directory>/STORAGE/EMC/validatesms.cmd
•
<Matrix recovery management installed
directory>/STORAGE/EMC/validatesrg.cmd
•
<Matrix recovery management installed
directory>/STORAGE/EMC/failoversrg.cmd
If your implementation of the storage adapter commands requires passwords to manage storage
replication, the storage adapter command implementation must handle passwords securely. It is
your responsibility to encrypt/decrypt passwords while saving and retrieving them.
Local Site logical server setup
You must ensure that logical servers selected for DR protection at the Local Site meet the following
requirements:
•
The storage associated with these logical servers must be SAN based.
•
A logical server must have been activated at least once, before it can be DR protected. If the
logical servers you plan to protect with Matrix recovery management at the Local Site have
not been activated, and an operating system and applications have not been installed, these
steps must be completed before you can configure these logical servers for DR protection.
Logical servers that meet these conditions will appear in the Available LS(s) list in the Local
Site Matrix recovery management configuration GUI, even if they are deactivated after they
have been activated for the first time.
Local Site logical server setup 15