A bunch of frozen media!!

[j1000]

I found that almost a lot of media was frozen wheN I checked.

backups failed with error 196 for lack of media but the media was frozen.

I unfrooze the media and restarted the server and found that the media has frozen again.

Any ideas please? some info and logs below; seems something is locked?

Info:

Symantec Netbackup 7.5.0.6

Windows server 2008 r2 is the OS

Logs;

00:02:11.156 [976.5412] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1420723456 -jm
00:02:11.156 [976.5412] <2> drivename_open: Called with Create 0, file IBM.ULT.000
00:02:11.156 [976.5412] <2> drivename_checklock: Called
00:02:11.156 [976.5412] <2> drivename_checklock: File is locked
00:02:11.156 [976.5412] <2> report_drives: DRIVE = IBM.ULT.000 = TRUE CURTIME = 1420761731
00:02:11.156 [976.5412] <2> drivename_close: Called for file IBM.ULT.000
00:02:11.156 [976.5412] <2> report_drives: MODE = 0
00:02:11.156 [976.5412] <2> report_drives: TIME = 1420747330
00:02:11.156 [976.5412] <2> report_drives: MASTER = bkserver.domain.com
00:02:11.156 [976.5412] <2> report_drives: SR_KEY = 0 1
00:02:11.156 [976.5412] <2> report_drives: PATH = {5,0,1,0}
00:02:11.156 [976.5412] <2> report_drives: MEDIA = BK052
00:02:11.156 [976.5412] <2> report_drives: REQID = -1420723364
00:02:11.156 [976.5412] <2> report_drives: ALOCID = 8875
00:02:11.156 [976.5412] <2> report_drives: RBID = {F9F7065B-9A89-4689-9833-285D17ED6168}
00:02:11.156 [976.5412] <2> report_drives: PID = 3624
00:02:11.156 [976.5412] <2> report_drives: FILE = D:\Netbackup\db\media\tpreq\drive_IBM.ULT.000

[j1000]

Media has been frozen but may freeze again as it did before. Any ideas?
 

[SymTerry]

Freezing media is a safety measure taken by the NetBackup application to help prevent further errors, drive damage, or possible data loss. Look for job errors. Check out the doc: How to troubleshoot frozen media on UNIX and Windows (TECH21473)

[Marianne]

The piece of bptm log is not helping.

You need the bptm log on the media server that logs the error as and when issue with media is experienced during backup operation by that particular media server.

Please copy the bptm log to bptm.txt and upload as File attachment.

Please post 'errors' file as well (see TECH21473 as per above post).

[Michael_G_Ander]

Also check the library logs to see if there is anything that could indicate a problem, I would include a message about cleaning the problems even though they are often shown as info messages

[j1000]

Errors of failed jobs include codes 6, 156 and 196

[Marianne · Accepted solution]

Seems like some tape drives were replaced at some point without updating NBU or else Device mapping has changed because no Persistent Binding was done at HBA level.

20:02:26.026 [5552.1476] <4> manage_drive_attributes: expected serial number [D120106357], reported [K120106248]
20:02:26.026 [5552.1476] <2> send_MDS_msg: MEDIADB 1 8902 ESX075 4000058 *NULL* 6 1420923758 1420983579 1423402779 0 1802596358 107 107 10 1 0 513 1024 0 28165860 0
20:02:26.026 [5552.1476] <16> manage_drive_attributes: FREEZING media id ESX075, Medium identifiers do not match

20:08:28.434 [5552.1476] <4> manage_drive_attributes: expected serial number [B120106141], reported [A120106160]
20:08:28.434 [5552.1476] <2> send_MDS_msg: MEDIADB 1 8902 ESX098 4000083 *NULL* 6 1421092887 0 0 0 0 0 0 10 1 0 17 1024 0 0 0
20:08:28.450 [5552.1476] <16> manage_drive_attributes: FREEZING media id ESX098, Medium identifiers do not match 

(many more such entries...)

How to proceed?

Firstly find out which make/model HBA in this media server, then download the HBA utility from the vendor's web site (e.g. SanSurfer for Qlogic HBA).
Use the utility to enable Persistent Binding.

Once Persistent Binding is in place, delete existing tape drives in NBU, then use Device Config Wizard to re-add them.

[j1000]

Logs attached.