Okay.. so here's my setup:

1 x Badass opteron 2TB server w/ RAID10 storage/etc/etc
3 x Normal wimpy servers and workstations whose cumulative total
     "standard" storage space exceeds that of the server

I use the big server as my primary.. er.. server, and the others are 
older machines that I still have lying around. I want to backup the 
server to the wimpy workstations to eliminate the server's PCI-e card 
as a single point of failure.

Tape drives are not an option: I might as well buy another server for 
the cost of a single tape drive. :(

How can I limit per-device how much space bacula eats? These are 
multipurpose machines and I don't want to fill their drives up with 
bacula data. (Free Space Command seems to only run for non-File 
media.)

Is there a trick to getting Bacula to automatically use the next 
storage daemon in line when backing up a large File Set in a single 
job? My job definition lists:

Storage = File,File-shog,File-intrigue

.. "File" has three archive devices, File-shog/intrigue are on two 
other machines.

I realise I can set multiple NFS mounts for use in a single storage 
daemon--but then I'm bypassing bacula.

I also realise I can set bacula-specific quotas on the drives in 
question for the bacula user--but then I'm bypassing bacula again 
there too.

I honestly have been searching through the mailing list archive. :-)

Hints would be much appreciated. Thanks!

Marc Tooley
P.S. Due to anti-spam measures, please post follow-ups to the list and not my 
email address. Thank you!

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to