Previous Post Next Post

OS and NBU

Created: 12 Oct 2012 | Updated: 13 Oct 2012 | 5 comments

Andy2345

This issue has been solved. See solution.

When there is an error on the media,It is first locked in the OS or in NBU ?
When a media is mounted on a drive ,then only the error must be locked.Not before that?
When we run inventory,Does any logs generate on OS?I mean if a media is protected error etc?
In case of write protected,Media should be in drive so that logs can be generated?Is it first on OS or on NBU?

Discussion Filed Under:

Comments RSS Feed

Comments 5 Comments • Jump to latest comment

Yasuhisa Ishikawa Partner Accredited Certified

OS and NBU - Comment:12 Oct 2012 : Link

OS does not lock media. OS is not aware of media availability, and does not manage media.

When media error occurs frequently - 3 times in 12 hours by default - NetBackup set media into FROZEN state to prevent them from use.

in general, OS deos not log errors, but NetBackup logs into its own log file, syslog(UNIX), and Application Log(Windows).

No log for inventory result.Write protect is detected at mount, and NetBackup logs it into error dbehich you can look by Reports in GUI or bperror command.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Andy2345

OS and NBU - Comment:13 Oct 2012 : Link

Read/ Write errors

The reading or writing operation is performed at the operating system/ tapedriver level. Therefore, although this issue is detected and reported in the NetBackup logs, it is not caused by NetBackup.

The cause of read/ write errors are usually an issue with the tape drive or media cartridge.Read/ Write errors

The reading or writing operation is performed at the operating system/ tapedriver level. Therefore, although this issue is detected and reported in the NetBackup logs, it is not caused by NetBackup.

The cause of read/ write errors are usually an issue with the tape drive or media cartridge.

I have read this in forum.Is it correct with my query?

mph999 Symantec Employee

OS and NBU - Comment:13 Oct 2012 : Link

I recognise that - it is from a Technote I wrote and is 100% correct.

When there is an error on the media,It is first locked in the OS or in NBU ?
When a media is mounted on a drive ,then only the error must be locked.Not before that?
When we run inventory,Does any logs generate on OS?I mean if a media is protected error etc?
In case of write protected,Media should be in drive so that logs can be generated?Is it first on OS or on NBU?

1. OS doesn't lock anything. NBU will freeze a media or down a drive if 3 errors are detected on that tape or drive within 12 hours BUT for certain errors, it will freeze the tape, or down the drive instantly.

2. If there is an issue with the library loading the media physically into a drive then I guess this is a time the media might be frozen, even though it was never mounted. Also, if the media makes it into the drive, but cannot be mounted, then it could be frozen.

3. How is an inventory going to detect if a media is write protected, so no. BUT, when an inventory is run, I'm fairly sure something is logged in robots log, BUT, nothing that includes antything like barcodes or tapeinfo ...

4. No idea - why does it matter, write protected media will be detected as a tapealert will be sent so it should log in bptm. Seeing as the 'write protect' issue is detected by the tape firmware, passed to the tape driver it has to go via the OS to get to NBU, so I would image that the error is first logged in the OS - but why does it matter where it is logged first.

Martin

Regards, Martin

Setting Logs in NetBackup:

http://www.symantec.com/docs/TECH75805

SOLUTION