Ryan Novosielski wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Damian Brasher wrote:
>
>> Ryan Novosielski wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Damian Brasher wrote:
>>>
>>>
>>>> Hi List
>>>>
>>>> When a tape is missed for one of our weekday sets the next evening
>>>> the previous days, missed, tape is still requested even though the
>>>> job should have expired. I have used Volume Use Duration = 22h see
>>>> below.
>>>>
>>>>
>>> The clock starts ticking on the first tape write.
>>>
>>>
>>>
>> Job {Max Start Delay = 22h} should prevent manual intervention then?
>> Damian
>>
>
> Keep replies on the list -- you'll get more assistance that way.
>
Sure - seems like my reply list was incorrect this morning - will check.
> That is possible. Seems to me what's actually goofing you up here is
> that the backup is hung waiting for a tape, since it wasn't there when
> the backup started. The next backup will then wait for that one. A
> cancellation should allow the next backup to start anew. It
> theoretically want the wrong tape, but as long as your tape is ABLE to
> be written, AFAIK, it will be written to when it is presented with that
> tape.
>
>
A cancellation cleared the job queue, It looks as some intervention is
unavoidable when a
tape is missed as I have been working through this problem for a while
now. However some
interventions is required, the tape needs to be changed! so to cancel a
job is not a huge amount
of extra work. It would be nice if entering the next tape was all an
untrained user needed to do.
Damian
--
Damian Brasher
Systems Admin/Prog
OMII-UK ECS
Southampton University
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
