|
You don't mention the technology behind your tape drive, database backend, CPU, RAM, or what your disk subsystem looks like--all of which would be useful to have a reasonable chance to analyze even vaguely properly, but I'll wade in nonetheless.
You are almost certainly shoeshining the heck out of your tape media. I believe most drive types will have to resort to stopping and starting once you get below a certain threshold (for LTO3, I think this is somewhere around 30MB/sec, as an example), the tape drive will wind up starting a stopping very frequently (as well as rewinding a bit). I imagine this will wear out both tapes and drive mechanisms pretty quickly.
Since you are not spooling data, I suspect you also are not spooling attributes--my first guess would be that your database backend is insufficiently fast--at a minimum you should spool attributes, and spooling data on even the local backups can yield performance gains, depending on your disk subsystem architecture. If network and disk subsystem can't deliver at least the minimum streaming rate for your tape drive, you need to spool to a fast enough disk to keep up with the tape drives needs.
If you are using something like LTO5, I think spooling using either SSD or RAID0 may almost be required--but perhaps LTO5 actually supports relatively low minimum streaming rates--I don't know, as I can't afford LTO5 (and I think the minimum streaming rate may well be manufacturer dependent).
-se
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
