campinam
asked on
SBS Backup - how fast?
On a SBS 2003 server I use its built-in backup utility to backup everything, including Exchange.
Last time a 400 GB backup took 12 hours, plus more for verification - total was 18 hours.
Machine is a 3.0 GHz, 4 GB RAM. Backup device is an external hard drive USB 2.0 connected directly to the server.
Is this a normal backup time? If not, what am I doing wrong? I used SBS install settings and backup settings that are pretty standard, or so I think I did it...
Last time a 400 GB backup took 12 hours, plus more for verification - total was 18 hours.
Machine is a 3.0 GHz, 4 GB RAM. Backup device is an external hard drive USB 2.0 connected directly to the server.
Is this a normal backup time? If not, what am I doing wrong? I used SBS install settings and backup settings that are pretty standard, or so I think I did it...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It is shared on my web site (link available in my profile) - but more directly, www.lwcomputing.com/mysoftware.asp
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
leew: thank you for the script.
Oliver: Most of the space is taken by pictures and presentations. The backup device is an external hard drive (1 TB) - or rather two of those - USB 2.0 connected directly to the server.
Now that I've learned more things (thanks), I'm thinking of doing this:
1. Run a full SBS backup every Friday night, then take this backup drive (A) to a safe place. Connect another backup drive (B) and delete all files on it - B would stay put all week.
2. Every other night, on B, run SBS backup to save the system, Exchange and the database (all this max 30-40 GB) by excluding the rest. This backup would replace existing file.
3. Also every other night, on B, after (2) completes, run NTBackup in incremental mode (takes less time than the differential mode) for data excluded at (2).
4. Next Friday night, still on B, full SBS backup. Take B to a safe place, replace with A, delete all files, and it's ready for (2) and (3) every other night.
Am I right? Did I miss anything? I'd appreciate any comments.
Oliver: Most of the space is taken by pictures and presentations. The backup device is an external hard drive (1 TB) - or rather two of those - USB 2.0 connected directly to the server.
Now that I've learned more things (thanks), I'm thinking of doing this:
1. Run a full SBS backup every Friday night, then take this backup drive (A) to a safe place. Connect another backup drive (B) and delete all files on it - B would stay put all week.
2. Every other night, on B, run SBS backup to save the system, Exchange and the database (all this max 30-40 GB) by excluding the rest. This backup would replace existing file.
3. Also every other night, on B, after (2) completes, run NTBackup in incremental mode (takes less time than the differential mode) for data excluded at (2).
4. Next Friday night, still on B, full SBS backup. Take B to a safe place, replace with A, delete all files, and it's ready for (2) and (3) every other night.
Am I right? Did I miss anything? I'd appreciate any comments.
How often you backup depends entirely on the value of your data. It's a little dated, but you might want to article on backup in general. http://www.lwcomputing.com/tips/static/backup.asp
Good article leew.
--
Your strategy would be a good start.
I was suggesting differential backups because as you may already know, if you run a full once a week, it should be fast enough to run the differential jobs in between and in case of disaster, you don't have to restore all the incrementals since the last full backup (and in case an incremental bkf is corrupt, you'll lose data).
About step 3, you need a full backup say Friday and incrementals (or differentials) the rest of the week. Next Friday a full job is run and so on. Or you could do 2 full bkf by months...
--
Your strategy would be a good start.
I was suggesting differential backups because as you may already know, if you run a full once a week, it should be fast enough to run the differential jobs in between and in case of disaster, you don't have to restore all the incrementals since the last full backup (and in case an incremental bkf is corrupt, you'll lose data).
About step 3, you need a full backup say Friday and incrementals (or differentials) the rest of the week. Next Friday a full job is run and so on. Or you could do 2 full bkf by months...
ASKER
> I have a script I just modified that , in theory, should allow you to create scheduled, automated backups on a regular basis.
Could you share the script?