Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Size of Exchange 2010 backup

Created: 11 Sep 2012 | 6 comments


We have Exchange 2010 SP2 environment with two mailbox servers and DAG. 

We backup all databases using Netbackup 7.5. 

Could any one tell me why if database has 80GB and logs have 4GB, backup on tape take size almost 200GB ?

We create backup as a VSS snapshot.

Best Regards


Comments 6 CommentsJump to latest comment

V4's picture

"We create backup as a VSS snapshot." Couldn't get this

Do you manually take VSS snapshots via OS or via any other utility?

What is your backup selection list? pls post it

remigiusz_sz's picture


I mean that symantec Netbackup policy is configured to take vss backup (snapshot). 

in backup selection list I refer to databases like:

Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\MXDB01

V4's picture

And during restore (if performed) how much data gets restored, 200GB or same 80+GB ?

Are you verifying 200GB count from activity monitor or from BAR GUI

with NBU 701 there was issue in Activity monitor for showing almost double of actual job size.

got fixed by 71

Wondering it's back (dark knight rises ;-)

remigiusz_sz's picture

after restore it's only 80GB not double :)

we have 7.1 version but policy is copied from earlier version

this double size is showing in activity monitor 

V4's picture

check with support on fix.. or try to upgrade on

Mark_Solutions's picture

Check the Client Backups report to see what that says the size is and also check in the catalog section of the GUI

If they say 80GB then it is the GUI showing the wrong size - but do double check exactly what you are backing up and their sizes in the BAR GUI (public folders and the like)

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.