The total backup size will depend on the size of the CCM database, i.e. the numbers of users, devices, and the CDR records to be backed up. Sometimes the backup size goes more than 2GB also, if there are a lot of CDR Records to be backed up. There is no thumb rule to decide the size. It would be a good idea to back up the database on some local machine or a local tape to find out how much space it takes up and then do a backup to the space where they are charged.
One way to reduce the size of the database can be to purge old CDR records and keep the most recent records only to be backed up, if you are fine with it.
Average size I have seen during back ranges from 50M to 250M With CDR's it can easily up to 1+Gb.
You can expect around 1.5GB with the following:
-Cluster with 4000 IP Phones
-30 PSTN trunks (Local and LD)
The number of phones and PSTN trunks has less impact, but when the number of phones and trunks increase, this will increase the number of calls made from these phones and add up to the CDR/CMR disk space. In the above scenario, we purge CDR/CMR records that are older than 30days, this will play role in the size.
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...