Highlighted
vzoli
1 Copper

lot's of volume id not in media index message

I have a networker 7.6.3.7 environment with a lot of storage nodes.

We got the following error messages :

2504 10/03/2012 12:30:04 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=nwszesn04.t-yyyy.com:/nsr/scsiDISK <NULL> operation failed: scsiDISK.001 (volume id 1214883451) not found in media index

72504 10/03/2012 03:50:46 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=crmdbrtst1:/dev/tape/by-id/scsi-350050763001a3e1a-nst mount operation failed: 1month.1846 (volume id 1934724341) not found in media index

72504 10/03/2012 04:30:08 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=nwszesn04.t-yyyy.com:/nsr/scsiDISK <NULL> operation failed: scsiDISK.001 (volume id 1214883451) not found in media index

72504 10/03/2012 05:47:19 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=crmdbrdv11:/dev/tape/by-id/scsi-350050763001a3e18-nst <NULL> operation failed: 1month.1851 (volume id 1297190701) not found in media index

72504 10/03/2012 06:01:56 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=migdbdev0.mig.yyyy.com:/dev/tape/by-id/scsi-350050763001a3e18-nst mount operation failed: 1month.2331 (volume id 1330747624) not found in media index

72504 10/03/2012 06:02:58 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=crmdbrdv11:/dev/tape/by-id/scsi-350050763001a3e18-nst mount operation failed: 1month.2334 (volume id 1028758355) not found in media index

72504 10/03/2012 06:40:04 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=nwszesn04.t-yyyy.com:/nsr/scsiDISK <NULL> operation failed: scsiDISK.001 (volume id 1214883451) not found in media index

72504 10/03/2012 08:33:05 PM 2 0 0 4276040928 15281 0 xxx.yyyy.com nsrd rd=migdbdev0.mig.yyyy.com:/dev/tape/by-id/scsi-350050763001a3e1a-nst mount operation failed: 1month.1846 (volume id 1934724341) not found in me

It gets from different SN-s from different volumes.

We created 3 new AFTD, but they also give this type of errors. After this error the AFTD-s unmounted and backups were stopped.

If we remount them, it works properly.

What could cause this type of behaviour? What should I check?

Zoltan

Tags (4)
0 Kudos
3 Replies
Panwar
2 Bronze

Re: lot's of volume id not in media index message

Hi Zoltan,

If you again recieve error message "not in media index" for the AFTD device. you can run scanner -m AFTD Device name.

Scanner - m will read the label from  AFTD device and update media database.

Regards

Panwar

vzoli
1 Copper

Re: lot's of volume id not in media index message

Hello,

Yes it is true, but it doesn't solve the root cause of the problem. Main problem is the device is unmounted, and it has to manually remount to work again. Sometimes it stucks and we have to reset the AFTD to work it again.

BR Zoltan

0 Kudos
SurajPujari
2 Iron

Re: lot's of volume id not in media index message

Have a keen look on your daemon.raw file, may be it can help you with what makes your AFTD unmount while Backups are running on it.

0 Kudos