Backing up and Restoring HP Insight Management 7.0 Central Management Server (Windows)

6
2. Ensure no HP Matrix infrastructure orchestration requests are in progress. Requests
pending approval and scheduled requests may remain scheduled.
a. When backing up a stand-alone CMS or the primary CMS in an infrastructure
orchestration federated CMS configuration, you can view the status of
infrastructure orchestration requests by selecting Infrastructure orchestration…
from the Tools menu in Systems Insight Manager and then selecting the Requests
tab. Select the End Date column name to sort the request list. Requests with an
empty End Date have not yet finished.
b. When backing up a secondary CMS in an infrastructure orchestration federated
CMS configuration, you need to quiesce the operations on the primary CMS
that are targeted at the secondary CMS that you are backing up. This will allow
infrastructure orchestration on the primary CMS to continue running while a
secondary CMS is being backed up. To do this, log in to the primary CMS to
issue the ioexec command, as shown below, from the command prompt. This
command is located under <HPIO>\bin. See Table 3 for the default location.
You will need to replace <secondaryCmsFQDN> with the lowercase fully
qualified domain name (FQDN) of the secondary CMS to be backed up. This
must be the same hostname configured on the Federated CMS Configuration
page. You can get to the page by selecting Federated CMS Configuration… from
the Options menu in Systems Insight Manager on the primary CMS.
ioexec beginmaintenance cms –C <secondaryCmsFQDN>
You can run the following command to get a count of active requests to the
secondary CMS. The quiesce is not complete until the active request count
goes to 0.
ioexec countrunningrequests cms –C <secondaryCmsFQDN>
For more information about these commands, run
ioexec beginmaintenance cms --help
or
ioexec countrunningrequests cms --help