> Kern Sibbald wrote: > Hello, > > If the only reason is to prevent a deadlock then this override is not > necessary since Bacula (at some version, I think it was 2.4.0) will not > use the same volume for reading and writing. > > If there is some other good reason, please remove the comments about > deadlock and resubmit, and I think you can remove any workarounds you > implemented to prevent deadlocks.
I underestimated that Bacula was smart enough to avoid using the same volume. So I've removed my hack to see how it goes. I think at times it could be handy to override the NextPool though. Maybe instead of overriding NextPool in the Schedule, how about in the Job definition itself? That way you just reference the appropriate jobs in your schedule to achieve your Copy or VirtualFull backups. Regards, ---------- Jim Barber DDI Health ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
