Hello,
In general, if the definitions of the jobs are not available, Bacula
will not have the
information it needs to perform a migration (Next Pool, ...). I agree
with what
Josh says -- if you want to access a Job for any reason, it is better to
keep the
Job definition and possibly disable
On 1/14/2019 6:49 AM, Alan Brown wrote:
If you are using Bacula for any form of archival work, or migrating OLD
backups, then you need to be aware of of this issue.
The Migrate feature only migrates jobs in a volume that are in the
configuration file.
I think I get your point, but why
If you are using Bacula for any form of archival work, or migrating OLD
backups, then you need to be aware of of this issue.
The Migrate feature only migrates jobs in a volume that are in the
configuration file.
What this means is that if you have jobs old jobs that are no longer
backed up
