Re: [Networker] Why doesn't nsrinfo show me saveset details?
> >> Just a related question here: what if you're scanning a whole tape,
> >> there's spanning save sets, but they don't all continue onto the same
> >> subsequent tapes? What does one do in that case? You have to break it
> >> down by individual save sets?
> > Scanner is supposed to be smart enough to see the ssid being scanned,
> > match it with the ssid it finds in the media db, and therefore just
> > the incoming info to the saveset.
Here's what you want to happen, when scanning a saveset that spans tapes:
>scanner -s NW-Server -S 2684190309 -i -t sdlt320 \\.\Tape2147483646
8909:scanner: using 'rd=StorageNode:\\.\Tape2147483646' as the device name
8936:scanner: scanning sdlt320 tape Tape-1 on
8939:scanner: sdlt320 tape Tape-1 already exists in the media index
8770:scanner: fn 161 rn 13153 read error No more data is on the tape.
29486:scanner: ssid 2684190309: NOT complete
8786:scanner: ssid 2684190309: 130 GB, 246555 file(s)
8761:scanner: done with sdlt320 tape Tape-1
8921:scanner: the following save sets continue on Tape-2:
client name save set save time level size files ssid
OldClient H:\Users 9/28/07 18:21 f 133263763868 246555
scanner: when next volume is ready, enter device name (or `q' to quit)
scanner: starting file number (or `q' to quit) ?
scanner: starting record number (or `q' to quit) ?
8917:scanner: continuing scan with tape on device
8936:scanner: scanning sdlt320 tape Tape-2 on
8939:scanner: sdlt320 tape Tape-2 already exists in the media index
8763:scanner: ssid 2684190309: SYNCHRONIZED at 130 GB, 246556 file(s)
You *need* to get that SYNCHRONIZED message. That indicates that you are
scanning in the proper order. In my case, there will be a 3rd tape. If the
tapes were not in the media db at all, that's when you have to first scan
as "scanner -m", so you can then determine the order to do "scanner -i".