From: Thomas G. <tho...@ic...> - 2007-08-22 12:01:50
|
Hi List, here are a few things i found during the translation: > We furnish such a script (mtx-changer) that works with mtx found > in the depkgs distribution. This script works only with single drive > autochangers. only single drive autochangers? false > Thus in principle, mtx-changer can be adapted to function with any autochanger program, a few lines later attention is invited to the fact that bacula doesn't support stackers and silos.why not? unclear regarding Volumes: > If no slot is given, or the > slot is set to zero, Bacula will not attempt to use the autochanger even if > all the necessary configuration records are present. Bacula will not use the Tape/Volume if no slot is given, all other Tapes (with correct slot and InChanger-flag) in the changer will be used. unclear > Current Bacula autochanger support does not include cleaning Maybe possible via an AdminJob? any examples available? > In addition, the console {\bf mount} command does not cause > Bacula to operate the autochanger, it only tells Bacula to read any tape that > may be in the drive. when i enter mount in the console, bacula asked which volume from which slot should be mounted, it is not only reading the drive=> it operates the changer-device > Normally this script will be the {\bf mtx-changer} script that we can provide, but it can in fact be any program. Normally this script will be the {\bf mtx-changer} script that we provide, but it can in fact be any program. better without the first "can"? > The only requirements are that the "commands" that Bacula uses are {\bf loaded}, {\bf load}, {\bf unload}, {\bf list}, and {\bf slots}. looks like there is something missing, The only requirements are that the "commands" that Bacula uses {\bf loaded}, {\bf load}, {\bf unload}, {\bf list} and {\bf slots} are supported by your custom {\bf Changer Command}. ? mtx-changer script: > Bacula checks the exit status of the program called, and if it is zero, the data is accepted. this is ok. > If the exit status is non-zero, Bacula ignores any information returned and treats the drive as if it is not an autochanger. unclear the drive is not an autochanger? on non-zero exit Bacula gives errors like 3307 Issuing autochanger "unload slot 15, drive 0" command. 3995 Bad autochanger "unload slot 15, drive 0": ERR=... Best Regards Thomas |
From: Kern S. <ke...@si...> - 2007-09-11 16:39:52
|
On Wednesday 22 August 2007 14:01, Thomas Glatthor wrote: > Hi List, > > here are a few things i found during the translation: > > We furnish such a script (mtx-changer) that works with mtx found > > in the depkgs distribution. This script works only with single drive > > autochangers. > > only single drive autochangers? > false Yes, that is out of date. All scripts now work with multiple drive=20 autochangers. I'll correct the English tonight ... > > > Thus in principle, mtx-changer can be adapted to function with any > > autochanger program, > > a few lines later attention is invited to the fact that bacula doesn't > support stackers and silos.why not? unclear Because they make a single pass through the casettes. They do not permit=20 random access to the "slots" as an autochanger does. I'll also make a not = in=20 the English version tonight. > > regarding Volumes: > > If no slot is given, or the > > slot is set to zero, Bacula will not attempt to use the autochanger ev= en > > if all the necessary con=EF=AC=81guration records are present. > > Bacula will not use the Tape/Volume if no slot is given, all other Tapes > (with correct slot and InChanger-flag) in the changer will be used. > unclear If the catalog does not have a non-zero Slot defined for a Volume, Bacula h= as=20 no way to know where it is in the autochanger, and hence cannot access. =20 Typically, this condition is fixed with an "update slots" of you have=20 barcodes or an "update slots scan" if you do not. The update slots figure= =20 out what Volume is in each slot and update the catalog. > > > Current Bacula autochanger support does not include cleaning > > Maybe possible via an AdminJob? any examples available? No, but I think you can probably "unmount" the autochanger with a bconsole= =20 script, then call mtx to load the cleaning casette, wait an appropriate tim= e,=20 then "mount" the autochanger again. > > > In addition, the console {\bf mount} command does not cause > > Bacula to operate the autochanger, it only tells Bacula to read any ta= pe > > that may be in the drive. > > when i enter mount in the console, bacula asked which volume from which > slot should be mounted, it is not only reading the drive=3D> it operates = the > changer-device Well, that is no longer true. Bacula now needs to know what Slot you want= =20 mounted. > > > Normally this script will be the {\bf mtx-changer} script that we can > > provide, but it can in fact be any program. > > Normally this script will be the {\bf mtx-changer} script that we provide, > but it can in fact be any program. better without the first "can"? Yes, correct. The first "can" should be deleted. > > > The only requirements are that the "commands" that Bacula uses are {\bf > > loaded}, {\bf load}, {\bf unload}, {\bf list}, and {\bf slots}. > > looks like there is something missing, > > The only requirements are that the "commands" that Bacula uses {\bf > loaded}, {\bf load}, {\bf unload}, {\bf list} and {\bf slots} are > supported by your custom {\bf Changer Command}. ? No. What is meant is that you can have any script you want, but the only=20 requirements for that script is that it must support the commands ... > > mtx-changer script: > > Bacula checks the exit status of the program called, and if it is zero, > > the data is accepted. > > this is ok. > > > If the exit status is non-zero, Bacula ignores any information returned > > and treats the drive as if it is not an autochanger. > > unclear > the drive is not an autochanger? Well, it produces an error, then will ask you to manually mount the tape on= =20 the autochanger drive (i.e. treats it like it is a standard tape drive=20 requiring an operator mount). > > on non-zero exit Bacula gives errors like > > 3307 Issuing autochanger "unload slot 15, drive 0" command. > 3995 Bad autochanger "unload slot 15, drive 0": ERR=3D... Yes, that is correct. Nice job. Thanks for finding these problems with the manual. Best regards, Kern > > > > > Best Regards > > Thomas > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel |