You must configure the features that you want to back up. Perform the following steps to choose the features that you want to back up
1 Navigate to the Disaster Recovery System. Log in to Cisco CallManager Administration, choose Disaster Recovery System from the Navigation menu in the upper, right corner of the Cisco CallManager Administration window, and clickGo.
The Disaster Recovery System Logon window displays.
2 Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Platform Administration.
3 Navigate to Backup>Configure Features.But keep in mind that Changing a backup feature changes it for both manual and scheduled backups.
4 From the list of available features, choose the feature or features that you want to include in the backup and click Save. You must choose at least one feature.
5 Continue with the next procedure for configuring a storage location.
Here is the URL for the Cisco IP Telephony Disaster Recovery System Administration Guide
Thanks for your reply but I think from my explanation and attachment it is pretty clear that I've got the backup configured correctly and that for some reason it is not backing up all of the features under "CCM".
I've got a case open with TAC who has confirmed this to be a bug and they are working on it. I will publish the bug ID once released.
TAC opened a bug ID for it: CSCsu70367 but I couldn't wait and decided to rebuild my publisher as a result.
I've just noticed that there is no information displayed under this bug ID and have contacted the TAC engineer to find out why. My advise would be to rebuild your server while you still have a fairly recent backup or you can contact TAC to see what they say. You'll noticed on the above bug ID that they don't mention ver.5.x so you might have a new one there. Good luck.
We did have TAC clean up the CM prior to this issue as we hade run out of disk space on the box and it didn't have enough room to create the required TAR files. Did you happen to have any space issues prior to your problem?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...