i have a strange problem whcih disappears after networker services restart.
after few days of running i have a strange state of library devices - Library device, active while it has no tape loaded nor writes any data.
problem is that the queued jobs are still waiting for the devices to be "free" thus backups are not running as they should.
any idea what might cause this to happen? i do not remember any changes to the environment and looks like this problem came up just from nowhere. this is the 2nd time i have experienced this. can it be because od automatic unloading of tapes ? the tape drives are not shared
Did you verify NMC is not playing trick with you? I have seen NMC not updating status sometimes giving false alarms.
If you are sure something is going on, check on server for ansrd and nsrindexd processes and to what task they have been allocated. That is if you have UNIX based server easy; with Windows you will need to use some additional tools to check out what is going on (I believe PowerShell can do it too).
I have faced this problem.... I heard that it is due to the new Leadville drivers tat EMC uses..
.
1.The solution to this is to restart he networker services(Not good).
or
2. Load the tapes manually, and u will be suprised to find once u do that the library starts working fine and will load tapes automatically in case of future Pending requests.
> " heard that it is due to the new Leadville drivers tat EMC uses."
Did you hear that from EMC? Because what you said can only be applied to Solaris 10 where instead of LUS NW will try to use OS's LeadVille drivers (as they are integrated with OS)?
Since you mentioned restaring NW services which is more term used on Linux and Windows, I wonder if we are on the same track...
even if i load the tape manually the backup does not start/continue. i have to restart the services always. it happens on ndmp storage nodes only and i found these errors in the logs
9023 2/12/2009 22:35:44 (pid10548) failed to establish connection to NDMP server, Could not find storage node in the RAP database! 8677 2/12/2009 22:35:53 (pid10548) WARNING fixed volume filemark not in sync with tape volume:MV6367 next:5 VWFN:4 ssid:4145436363 0 2/12/2009 22:36:08 (pid10548) device resource lookup fails 9023 2/12/2009 22:36:08 (pid10548) failed to establish connection to NDMP server, Could not find storage node in the RAP database! 9039 2/12/2009 22:36:08 (pid10548) ndmp tape setstate failed 38758 2/12/2009 22:36:08 nsrd media warning: rd=be-s0570-mx1.adroot.local:nrst4l (NDMP) opening: unknown error
ble1
6 Operator
•
14354 Posts
•
56186 Points
638
0
Posted November 18th, 2009 13:00
Did you verify NMC is not playing trick with you? I have seen NMC not updating status sometimes giving false alarms.
If you are sure something is going on, check on server for ansrd and nsrindexd processes and to what task they have been allocated. That is if you have UNIX based server easy; with Windows you will need to use some additional tools to check out what is going on (I believe PowerShell can do it too).