Folks,
I am running DEC Network Save and Restore (V3.1A) on an Alpha 2100
(Digital Unix V3.2C). To determine whether the overnight backup
has completed successfully, a script is run each morning which
basically grep's for "saveindex: bootstrap" in the daemon.log.
Now I am finding that this line is sometimes missing from the
log, although all other signs point to a successful dump. Running
'scanner' on backup tape also lists the index as having been backed up
OK, but it displays an error line after bootstrap
line as follows:
mercury /i64 9/19/96 1:45 1 155917192 1101 31956 E
mercury / 9/19/96 1:47 1 62812 69 31957 E
mercury /usr 9/19/96 1:47 1 135037656 923 31958 E
apollo /usr/var/nsr/index/mercury 9/19/96 1:53 1 6852824
3 31959 E
apollo /usr/var/nsr/index/apollo 9/19/96 1:54 1 4836020
8 31960 E
apollo bootstrap 9/19/96 1:55 1 521556 13 31961 E
scanner: fn 168 rn 0 read error No space left on device
scanner: done with tz87 tape WEEKLY-3-2
Has anyone seen this error line before and does it have any significance
to the reliability of the backup of the index? By the way in the above
example, there was more than 50% capacity left on tz87 tape. And is this
connected to the "saveindex: bootstrap" line not being present in the log?
Thanks
Paddy
---------------------------
Paddy Croskery
Computing Services
Queens University
Belfast BT7 1NN
---------------------------
Received on Thu Sep 19 1996 - 16:37:23 NZST