RE: Backup performance issue.

[Evan Harris <spanner@xxxxxxxxxx>]

Rob

I think you said that you had checked SST for tape errors and had found
none. Nevertheless these figures smack of tape retry errors if you can't
find anything else in the job log, the history log or the operator message
queue.

You've probably considered this, but is it possible that tapes are cycled
in such a way that the same tapes are re-used on the same days (and these
same days are the days you notice problems) ? This might go some way to
explaining your errors.

I used to check the SST tape log on a weekly basis looking for any bad
tapes, but the report never indicated any that it thought were going bad -
not even tapes that caused a backup to fail due to a media error.

Regards
Evan Harris

> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
>                                         Start of  2nd  3rd   4th  End of
> SAV
> Date                  Submitted  INZTAP   SAV*    Vol  Vol   Vol  or abort
>   Aborted?
> 12/9/2002   Monday        20:00   20:00  20:01  21:00 21:55 22:47   23:09
>   N
> 12/5/2002   Thursday      20:00   20:00  20:01  20:59 22:45 23:36   23:45
>   Y
>
> As you can see the time from the start of the second volume until the
> start of the third volume seemed to be rather large on the night the
> backup had to be aborted.  There were no messages in the joblog.  There
> was nothing indicated in the output created by the SAV command.  Yes,
> there were numerous other jobs running, (but NO Domino jobs).  Also
> included in these jobs were other saves.  Yes, at the same time that we do
> the save to this 3590 we run:
> a job to save to one 3581
> a job to save to another 3581
> a job to save some libraries to a save file.
> But, heck, these jobs run every night and don't seem to have any effect.
> And the performance data didn't seem to indicate any spikes.
>
> Rob Berendt