Checkpoint and Importing Objects

Attention: To use the checkpoint option, the Allow policy checkpoint and restore setting must be configured in System Settings. See Configuring System Settings.

During an import action, the CMP system includes the Perform checkpoint before importing option. This is a protective measure that uses the Checkpoint function to save a snapshot of all the configuration objects that exist in the system. See the Policy Wizard Reference for more checkpoint details. Included in the checkpoint output file are:

Enabling the checkpoint option ensures that if a newly reconfigured system fails to function as expected, a checkpoint XML file exists that returns the system to the state prior to the import action. An additional benefit is that the checkpoint output file is saved in the CMP database and is accessible using Policy Checkpoint/Restore under the Policy Management section. Refer to the Policy Wizard Reference for details on managing checkpoint files.

In a networked CMP system, the checkpoint function is limited to the NW-CMP server. The Perform checkpoint before importing option is not available for S-CMP servers. After a restoration from a checkpoint onto a NW-CMP server, the NW-CMP server pushes the restoration data to all S-CMP servers. The MPE and virtual MPE templates are not updated. Real MPE templates and related associations are restored on the S-CMP servers, so that the policies can be restored to MPE through the virtual template.

The Checkpoint function differs from the Export All function in the following ways: See Exporting All Configuration Objects for details on exporting all configurable objects.