CUCM cluster backup size reduction

[joeharb]

We have one pub and 4 subs in our cluster and are having issues with the size of the backups.  In the past if a sub were to fail or need to be replaced we would simply do the install and add it back to the cluster and let the db synch, not doing a DRS restore.  Currently the backup's consist of each of the TFTP tar files which are well over ~2.5 Gig each.  Other than deleting files unused files from each server is there a way to reduce or eliminate the backup of subs?  I have thought about about denying the sub's IP address from the backup store but this would result in an error in the backup, ie it wouldn't complete.

We have restricted the number of copies to 1 but the total backup size is almost 17 Gig.

Anyone else had issues with this?

Thanks,

Joe

[Suresh Hudda]

CUCM backup size keep increasing whenever we do upgrade, device pack installation, firmware upgrade etc. So, the best option is to delete unused firmware files from all tftp servers.

Suresh

[Gordon Ross]

Each node's backup contains data that is unique to that node. Only the publisher backs up the database.

If you perform some magic to exclude a node from the backup set, you'll be loosing things like certificates - which are becoming more and more important in CUCM.

But why waste the time worrying about 17GB of disc space? A 1TB HD is peanuts nowadays.

GTG