Use the native virtual autochanger -- see FileChgr1 in the default bacula
config files.
__Martin
> On Fri, 10 May 2019 10:44:32 -0700, David Brodbeck said:
>
> Apparently so.
>
> I've been digging for recipes to do that. Is the old advice to use vchanger
> still best, or does Bacula's
Apparently so.
I've been digging for recipes to do that. Is the old advice to use vchanger
still best, or does Bacula's native autochanger support make that obsolete?
I'm running v9.4.
On Fri, May 10, 2019 at 1:52 AM Kern Sibbald wrote:
> Hello,
>
> If you are doing any kind of "copy" of data
Hello,
If you are doing any kind of "copy" of data (Migration, Copy,
VirtualFull, ...), it seems to me to be obvious, but perhaps I am
mistaken, you need two different Storage daemon device definitions
-- one to read a Volume, and one to write to a different Volume.
Still trying to get Progressive Virtual Full backups to work.
I solved the "no previous jobs found" problem by making only one job
definition (instead of separate incremental and virtualfull definitions),
and changing the job level to VirtualFull in the schedule for the times
when I want to
