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
Here are two possible solutions:
* Make the tunnel at startup (e.g. in the script that starts bacula-dir).
* Use something like inetd to make an ssh connection on-demand (e.g. like
https://capocasa.net/on-demand-ssh-port-forwarding-with-inetd).
__Martin
> On Fri, 11 Jan 2019 20:55:04