On 12/01/17 16:17, Charles wrote:
...
> To be thorough, the bacula-sd init script should not only run the mt
> rewoffl and mtx unload commands; it should also error trap their output.
> I suspect that, when our autoloader and backup server are powered up at
> the same time, the autoloader does
On 11/01/17 15:01, Alan Brown wrote:
> On 11/01/17 05:16, Charles wrote:
>>
>> According to both the man pages and experimentation, Debian Jessie's
>> mt and mtx do not support an unlock command.
>
> Whilst other debian versions do
>
> # mt --version
> mt-st v. 1.3
> default tape device:
On 11/01/17 05:16, Charles wrote:
>
> According to both the man pages and experimentation, Debian Jessie's
> mt and mtx do not support an unlock command.
Whilst other debian versions do
# mt --version
mt-st v. 1.3
default tape device: '/dev/tape'
lock (SCSI tapes) Lock the tape drive
On 10/01/17 22:25, Alan Brown wrote:
> On 10/01/17 06:04, Charles wrote:
>>
>> Have modified /etc/init.d/bacula-sd (Debian Jessie), adding mt rewoffl
>> and
>> mtx unload commands immediately before bacula-sd is started.
>>
>
> That should do the trick, although I'd add mt unlock to make
On 10/01/17 06:04, Charles wrote:
>
> Have modified /etc/init.d/bacula-sd (Debian Jessie), adding mt rewoffl
> and
> mtx unload commands immediately before bacula-sd is started.
>
That should do the trick, although I'd add mt unlock to make absolutely
sure.
>> ...
>> Other than that: update
On 10/01/17 03:17, Kern Sibbald wrote:
> ...The one thing that does not make sense
> to me, however, is your tapeinfo did not show any Tape Alerts ...
Thanks for being thorough, Kern.
Our bacula-sd.conf's Device stanza for the autoloader did not have an
Alert Command directive. Now fixed.
On 09/01/17 22:39, Alan Brown wrote:
> On 09/01/17 14:47, Charles wrote:
>> ... Bacula shows the tape wth status Error (simply
>> reflecting what the autoloader has told it?).
>
> Are you sure it was the loader which had the critical error?
No
> Most "critical errors" of this kind are bacula
Hello Charles,
If you do not know who Alan Brown is, I can say that he is at least 10
times more knowledgeable about the use of tape drives with Bacula than I
am, so I defer to his analysis. The one thing that does not make sense
to me, however, is your tapeinfo did not show any Tape Alerts,
On 09/01/17 14:47, Charles wrote:
>
> Hello bacula-users :-)
>
> Are any tools available to mend Bacula after almost certainly spurious
> errors reported by a tape autoloader?
>
> Within a few minutes of Bacula starting to use an autoloader which had
> been subject to an abrupt power outage, the
On 27/12/16 23:30, bacula-users-requ...@lists.sourceforge.net wrote:
> --
>
> Message: 8
> Date: Fri, 23 Dec 2016 10:13:58 +0530
> From: Charles <c...@charlesmatkinson.org>
> Subject: [Bacula-users] How to fix Bacula after tape autolo
Hello bacula-users :-)
Following misbehaviour by an HP StoreEver 18G2 LTO-6 Ultrium 6250 Tape
Autoloader, the list volume command shows two tapes with VolStatus Error
and one tape as Full with VolBytes 12,901,819,392.
We do not believe the information. Surely an LT06 cannot be filled with
11 matches
Mail list logo
