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 native autochanger support make that obsolete?
> I'm running v9.4.
> 
> On Fri, May 10, 2019 at 1:52 AM Kern Sibbald <k...@sibbald.com> wrote:
> 
> > 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.  It appears (I don't have enough
> > information here) that this is not your case.
> >
> > Best regards,
> > Kern
> >
> > On 5/10/19 2:58 AM, David Brodbeck wrote:
> >
> > 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 consolidate. It now correctly locates the jobs to
> > consolidate. However, I'm getting deadlock when it tries to access storage,
> > probably because I have Pool and Next Pool set to the same location.
> >
> > The documentation (
> > https://www.bacula.org/9.4.x-manuals/en/main/Migration_Copy.html) states
> > that it should work:
> > "Alternatively, you can set your Next Pool to point to the current pool.
> > This will cause Bacula to read and write to Volumes in the current pool. In
> > general, this will work, because Bacula will not allow reading and writing
> > on the same Volume."
> >
> > This is what I'm trying to do, but it doesn't work; the job stalls with
> > "waiting on Storage." I assume this is because my file pool only has one
> > device, so Bacula assumes it can't both read from and write to it at the
> > same time. I've found lots of old (v5.x era) references to using vchanger
> > to solve this kind of problem, but I'm unsure if that's still the best way
> > to go. The current documentation is a bit fragmentary on this and I'm
> > hoping someone can point me in the right direction.
> >
> > Here's the relevant configuration stanzas for my storage:
> >
> > bacula-dir.conf:
> > Storage {
> >   Name = russell.math.ucsb.edu-sd
> >   Address = russell.math.ucsb.edu
> >   SDPort = 9103
> >   Password = <redacted>
> >   Device = DataCenter
> >   Media Type = DCFile
> >   Maximum Concurrent Jobs = 10
> > }
> > Pool {
> >   Name = DataCenterPool
> >   Pool Type = Backup
> >   Recycle = yes
> >   AutoPrune = yes
> >   Volume Retention = 60 days
> >   Maximum Volume Bytes = 50G
> >   Maximum Volumes = 280
> >   Label Format = "DCVol-"
> >   Storage = russell.math.ucsb.edu-sd
> > }
> >
> > bacula-sd.conf:
> > Device {
> >   Name = DataCenter
> >   Device Type = File
> >   Media Type = DCFile
> >   Archive Device = /media/bacula/DataCenterPool
> >   LabelMedia = yes;
> >   Random Access = Yes;
> >   AutomaticMount = yes;
> >   RemovableMedia = no;
> >   AlwaysOpen = no;
> >   Maximum Concurrent Jobs = 10
> > }
> >
> >
> > --
> > David Brodbeck
> > System Administrator, Department of Mathematics
> > University of California, Santa Barbara
> >
> >
> >
> > _______________________________________________
> > Bacula-users mailing 
> > listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users
> >
> >
> >
> 
> -- 
> David Brodbeck
> System Administrator, Department of Mathematics
> University of California, Santa Barbara
> 


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to