Link to home
Start Free TrialLog in
Avatar of Ash_San
Ash_San

asked on

Size of MS Exchange 2003 Backup

Hii
I;m backing up my Exchange 2003 server standard edition using nt backup and the size of the backup is increasing everyday at large amounts. It's less than a month we've started using exchange and i've out a limit of 1Gb on invidual mailboxes (we have around 30 users) . Now the backup size is 65GB. Is there a way to keep this size minimal as paossible without sacrificing any services.
i mean is there any cleaning job required to be done to make the exchange working efficently with less space.

Thanks in advance for your time and input
Avatar of aissim
aissim
Flag of United States of America image

Oh my - 65GB doesn't even sound possible for only a month in production. First thing to do is figure out where all that space is coming from - is it the database? the logs? or are there other things being backed up in conjunction with the Exchange backup. Once you have an idea of what exactly is taking up the majority of the 65GB it'll be easier to figure out how to trim that down.
Avatar of redseatechnologies
Are you using NTBackup to a file?

I have seen this problem many times when trying to use NTBACKUP to a file - overwrite settings overwrite the data, but the file continually increases.

I am yet to see a solution, other than a script that deleted the bkf file before ntbackup starts

-red
Avatar of Ash_San
Ash_San

ASKER

Yes i'm using NTBACKUP and it is backing up to the same file everyday. So red does that mean deleting old backup file and then starting with a fresh file will help????

Thanks
ASKER CERTIFIED SOLUTION
Avatar of aissim
aissim
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
>>You could just change your backup job to 'overwrite' versus 'append'

That is the whole problem though - that doesn't work sometimes.

>>So red does that mean deleting old backup file and then starting with a fresh file will help????

I do not have a better solution than this at the moment unfortunately, but i do not consider this a very good option.  Deleting a backup before doing the next one is dangerous.

What I would probably recommend instead is that you create 2 backup jobs that run on alternate nights to 2 different files - after one finishes, delete the other backup file (if you know what I mean).

-red
Avatar of Ash_San

ASKER

thank you so much for your response red and aissim. i'll keep 3-4 different copies before deleting the last one.
Avatar of Ash_San

ASKER

Thanks again red and aissim ...so creating a new backup file for each day is working fine as the size is easily manageable...