HP StorageWorks P9000 Command View Advanced Edition Suite Software 7.1 Administrator Guide (web) (TB581-96050, May 2011)

server.agent.rm.ignorePairStatus
CAUTION:
If you want to check the latest copy pair information by using the GUI or CLI, take either of the
following actions depending on the copy pair management method.
If local management is used: Refresh the storage systems.
If central management is used: Refresh the pair management server.
• If you want to unify the coding format of pair volume information into the HORCM_DEV or HOR-
CM_LDEV format when creating pairs:
server.agent.rm.pairDefinitionForm
• If you want to exclude a volume pair that is already managed by RAID Manager from Device
Manager operations
server.agent.rm.exclusion.instance
• If you want to optimize a user-created RAID Manager configuration definition file so that it can
be used in Device Manager
server.agent.rm.optimization.userHorcmFile
In addition, to use Replication Manager to manage copy pairs, you need to specify the properties
below. If the properties are not set to appropriate values, the memory heap size might be insufficient
or a timeout might occur during the Replication Manager processing.
• agent.rm.TimeOut property in the agent.properties file
Adjust this value as necessary, while running Replication Manager and checking for timeouts
during processing.
• server.agent.maxMemorySize property in the server.properties file
Specify a value based on the number of pairs managed by a host (pair management server). By
default, the heap runs in a 64-megabyte memory area. If the number of managed pairs exceeds
5,000, increase the memory heap size by 64 MB, and increase by another 64 MB for every
2,500 pairs above that. For example, if a host manages 6,000 pairs, set the serv-
er.agent.maxMemorySize property to 128. Also, if a host manages the configuration definition
files for both a primary and secondary site, specify a value based on having twice as many
managed pairs.
Specifying settings for switching the Java execution environment
The following Java execution environments can be used on a Device Manager agent whose host OS
is Windows or Linux:
• JRE 5 (1.5.0) bundled with the Device Manager agent
• Oracle Sun JDK 6 Update 22 (1.6.0_22) or later
• Oracle Sun JRE 6 Update 22 (1.6.0_22) or later
Use the following procedure to switch the Java execution environment after Device Manager agent
operation has started.
To switch the Java execution environment:
1. Log on as a member of the Administrators group or log in as a root user.
Administrator Guide (Web Version) 207