I have a virtual Exchange 2007 system (VMware VM's) that is being backed up by VEEAM every night using block-tracking / snapshotting (standard Veeam backup strategy). The user load is about 200 active users. Every night, the backup is taking in about 75GB of data for the mail store backup of (5 different databases). However, if I look at the STORE SIZE, the store is not growing by this much at all...in fact, if the store grows 1 - 2 GB per day, that's a VERY BUSY email day.
I have other sites with MORE users running Exchange 2010 that is taking about .... 15GB of backup data (also using Veeam) and their daily store is growing by 5GB or more per day.
Can anyone think of any reason why this backup would be tracking SO MANY block changes? We worked with VEEAM, and they also agreed that the backup was much larger than they would expect ... but we ultimately could not resolve this with Veeam.
Can anyone think of a way that I can track down why this disk is catching so many changes?
About the Exchange system:
Exchange Version: Exchange 2007 with latest SP and rollup
Exchange Setup: 5 mailbox DB's, 1 public folder, NO circular logging. (1) CAS/HT server, (1) Mailbox server without CAS or HT roles
Windows Version: Windows 2008 R2
VMWare Version: VMware v5.5 clustered across (3) Dell hosts on an Equallogic SAN