Bacula-users

Re: [Bacula-users] Configuring autochanger with SAS LTO-5 drives

2017-06-03 18:46:43
Subject: Re: [Bacula-users] Configuring autochanger with SAS LTO-5 drives
From: Ivan Adzhubey <iadzhubey AT rics.bwh.harvard DOT edu>
To: <bacula-users AT lists.sourceforge DOT net>
Date: Sat, 3 Jun 2017 18:45:39 -0400
Hi Kern,

Thank you, your reply was most helpful. I am making progress, slowly but 
steadily. Hopefully, will have our new backup system up and running early next 
week.

Would you recommend building & installing version 7.9 instead of 7.4.4, which 
is the one available through Ubuntu repos? We do not need any of the more 
advanced features of the recent versions but bug fixes would be welcome.

--Ivan

On Saturday, June 3, 2017 6:02:25 AM EDT Kern Sibbald wrote:
> Hello,
> 
> In Bacula the "variables" that are set in the bacula-sd.conf file are
> normally referred to as Directives.  In general their scope is within
> the enclosing brackets that define the particular resource (e.g. Device
> { ... } or Autochanger { ...}
> 
> Normally for a Device resource that is part of an autochanger, you do
> not need to specify the Changer Device directive or the Changer Command
> directive, because they already be defined in the Autochanger resource.
> Within the Autochanger resource, the Changer Device should point to the
> scsi control channel for the changer -- in your case below this would be
> /dev/sg4.
> 
> The Control Device directive within a Device resource is used to specify
> the scsi control device for the Drive. This control device is used for
> TapeAlerts.  I strongly recommend setting up tape alerts under Bacula
> 7.9 and later as it will let you know when there are drive problems.  In
> prior Bacula version the implementation was too simplistic and so there
> was no need to specify a Control Device. Even in 7.9 and later you are
> not required to specify a Control Device within the Device resource.
> 
> Yes, the Control Device is primarily used for Tape Alerts, but it can
> also be used in the Enterprise version for drive locking and autochanger
> sharing.
> 
> Final note:  Both Changer Device and Changer Command are normally
> specified only in an Autochanger resource.  However, the original
> autochanger implementation was for a single drive autochanger, and in
> that case, Bacula did not have an Autochanger resource as the Device
> itself can be a single drive Autochanger by specifying the Changer
> Device and Changer Command within the Device resource.  I hope that is
> clear, and I see the documentation is not totally clear.  I have
> attempted to correct this in the latest manual that is on www.bacula.org.
> 
> Best regards,
> Kern
> 
> On 06/03/2017 05:02 AM, Ivan Adzhubey wrote:
> > On Thursday, June 1, 2017 11:27:49 PM EDT Ivan Adzhubey wrote:
> >> [7:0:0:0]    mediumx QUALSTAR TLS-8466         227d  /dev/sch0  /dev/sg4
> >> [8:0:0:0]    tape    IBM      ULTRIUM-HH5      BBNF  /dev/st0   /dev/sg2
> >> [8:0:1:0]    tape    IBM      ULTRIUM-HH5      BBNF  /dev/st1   /dev/sg3
> >> 
> >> But I am still confused about few bits of configuration not very well
> >> explained in the documentation. I have used LTO-4 Device section from the
> >> distribution bacula-sd.conf file as a template. Here is my questions:
> >> 
> >> a) I have added ChangerDevice directive to the Device resources for the
> >> drives, pointing to their corresponding raw SCSI devices (/dev/sg2, /dev/
> >> sga3), while Autochager has ChangerDevice configured as /dev/sg4. Is this
> >> configuration correct? I am assuming these tape raw devices only used for
> >> the purpose of running AlertCommand on the drives?
> > 
> > Obviously, the above assumption was wrong because btape crashes if I
> > specify anything other then the autochanger's raw SCSI device as the
> > ChangerDevice under Device resource for the tape drives.
> > 
> > Does this mean Device {...} will not localize variables specified inside
> > them? What about other resources? I could not find anything in the
> > documentation regarding the variables scope inside bacula-X.conf files.
> > 
> > Of course, I might simply hardcode /dev/sgX names into TapeAlert strings.
> > 
> > Thanks,
> > Ivan


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users


ADSM.ORG Privacy and Data Security by https://kimlaw.us