still increase the time before the management server times out, but keep in mind that it will lengthen discovery.

To increase the time-out period:

1.Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the Disk Space tree.

2.Paste the following text into the Custom Properties box.

cimom.cxws.agency.firstwait=200000

cimom.cxws.agency.timeout=200000

where

•cimom.cxws.agency.firstwait - The firstwait property controls the amount of time required for the management server to wait after it first contacts the CIM extension on the host before the management server attempts to proceed with a username and password. The default value is 1,000 ms. You are modifying it to wait 200,000 ms or 3.33 minutes.

•cimom.cxws.agency.timeout - The timeout property controls the allowable interval of silence before either the CIM extension or the management server starts to question whether its partner is still alive. If one entity (management server or extension) does not receive a message from the other during the interval set by the timeout property, it sends an “are you there” message. If that message is not acknowledged during the interval set by the timeout property, the entity concludes that the connection is no longer functioning. The CIM extension stops attempting to make a connection. When this occurs on the side of the management server, the management server attempts to re-connect (and continues the attempt until the host becomes available). The default value is 1,000 ms. You are modifying it to wait 200,000 ms or 3.33 minutes.

3.Click Save.

ERROR replicating APPIQ_EVAStorageVolume during Discovery Data Collection for an EVA array

Errors similar to ERROR replicating APPIQ_EVAStorageVolume might occur when an EVA-specific data cache is updated during a Discovery Data Collection operation. For example, when Data Protector creates a snapshot, a new virtual disk is automatically created on the EVA array, and the EVA database used by the management server is updated to reflect this change.

If the EVA database is changed during a Discovery Data Collection operation, small replication errors may be seen as a result. The array information will be updated with the correct information next time Discovery Data Collection runs.

Recalculating the Topology

When Recalculating the topology or running Discovery Data Collection, other tasks using the management server can be delayed.because the management server must recalculate the topology, which is a resource intensive operation. Recalculation occurs after a Discovery Data Collection when provisioning is done, and when you choose to recalculate the topology manually.

HP Storage Essentials SRM 6.0 User Guide 719