Backing up and restoring HP Insight Management 7.3 Central Management Server (Windows)

Technical white paper | HP Insight Management 7.3
Introduction
If the HP Insight Management CMS has been lost or corrupted, you may need to restore the CMS from a backup copy.
Note:
The information in this white paper is specific to the HP Insight Management software components included on the HP
Insight Management 7.3 DVD. See Scope for more details.
Preparing your environment for backup describes the steps to quiesce the HP Insight Management CMS before performing a
backup. Saving your environment describes the steps to perform a full system backup (including the Windows operating
system and HP Insight Management program files) or a partial backup (data only) of the HP Insight Management files,
directories, and databases on the CMS that contain user-changeable state and configuration data. A partial backup can be
performed between full system backups.
The steps to restore the CMS are described in Preparing your environment for restore and Restoring your environment.
Completing the recovery process describes a set of best practices to resynchronize the CMS environment with the managed
environment after the data has been restored. HP recommends periodically testing your backup and restore procedures in a
nonproduction environment.
Note:
This white paper describes the backup and restoration of the same system (or an identical replacement system) for fault-
insurance purposes only. It does not apply to system migration or software upgrades.
Scope
This white paper describes the procedures to back up and restore the HP Insight Management 7.3 components listed in
Table 1.
Table 1. HP Insight Management components covered in this white paper
HP Insight Management component
Comments
HP Systems Insight Manager
HP System Management Homepage (SMH)
HP Version Control
HP Insight Control server deployment
A full system backup should be
performed whenever changes are made
to the HP Insight Control server
deployment environment.
Note:
This component is not supported in a
Microsoft Failover Cluster
configuration.
5