Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Tapes becoming freeze

Created: 29 Jul 2014 • Updated: 15 Aug 2014 | 10 comments
This issue has been solved. See solution.

Hello all,

Few weeks ago I realized that a lot of jobs were failing with status 96 and 196. We were adding tapes, the backup windows was ok so no obvious reason for the failed jobs. Then I realized that the tapes that were coming back from vault and we were loading into the robot was actually on freeze state.

I manage to check all reloaded tape with:

bpmedialist -m XXXXXX
bpimmedia -mediaid XXXXXX, and then:
bpmedia -unfreeze -m XXXXXX

So I don't have a problem with it anymore, as long as I check tape by tape. My question would be, why is this happening:

My NBU is 6.0MP7 running on a Windows 2003.

Thanks in advance!!

Operating Systems:

Comments 10 CommentsJump to latest comment

INT_RND's picture

That is odd because vault won't auto-eject a frozen tape. It's possible that the tapes are being write-protected when they are sent offsite. If Netbackup attempts to write to a write-protected tape it will become frozen.

Basically, I'm saying that vault is not the cause of the frozen state.

Here is the troubleshooting guide for frozen media:

http://www.symantec.com/business/support/index?page=content&id=TECH21473

Marianne's picture

Best to find out why tapes are getting Frozen as soon as possible - not when they get back on site.

You may want to keep an eye on 'Media Logs' report on a regular basis.
Use Filter to exclude 'Info' type output in Severity column. You will be left with Warning and Error logs.
Also add VERBOSE entry to ...Veritas\volmgr\vm.conf on all media servers and restart NBU Device Manager service.
Exact reason for media being frozen will be logged in Windows Event Viewer Application log.

PS:
NBU 6.x ran out of support almost 2 years ago.
PLEASE upgrade!

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
LEAQUI's picture

Hi Marianne,

Thank you for your assistance.

But, what should I filter to exclude "Info"? And how do I add VERBOSE to that file?

Thanks in advance.

Riaan.Badenhorst's picture

Are you 100% sure they came back frozen and didnt get frozen after coming back?

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Marianne's picture

Please download System Administrator's Guide for Windows, Volume 1 : http://www.symantec.com/docs/TECH43931 

Chapter 5 - Viewing NetBackup Reports
On page 299, have a look at 'Standard Toolbar', 
You will see an icon that look like a funnel. That is the 'filter' icon.

So, run Media Logs report.
Select the filter icon.
Select 'does not contain' and in Severity column type Info.

This will exclude Info messages and leave you with Warning and Error messages.

To add VERBOSE entry to vm.conf, open the file with a text editor such as Notepad and add VERBOSE on a new line at the bottom of the file.
Save and close the file.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
LEAQUI's picture

Thank you both.

Riaan, no I'm not sure, how could I check it?

Marianne, done it. Checking the Media Logs, from earliest available until current time, only 3 messages are shown, should I increase the logging level? It's current set up as global, which is 0.

Thanks.

Riaan.Badenhorst's picture

You can check the bptm logs on the media servers for entries stating

"<16> write_data: FREEZING media id"

This is usually followed by something like "Medium identifiers do not match" or "Externl event caused rewind during write, all data on the media is lost" or what ever the problem is that was found with the media.

This would show that they were frozen on that date and weren't frozen already.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

SOLUTION
Marianne's picture

Have you had any media that became frozen lately?
If not, there will be nothing in bptm log or Media Logs report or in Event logs.
That is why I suggested that you run the report on a regular basis - once or twice per week so that you can catch the tapes getting frozen while there are still logs available to find the reason.

Apart from Media Logs report, you can also run Media Summary (with Verbose option selected) or Media List report and look for tapes with (new) Frozen state.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

LEAQUI's picture

Brilhant!!

Understood what you both are telling me, and from now on I'll keep an eye on it.

Thank you very much!!

INT_RND's picture

Please mark this question solved once you have figured it out.