NSR - Trying to recover earlier index database

From: David Hume <dhume_at_gds.CA>
Date: Tue, 03 Nov 1998 15:19:27 -0800 (PST)

Running Networker on Digital UNIX 4.0D

Recently upgraded to version 4.4 from 4.2. Since then, have
realized current database is corrupt and/or out of sync,
and would like to try earlier version (created by NSR 4.2)
of index database instead.

(Name of the client, which also happens to be the NSR server,
has been changed to protect the innocent :-)

mminfo -av shows like the following relating to the index:

ServerDaily.006 host4.dom.bc.ca 7/02/98 22:41:14 4189 MB 19269 cb full /usr/local/nsr/index/host4.dom.bc.ca
ServerDaily.006 host4.dom.bc.ca 7/02/98 22:41:15 4 KB 19270 cb full <1>/usr/local/nsr/index/host4.dom.bc.ca

(It is quite a large index... and I do not understand what the constant
 4 KB 'continuation' file would be)

With the appropriate tape above mounted, have tried the following,
from _various_ different current-working-directories (/ , /usr/local/nsr,
/usr/local/nsr/index) trying to relocate old index elsewhere
before moving into the actual location

---------------------------------------------

host4# recover -d /usr/local/nsr/get.back.index -s host4.dom.bc.ca -S 19269 /usr/local/nsr/index/host4.dom.bc.ca

Recovering files within /usr/local/nsr/index/ into /usr/local/nsr/get.back.index

nsrindexasm -r ./host4.dom.bc.ca/db
nsrindexasm: Unable to translate /usr/local/nsr/get.back.index/host4.dom.bc.ca/db into a host name

./host4.dom.bc.ca/
Received 2 matching files from NSR server `host4.dom.bc.ca'

---------------------------------------------

All of the above takes quite a while to run, and at the end of
it, 2 files have _not_ been written anywhere on disk that I
can tell, certainly anywhere expected (and the index size is
such I believe I would notice if files got written somewhere
UNexpected)

So I guess there's a couple of queries here:

>From anyone who has tried to restore an earlier index from Networker
itself and succeded, would appreciate any tips/how to's/glaring errors
spotted with the above you can provide.

Does anyone know why (and if that's the reason for no success)
I am getting the "Unable to translate /usr/local/nsr/get.back.index/host4.dom.bc.ca/db into a host name" error from nsrindexasm?

I can be reached at dhume_at_gds.ca

Much thanks in advance,

        Dave Hume, GDS & Associates, Victoria BC Canada

P.S. Having said all the above, I take it this would be a bad
        time to also mention the company here wishes to go
        to NSR version 5.2 sooner rather than later... :-)
Received on Tue Nov 03 1998 - 23:20:23 NZDT

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