So I have this old saveset, that was made on another NW server. I have a 
list of the client IDs from that other NW server. So I created a client on 
my NW server with that old client ID, and scanned the tapes. (I scanned 
each tape with "scanner -m", then did an mminfo for the client I created, 
then did a "scanner -i" for the ssid that I wanted).

Then I extended the retention time. And this is what it looks like now:

>mminfo -avot -q ssid=1944942739 -r 
savetime(22),ssbrowse(22),ssretent(22),ssflags

     date     time         browse time          retention time    ssflags
  3/28/2008 7:00:34 PM  5/12/2013 2:41:45 PM  3/13/2020 8:52:39 AM vrF

But when I go to browse that client, it says no index was found. Yet there 
should be an index, especially since I did the "scanner -i".

When I scanned it into the index, I did this:

>scanner -s NW-Server -i -S 194492739 \\.\Tape2147483646
8909:scanner: using 'rd=Storage-Node:\\.\Tape2147483646' as the device 
name
8936:scanner: scanning sdlt320 tape 1127153768 on 
rd=Storage-Node:\\.\Tape2147483646
8939:scanner: sdlt320 tape 1127153768 already exists in the media index
8770:scanner: fn 257 rn 8466 read error No more data is on the tape.

8761:scanner: done with sdlt320 tape 1127153768


That should be a valid scan to add the index, right?

I don't know the exact folder name I want, and the whole saveset is like 
26G, made up of 300K small files. So I don't want to restore the whole 
thing somewhere, and then dig out the few files I need.

Why is this not browseable?

-- 
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>