It there a technical reason why the NextPool directive is part of the pool at
all? When I first heard about migration and copy jobs, I expected to find
something like a TargetPool directive in the job definition, so that it can be
varied for each job.
Someone already had to hack around this with
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
