Today, I ran multiple SAV commands. Idea was to see if overflowing a tape
caused issues that were not detected. So, after three SAVs complated and
partway into the fourth, a tape change request was issued' I changed the
tape and entered G to continue. At the conclusion of that SAV, I ran an
additional SAV. No errors in the jobog with the exception of reporting
that 17 files were not copied. All had locks. Nothing beyond the notice
of 17 objects not saved in the joblog. Nothing at all in any of the logs
accessed by SST. Everything worked like it is supposed to work.

Wednesday, I try a full save again. At that point, if it errors off, I
will report whatever is available.

John McKee

On Sat, Aug 29, 2015 at 12:23 PM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 28-Aug-2015 14:15 -0600, John McKee wrote:

<<SNIP>> None of this explains why backup has failed the past two
times.

Looking around within SST, I never saw anything specific to tape.
Abxolutely no guarantee that I am looking in the right places with
SST.

Anyway, if anybody has other ideas, I would appreciate suggestions.


Perhaps for the [duration of the] two failing saves, post the joblogs [,
history, LIC Logs, and PALs] somewhere that they can be (re)viewed.

--
Regards, Chuck

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].