question on error msg in daemons.log

[a222401]

hi,
C an somebody help to understand these 2 lines

09/01/03 03:05:32 PM nsrmmdbd: WISS error: Unable to mount D:\nsr\mm\mmvolume6: bad database header

09/01/03 03:05:32 PM nsrmmdbd: media db must be scavenged

 

[birky]

Hi

If I remember correctly then this message usually indicates that your media db is corrupted.

nsrim -X (checks the media db)

If db corruption is shown then try the following;-

Unix;-

1) nsr_shutdown -a
2) rename the media db (/nsr/mm)
3) start daemons using nsrd
4) recover media db using mmrecov

Windows;-

1) Stop Networker services
2) rename media db install_path/nsr/mm
3) restart Networker services
4) recover media db with mmrecov

This usually works with versions prior to v7 but, I've been told that if you receive this error in v7 then you should contact Legato Support as it could be due to a fatal error.

Good luck

 

[605]

Do not shoot too far! - mmrecov is the last tool you should
use. The WISS (WIsconsin Storage System) database 'only'
wants to be scavenged. To do this, please proceed as follows:

- Stop all NetWorker daemons.
- In the directory ..\nsr\mm\mmvolume6 , delete only all
index files for the media database:
clients_i*.*
ss_i*.*
vol_i*.*
- Restart NetWorker.
- Examine the file ..\nsr\logs\daemon.log .
You will see the following message (example):
04/07/02 21:04:52 nsrmmdbd: WISS error: Unable to mount
Z:\NSR\mm\mmvolume6: bad database header
04/07/02 21:04:52 nsrmmdbd: media db must be scavenged
04/07/02 21:04:52 nsrmmdbd: media db scavenge successful
04/07/02 21:04:52 nsrmmdbd: WARNING: clients file missing from
Z:\NSR\mm\mmvolume6
04/07/02 21:04:52 nsrmmdbd: media db is cross checking the save sets
04/07/02 21:04:52 nsrmmdbd: media db is open for business
04/07/02 21:05:02 nsrindexd: Running nsrck to check client file indices

- Examine the directory ..\nsr\mm\mmvolume6 .
All the index files you deleted are back again.
- Restart the NetWorker server.
- Examine the file ..\nsr\logs\daemon.log once again.

The previous error message shall not be reported any longer.
If you still have problems, then you should restore the last
bootstrap with mmrecov.