On 09/05/2014 12:16 PM, John Drescher wrote:

> There are several ways to control what volumes bacula use. Although I
> am uncertian how you got in the situation you were in.

That makes two of us. I
1. deleted some volumes and didn't run 'update slots',
2. got an 'intervention needed' e-mail a day or so later.

I'm beginning to think I'd be better off with a simple pre-job script
that checks the disk and re-points a symlink to the next disk in the
set. Or something along those lines.

I've another bacula setup that writes to a single filesystem. It's been
running with about zero problems (knock on wood) and zero maintenance
for years: auto-labelling works, volume recycling works, the only
problems are spinning rust and lsi's ugly raid manglement software.

It seems once you step out of the ein drive, ein tape sandbox you're in
the "not intended for" use case and all bets are off. Which is only fine
if you don't care about your backups.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users