In regard to: Re: [Networker] Recovering an Index, Robert Brault said (at...:

If you are getting them from tape it is the "scanner" command.

Scanner should be a last resort.  nsrck -L7 is what should generally
be tried first.

In Richard's case, he can

- just go back to whatever the closest index backup was that happened
  before the index move.  The only way he would have to resort to scanner
  in that case is if the timeframe he needs to recover to happened between
  the index backup that he recovers and when the indexes were moved.  Even
  in that case, it's going to be faster to load the closest previous
  index he can find using nsrck -L7, and only then should he use scanner
  to build index entries for the savesets that happened after the index
  backup but before the mass index move.

- try Davina's second suggestion

Yes this is fairly easy. When you run nsrck -L7 clientname, it merges an
index backup into the existing index. So this gives you a couple of
options. If you have an index backup from just before the old indices
were moved away you could just run nsrck -L7 specifying the date of the
backed up index. Otherwise you could swap the indices over (move the old
one into place) and run nsrck -L7 on a recent index backup.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER