EasyUC for Cisco
Config Backup: back up the CUCM configuration
Shows which CUCM objects EasyUC backs up, how large the backup is and what changed most recently.
In EasyUC: EasyUC Cisco → Config Backup
What it is for
The CUCM backup keeps a restorable copy of selected CUCM objects in the EasyUC database. For a phone this includes lines, speed dials, BLF buttons, add-on modules, services, owner and user associations. EasyUC reads the objects from the CUCM via AXL, one after another and never in parallel. If an object is later deleted directly in the CUCM, it can be restored under Restore Config exactly as it was backed up.
The Config Backup page is the information view for this backup. For each category it shows whether it is backed up, how many records and how much storage are used, when the last full reconciliation took place and which changes EasyUC detected most recently. All other pages continue to show the live data of the CUCM. The backup is read only for restoring.
Config Backup is not a backup of the EasyUC appliance and not a replacement for the DRS backup of the CUCM. Only the object types of a CUCM connection listed below are backed up. Objects such as device pools, partitions, calling search spaces, route lists, route groups, hunt pilots or line groups are not part of the backup. They must exist in the CUCM for a restore to succeed.
Prerequisites
- License module
cucmand an active CUCM connection. Without a connection the page shows: “No active CUCM connection. Select one at the top or set one up first.” - For the menu items Config Backup and Restore Config one of these roles is sufficient:
ROLE_APP_LIST_DELETE_DEVICE,ROLE_APP_RESTORE_DEVICE,ROLE_APP_RESTORE_DELETED_USER,ROLE_APP_RESTORE_TRANS_PATTERN,ROLE_APP_CREATE_TRANS_PATTERN,ROLE_APP_RESTORE_ROUTE_PATTERN,ROLE_APP_CREATE_ROUTE_PATTERN,ROLE_APP_RESTORE_ENDUSER. - Which tabs you see depends on the object type. Phones and phone numbers:
ROLE_APP_LIST_DELETE_DEVICE,ROLE_APP_RESTORE_DEVICEorROLE_APP_RESTORE_DELETED_USER. Translation patterns:ROLE_APP_RESTORE_TRANS_PATTERNorROLE_APP_CREATE_TRANS_PATTERN. Route patterns:ROLE_APP_RESTORE_ROUTE_PATTERNorROLE_APP_CREATE_ROUTE_PATTERN. End users:ROLE_APP_RESTORE_ENDUSERorROLE_APP_RESTORE_DELETED_USER. - SIP trunks, gateways, gateway ports and application users are visible only to administrators and template creators (
ROLE_APP_ADMIN,ROLE_APP_TEMPLATE). - Enabling, changing settings, Back up now, Accept and Delete backed-up data now are available only to administrators.
- The background job of the CUCM backup must exist and be enabled. For fast detection of changes, the change feed of the change log should also be running for the connection.
- Plan a time window with little activity on the CUCM. The first full pass reads every selected object once.
Step by step: enable the CUCM backup on the connection
-
Under Backed-up objects, select the types. The defaults are Phones, Translation patterns and Route patterns. You can add Phone numbers (lines/DNs), End users with controlled devices, Application users with controlled devices, SIP trunks and Gateways with ports (MGCP, SCCP, H.323). At least one type must be selected.
Step by step: read the state of the backup on the Config Backup page
Step by step: switch categories, back up immediately and delete data
Fields and options
| Field / action | Meaning and use |
|---|---|
| Enable CUCM backup | Main switch per CUCM connection. Default: off. Switching off only stops the collection. Existing backups remain restorable until the end of the retention period. |
| Backed-up objects | Eight switches in four groups. Devices: Phones, Phone numbers (lines/DNs). Dial plan: Translation patterns, Route patterns. Users: End users, Application users. Infrastructure: SIP trunks, Gateways with ports. Default: Phones, Translation patterns, Route patterns. |
| “new” badge | Marks types that were added later. They are not enabled automatically on connections with a saved selection. |
| “coming” / “not supported yet” badge | The server reports per connection which types it already collects. A type with this badge stays selected but is not backed up yet. In version 4.8.7 the server reports all eight types as supported. |
| Start / End | Time window of the full pass in the format HH:MM. Default 01:00 to 05:00. Whatever is not finished within the window is continued in the next window. |
| Time zone | Time zone of the time window. Default Europe/Berlin. |
| Pace | Pause between two AXL requests: Slow 400 ms, Normal 120 ms (default), Fast 30 ms. A slower pace spares the publisher, and the pass takes longer. |
| Re-read at the latest after (days) | Unchanged objects are also read again after this time. Allowed 1 to 30, default 7. |
| Retention of deleted objects (days) | Deleted objects that have not been restored remain restorable for this long. Allowed 7 to 365, default 90. |
| Backup (column) | State of the category: backed up, off or off since <date>, or not supported yet. For switched-off categories the line below states when the data will be removed. |
| Records | Number of backed-up objects that are not deleted. The tooltip lists pending, held and reported-as-changed objects as well as the number in the CUCM at the last reconciliation. |
| Storage / uncompressed | Storage is the size of the stored, compressed content. Uncompressed is the size of the backed-up configuration. The addition + … log states the size of the change log. |
| Last full reconciliation | End of the last full reconciliation of the category. Without a reconciliation it shows “no full reconciliation yet”. |
| Source (Recent changes) | How EasyUC learned of the change: Pass, Refresh, Change feed, Reconciliation, accepted, EasyUC or AXL version. |
| Held deletions | Protection against mass deletion. If more than 50 objects and at the same time more than half of a type are missing in a reconciliation, they are considered deleted only after Accept. |
Check the result and troubleshoot
- You recognize success by Enabled in the status bar, a date in Last full reconciliation and rising values in Records.
- Secret values such as passwords, PINs and digest credentials are never backed up. The Backup dialog marks them with “not backed up – set it again when restoring”.
- “Please select at least one object type.”: select at least one type under Backed-up objects.
- “Start and end of the time window must differ.”: correct the time window.
- “The background job of the CUCM backup is missing or disabled. Please check under background jobs.”: activate the job under the background jobs.
- “Change feed off – changes are only backed up in the time window”: the change feed of the change log is not running for this connection. A restore then brings back the last backed-up state. Switch on the change feed on the CUCM connection.
- “The CUCM backup is enabled, but none of the selected object types is backed up on this connection yet – nothing is collected.”: also select a type that is already backed up.
- “The CUCM backup settings were changed in the meantime (e.g. by another administrator). Nothing was saved – the view has been reloaded, please try again.”: repeat the action.
- “The category was switched off just now – please try again in a minute.” or “Partly deleted – please run it again.”: start Delete backed-up data now again.
- “You do not have permission for this.”: you lack the role for this category. Figures of a category without permission appear as a dash with the note “No permission for this category”.
- A pass in the state Interrupted waits until the next time window. Back up now resumes it immediately.