On 08/21/2017 11:49 AM, Phil Stracchino wrote: > I can immediately cite one practical *disadvantage*: you're going to be > doing a fandango on disk. With 500 volumes open, you may well spend > more time seeking than actually writing.
Well, I'd also want to look at the elevator scheduler and the actual hardware too... The problem as I see it, is bacula sucks at "disks as tapes". It doesn't work without vchanger, and it can't auto-label volumes in the vchanger. (Inability to write two copies at once to guard against disk failure is icing on the cake.) If you back up to a single filesystem, you can spool jobs in parallel to fast drive and have them despooling to volumes sequentially to spinning rust with very little practical speed penalty. Provided your disk subsystem is faster than the network, of course. Adding one volume per job/client constraint and $(JobId) to volume label shouldn't be too hard. If you want to use removable drives as "magazines" with one drive per client... I'd be tempted to take a close look at BackupPC or some such before I'd commit to bacula. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
