Don't configure your jobs to USE the scratch pool. That's the root of the issue.
Instead, set your job's pool to be something else OTHER than "Scratch", let's say it's "Client1_Pool" just for example. Of course, you'll have to define the pool to the director and reload the config before you run the job. It's a good idea to test the config before you actually issue the "reload" command. Speak up if you need help with that. When your job "Client1" runs, if there are valid volumes in "Client1_Pool" then bacula will use a volume in the "Client1_Pool". If there is NOT a valid volume in the "Client1_Pool" THEN bacula will re-assign an appropriate volume from the "Scratch" pool into "Client1_Pool" and use that one. So your jobs should never be explicitly told to use the Scratch pool. Bacula does it automagically. I hope that helps it make sense. --Tim ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
