HP XP Racks - Manual (Page 708)

Notes on updating configuration files
This section contains notes on updating a configuration file:
•
Do not perform an update on a configuration file from both Replication Manager and Business
Continuity Manager at the same time.
◦ If you update a configuration file from Business Continuity Manager, first stop the Business
Continuity Manager agent that is using that file to start up.
◦ If you attempt to simultaneously update or view a configuration file from both Replication
Manager and Business Continuity Manager, an error might occur from either Replication
Manager or Business Continuity Manager. If this happens, re-execute the update or view
operation. If an error occurs in an attempt to view the file from Replication Manager, the
configuration file information will be acquired the next time a request is issued. (Requests
are issued at regular intervals, as defined in Replication Manager.)
◦ If you update a configuration file from Business Continuity Manager while the Business
Continuity Manager agent is running, any changes that were made will not be applied
to the Replication Manager configuration file. If this happens, restart the Business Continuity
Manager agent, and then refresh the file from Replication Manager.
•
If you update the disk configuration definition file from Replication Manager (or Business
Continuity Manager), the updating process has an immediate effect on the information
regarding the volumes being used by the root list definition file or path set definition file. This
is especially true when you delete volume information. Make sure the root list definition file
or path set definition file is not using the volume.
Working around site errors and host failures
When a Business Continuity Manager agent cannot be used because of a site error or host failure,
you can use a Business Continuity Manager agent installed on one or more other hosts to perform
operations on the copy groups from Replication Manager. To switch to the Business Continuity
Manager agent installed on one or more other hosts, from Replication Manager, change the
primary host for the copy groups. For details on how to change the primary host, see the HP XP7
Replication Manager User Guide.
After the system has recovered from a site error or host failure, you must restart the Business
Continuity Manager agent and then refresh the management information on Replication Manager.
Error types and error information handling
Business Continuity Manager agent connects via TCP/IP and exchanges storage information with
Replication Manager.
If a communication line error or Business Continuity Manager agent failure occurs while the Business
Continuity Manager agent is running, error information is output to the Replication Manager log.
However, since the error is detected after Replication Manager issues a request, the output of error
information might be delayed for some time after the actual error occurrence.
In addition, if an error occurs when the Business Continuity Manager agent attempts to acquire
storage information, that storage information and the error information will not be displayed in
the Replication Manager window. If this happens, check the contents of the collected log.
Table 122 (page 709) shows the information that Business Continuity Manager agent outputs to the
log.
708 Linkage with Replication Manager