BE2010 R3 - Excruciatingly long backup window. Looking for tips/tricks for optimally setting up jobs.
Hi Folks, I'm running BE 2010 R3 with all the updates through SP3 on a single media server. Remote agents are all up-to-date.
Good, bad, or ugly I'm going to lay out the current setup we have, and I'd like to get feedback on how to better set this up, or decide if this is just as good as it gets.
Our weekly full backups consist of two jobs.
Job #1: Windows servers. We have about 25 windows servers on this selection list. It backs up system state, disk drives, and any sql databases. The job is about 2.8TB, with about 3.6 million files and 500,000 or so directories. It takes about 40 hours to run.
Job #2: Filer backup. This just backs up all our network shares from our filer via smb. This job is about 2.4TB, with 2.8 million files across ~250,000 directories. It takes about 60 hours to run.
We have a quantum superloader 3 with 8-tape magazine and a single LTO4 drive. I find this infuriatingly slow. Basically we start backing up at 11AM on Friday, and it doesn't finish until sometime on Tuesday.
I got some improvements by bumping the block size up to 256KB but I think now it might have to do with how the jobs are set up.
Symantec suggested I set up 25 different jobs, one for each server, but I'm not entirely sure how you would work out the scheduling of those, it seems like it would be impossible to stagger the time windows for so many different backup jobs. Then, glancing through the best-practices guide, it seems like they also recommend splitting the servers down into jobs that segregate out system state, sql backups, etc. At this point I'm just rather lost, and looking for some guidance. It's a pretty simple and straightforward setup, by comparison to what many people have, but even this feels a little beyond my scope.
Thanks in advance for any tips or tricks, comments, criticism, etc, I will gladlty take whatever I can get.
ETA - Is there a reason my comment replies are being sent to a moderation queue? Seems like an unnecessary hurdle with a b2b customer when replies to the topic can't even be posted in a timely manner.