On Sun, 15 Jul 2012, Thomas Lohman wrote:
> This actually is a hardcoded "sanity" check in the code itself. Search
> the mailing lists from the past year. I'm pretty sure I posted where in
> the code this was and what needed to be changed.
Excellent; thank you! I have found your post and the re
This actually is a hardcoded "sanity" check in the code itself. Search
the mailing lists from the past year. I'm pretty sure I posted where in
the code this was and what needed to be changed. We have no jobs that
run more than a few days so have not made such changes ourselves so I
can't gua
Update. We are still seeing this in 5.2.10 as well.
It seems to happen more often towards the beginning of a series of jobs,
when a tape is first chosen (i.e. not when a job is directly using a
tape that's already been chosen and loaded into a drive by a previous job).
Stephen
On 7/5/12 7:
On Sat, 14 Jul 2012, Boutin, Stephen wrote:
> Try changing (or adding if you don't have it already) the heartbeat
> interval variable. I have about 160TB I'm currently backing up total &
> some of the boxes are 8-29TB jobs. Heartbeat is must, for large jobs, as
> far as I'm concerned.
Good ide
