HP Insight Control 7.3 Update 1 Getting Started Guide

13 Backing up and restoring a CMS
If your CMS environment becomes lost or corrupted, it might be necessary to restore the environment
from a backup copy.
HP has published a white paper that contains step-by-step instructions for defining backup and
recovery procedures for HP Insight Management products running on a Microsoft Windows-based
CMS. The white paper, Backing Up and Restoring HP Insight Management 7.3 Central Management
Server (Windows) is available at the following web site:
http://www.hp.com/go/insightsoftware/docs.
HP recommends that you follow the instructions in this white paper to periodically perform a full
backup of your CMS. This white paper describes the backup and restoration of a same system for
fault insurance purposes only. It does not apply to system migration or software upgrades.
In addition to describing full backups, the white paper covers the following topics:
• How to quiesce the Insight Management environment before performing a backup.
• Backing up the Insight Management files, directories, and databases that contain user
changeable state and configuration data. This partial backup process can be performed
between full backups.
• Restoring the environment.
• Completing the recovery process, which defines a set of best practices to re-synchronize the
environment after the data has been restored.
The recovery process requires the mxsync utility to be installed on the CMS. The mxsync
utility is included in the HP Insight Management download package or DVD and is installed
through the Insight Management Installer wizard.
To successfully restore the Insight Management files, the CMS must be running the same version
of the software that was running when the full system backup was performed. HP recommends
performing a full system backup prior to updating software on the CMS and immediately after you
finish the update.
HP also recommends that you periodically test your backup and restore procedures in a
non-production environment.
30 Backing up and restoring a CMS