Recently i noticed that browsing saveset recover threw errors about bad
file discriptor, directed recovery was failing, i noticed that
1. index path for the server was double, i.e index\clienta\clienta.
2. Few monghts ago server joined AD and its full name had changed from
cleinta to domain.clienta.
3. Backups on this clients have been sucessfull ever since.
Bootrap used during DR was Level FULL, however, i failed to recover file
level backups from any clients, running nsrck -L7 failed and no client
index was recovered, from recent tapes, the tape that was requeted by
networker was 2 months old, what would have caused this correption ?, why i
did not notice this during reqular backups and Networker did not warn me of
any problems ?
i corrected the index path on the backup server and rerun nsrck -L7 this
seems to have brought back the recent backup, i am not getting any errors
any more when browsing servers index and file level recovery atleat fromt
he time i corrected this issue is browsable.
What can i do to ensure we have alternate method to backup all client index
regularly, i though Bootstrap level FULL backed up client index in FULL
I am thinking of implementing savegrp -O to backup client indexes
independently, will i be able to restore it outside of nsrck -L7 ?
What are the best practices\scripts you may have that you can share.
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
wit this list. You can access the archives at
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER