Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

index notice: bad database header

Status
Not open for further replies.

SOLARFLARE

IS-IT--Management
Aug 13, 2000
3
0
0
US
Legato 5.5, suggestions about proper way to fix the following: (index / unix1)

05/24/04 08:44:03 nsrd: server notice: started
05/24/04 08:44:12 nsrmmdbd: media db is cross checking the save sets
05/24/04 08:44:22 nsrindexd: checking index for unix1
05/24/04 08:44:22 nsrindexd: Warning: /export/disk4/nsr/unix1/db missing file sr_x8
05/24/04 08:44:22 nsrindexd: Check failed for client unix1 (bad database header)
05/24/04 08:44:22 nsrd: index notice: Check failed for client unix1 (bad database header)
 
You may try to run nsrck to check anf repair the file index.
If this does not work, you have to recover the index backup.

With NW 5.x this is a bit more difficult than with NW 6 and 7. Prodeed as follows:

- stop the NW server
- delete /export/disk4/nsr/unix1/db
- start NW
- create a new database with nsrck -c unix1
- find out the save set of the last full index backup
- recover that save set recover -S ssid
- scan missing media, if required

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top