Sorry for the delay
Am 27.03.2015 um 01:21 schrieb Kern Sibbald:
> Hello,
>
> There is a section in the manual that provides a step by step
> procedure for testing writing to tapes. In addition to what John
> wrote you, there are two other obvious things for you to do:
running a version 3.0.x h
Hello,
There is a section in the manual that provides a step by step procedure
for testing writing to tapes. In addition to what John wrote you, there
are two other obvious things for you to do:
1. Ensure that tape drive hardware compression is turned on.
2. Send the Job report output when a
There is also some tests you can do with btape (chapter 3 from
http://www.bacula.org/7.0.x-manuals/en/problems/problems.pdf).
Best regards,
Ana
On Thu, Mar 26, 2015 at 1:00 PM, John Drescher wrote:
> On Thu, Mar 26, 2015 at 11:26 AM, Markus Rosjat wrote:
> > Hi there,
> >
> > I know this quest
> "John" == John Drescher writes:
John> On Thu, Mar 26, 2015 at 11:26 AM, Markus Rosjat wrote:
>> Hi there,
>>
>> I know this question was asked befor and maybe it will be again in the
>> future but I'm kinda frustrated with it.
>> We have a LTO-3 hp tapeloader and suddenly our jobs began t
On 2015-03-26 08:26 AM, Markus Rosjat wrote:
> Hi there,
>
> I know this question was asked befor and maybe it will be again in the
> future but I'm kinda frustrated with it.
> We have a LTO-3 hp tapeloader and suddenly our jobs began to randomly
> mark tapes as full even the tape was writen with h
On Thu, Mar 26, 2015 at 11:26 AM, Markus Rosjat wrote:
> Hi there,
>
> I know this question was asked befor and maybe it will be again in the
> future but I'm kinda frustrated with it.
> We have a LTO-3 hp tapeloader and suddenly our jobs began to randomly
> mark tapes as full even the tape was wr
