SUMMARY: NSR stopped mid-backup

From: Keller, Raymond L. RK0514 <RKeller_at_williams-int.com>
Date: Fri, 02 Aug 96 13:55:00 PDT

Digital Support solved this one quickly.
The index and bootstrap backups for an incremental are level 9 backups. The
solution was to add level '9' to the pool definition. Interesting to note
is that for other backups I have run (full, 1, 2), the level of the index
backup matches the actual data backup.
___________________________________________________________________

The original posting:
A scheduled NSR backup stopped after backing up the system save_sets but
prior to backing up the index and bootstrap.
It then issued the following message:
     backup to pool 'Default' waiting for 1 writable backup tape
although I was using pool 'Incr'.

Details:
DU 3.2D-2 NSR V3.2
Only one group active: 'Server'
Only one client in group (the server itself).
Using single TLZ07 DAT drive (no loader).
Incremental 'i' backup backed up all 6 requested file systems to tape
'Alpha.Incr.002' from pool 'Incr'.
At present time, the tape volume shows <1% used and appendable.
No other writable volumes for pool 'Incr' currently exist.
No indication of tape (or other) errors.
The 'Messages' window in nwadmin listed all of the appropriate " done saving
to pool 'Incr' " messages, but they don't show up in /nsr/logs/messages,
although the " waiting for writable " messages do.

Any suggestions will be appreciated. I logged a call to Digital, but I
can't afford to wait a week for them to respond.
I also just subscribed to the networker list, as suggested to another user
yesterday by j.studnicka_at_ic.ac.uk.

Ray Keller
Williams International
Walled Lake, Michigan
RKeller_at_williams-int.com
Received on Fri Aug 02 1996 - 21:07:27 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT