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
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
