Hi Phil,

     Is this behaviour displayed only by the library connected to the storage node or is it also for the library connected to the networker server also? I would recommend you to do a controlled scavanging of the media database.

HTH,

Rovin D'Souza.

Hi Phil,

Is it Happening to a particular devices & is the SN is of windows flavour , If yes check the drive ordering for these drives.

Also verify that the verify label on inload option os checked in the JB properties.

Regards

Thank you for your input.

I ran checks on the index and media database (nsrim -X, nsrck -L6) and removed duplicate volumes.

The Storage Node is configured on a Windows 2003.

The library is only attached to the Storage Node and only has one tape device.

The behaviour is only on the Storage Node.

When running one of the inventories I checked the option 'verify label'.

At the moment I took an inventory again and the backup is running fine. Only when the scheduled backup runs, the volumes become unlabeled ...

Hi phil ,

             How the Storage Node connected to the Networker server , Kindly check there are two Ip has been configured for the Storage Node , because i face the same Problem i do configured two IP in the storage node and even its not in the DHCP Because of that it gets disconnected immediately . if you try to take inventory all tapes will show lalbeled and after few min all the tape will go the unlablled state rite .

Rajesh S 

Yep, that is the bevahiour we are facing too ...

The Storage Node has two fixed IPs; one is for the backup (10.0.0.6 (backup over VPN) ) and the other is for the internal services it provides (192.168.100.80) . The firewall logs are clean concerning the backup, no dropped/rejected packets or timeouts.

I committed two changes: network performance tuning (to prevent connection time outs, just in case) according the procedure from the networker procedure generator and I disabled the nsrauth authentication method (esg110616:  GSS Authentication can cause inter-process connectivity issues) . Fingers crossed :-) .

Then you can add both the IP in the etc/host entry and remove the Storage node and again add the storage node once again and try to take inventory ,Hopefully this will work . Once this has not worked ,  then remove one Ip and again add the storage Node , Atleast we can come in Conculsion what makes the issue . I have done in my setup like removed one IP and added the NIC in the Bonding . Then it has worked fine .

Rajesh S 

Thanks Rajesh for the information.

In fact, the hosts' files (and /nsr/res/servers of the SN) of the server/storage nodes are the first things I configure in a NetWorker environment to avoid dns problems. But, it is good to point out to remove and re-add the storage node and configure the hosts file first with one IP. I will try that. I am glad to hear it worked for your environment.

Regards.

Hi,

since this is a windows server, make sure the removable storage service is disabled. If windows is somehow accessing the library, this may mess up Networker's information about it.

Hello,

I disabled the Removable storage services (when I installed NetWorker) . Although I did not resolved the issue yet, 'coz I am on a project with a deadline, I have a clue which is pointing in the direction of HP Insight management software. Probably I will pick up this issue tomorrow and will update later on. Thanks for thinking with me.