A policy checkpoint is a method of saving the records in the
CMP database at a specific point in time. The table below details which configurable objects are and are not saved as part of the checkpoint.
Record Keeping and Policy Checkpoints| Records saved |
Records not saved |
|---|
- policies
- policy groups
- policy templates
- policy tables
- policy counter IDs
- traffic profiles
- traffic profile groups
- MPE configuration templates
- match lists
- retry profiles
- applications
|
- quota profiles
- quota conventions
- serving gateways/MCC-MNC mappings
- charging servers
- time periods
- customer AVPs
- services
- rating groups
- LI mediation functions
|
Note: The checkpoint function also saves associations between:
- Virtual MPE templates and real MPE templates
- MPE devices and virtual MPE templates
- Virtual MPE templates and other configuration objects
You can save up to 10 checkpoints.
After a checkpoint is created, you can return to this set of records at any time by restoring the checkpoint.
CAUTION: When you restore a checkpoint, all existing data is permanently removed.
The checkpoint function is different from the import/export function in the following ways:
- Checkpoints are saved to the CMP database rather than to a file.
- A checkpoint saves all the records mentioned in the preceding table. The import/export feature allows you to select which records to import or export.
- A checkpoint can only be used on a specific CMP system and cannot be migrated to another CMP system.