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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access denied to Media Database

Status
Not open for further replies.

sunt

MIS
Nov 6, 2002
29
US
Hi,
I have re-installed the 6.1.2 on server's D drive. I found that everytime when it backup a particular client the console prompt out a message like this:
"nsrd: media emergency: access denied to media database"

and then in the daemon.log I found a lot of:
"savegrp: SYSTEM error: Invalid argument"
"savegrp: Failed to update server, retrying."

finally the savegrp ended with failed.

I suspected a couple of things, hope you can shed some light:
1. there is hard disk problem on the server side for the D partition
2. there is hard disk problem on the client side
3. NIC problem on client side
4. any other?

Thanks
 
It is possibly the media index entries for this client.
Try an nsrim -X.
It may be that the client in question is using an old version of Networker, what version is it using?
 
The client is using 6.0.Build.153.
 
Have you tried the nsrim -X and stopping/starting Networker? Does it work then?
 
Yes I have tried the nsrim -X twice, the first time that output something like, client index xxx, xxx records has occupied xxxkb. etc.
The second time I ran it, it seems take long time to run nsrim -X. After I type in the nsrim -X in the command line and press enter, it holds for quite a while. During that time, remote console can not connect to the backup server (only seeing the star keep flying over). Finally, i crtl-c to break it and the console can connect right away.
Seems this command is only for informational, is this true?
 
Side note: Please upgrade your client asap.

Are you backing up this client in two different savegroups running at the same time? If so, then modify the schedule of one of them so that they don't conflict.

I don't think it's a problem on the client side. It's the NetWorker server cannot access it's databases.

It could be client index corruption as well. Run:

nsrck -L6 <client_name>
nsrim -X

It could be a problem with the d: drive. Anything's possible.

 
Yes it is probably some problem on d drive.
I found that when I open a folder from the file explorer it takes long time to display the whole tree in the left panel of explorer. During that time, the hard disk was spinning very hard.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top