UNSOLVED
"No such file" errors occurs on several clients after Networker server has been running for a few days
A backup admin colleague is getting "no such file or directory" backup errors on several-but-not-all clients.
The odd thing is that it can be resolved by rebooting the Networker server or restarting nsrd. Things are fine for a few days then start to go wrong again.
I have a ticket open with EMC but I was wondering if anyone else had any tips....when I search Powerlink for "no such file" using the exact phrase, I get hits on the individual words which doesn't help me much.
The clients are almost entirely windows 2003 servers, have VSS disabled and run versions of Networker from 7.2.1 to 7.4.2
Affects several clients; some share, some SQL, some application servers
I just found out that some of these clients are running quite old versions of Networker ( not as originally thought )
Have asked the local admins to try an upgrade.
There's nothing in the daemon logs on server or storage nodes abput this error
- Well, in case you quoted above it might be that share really was not there. Do you use static savesets? (listing those - I guess yes since you have shares) In such case it is possible that share or part of share was not available and you got the error.
It's more widespread than shares; some errors are on the C: drive and also I'm told one linux client is also affected.
The pointer to the problem is that a restart of the Networker server seems to cure the issue.
Many thanks for your continued interest.
butchej
8 Posts
641
0
Posted December 2nd, 2009 07:00
* xxxxnt3share1.xxxx.chevrontexaco.net:E:\share\NMA MIPS E:\share\NMA MIPS: No such file or directory
* xxxxnt3share1.xxxx.chevrontexaco.net:E:\share\Office Support Services 5 retries attempted
* xxxxnt3share1.xxxx.chevrontexaco.net:E:\share\Office Support Services E:\share\Office Support Services: No such file or directory