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

Issues with our NBU

Created: 08 Dec 2012 • Updated: 14 Jan 2013 | 7 comments
This issue has been solved. See solution.

Hi Guys,

 

There are some issues that we are constantly seeing in our environment. They may be small to solve if only i know why they are cropping up and what is the reason that made them to pop up again like they are actually related to drives/robots/medias :

 

Tape Library disappears from Robotic host

Backup failing with Media Write Error.

Missing Drive Path

Drives in PEND Status
 

 

help would be appreciated..thanks

 

Comments 7 CommentsJump to latest comment

Marianne's picture

None of these errors are CAUSED by NBU.  You have device-level issues.

You need to start troubleshooting at OS and device level.

NBU relies 100% on the OS for device access and I/O.

Check OS log files for device-related errors.

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

RLeon's picture

Tape Library disappears from Robotic host
Backup failing with Media Write Error.
Missing Drive Path
Drives in PEND Status

All of these have one thing in common: If you did not configure persistent binding properly, it would eventually happen.

Without persistent binding, these problems happen when you power cycle the tape library, san switch or reboot the NetBackup host. You won't see the problem immediately until NetBackup tries to use the robot or drive and finds that the device path has changed since it was last used.

Configure persistent binding on the media server(s) that connect to the tape library.
Please refer to your OS and HBA documentation for details.

nbuno's picture

ok thanks..cool..so does SSO is ok with persistent binding ?

RLeon's picture

Yes.

Please refer to this for more details:
  http://www.symantec.com/business/support/index?pag...

Although it is quite old, everything in it is still valid.

As Marianne pointed out, this is not a NetBackup issue; not directly.
But you need persistent binding configured or you will see problems in NetBackup.

nbuno's picture

any quick reference how to do persistent binding on an AIX master/media server ?

RLeon's picture

Apparently this does not apply to AIX:
http://www.symantec.com/business/support/index?pag...

But please check with your Storage/SAN/HBA guys and documentations.

For your other non-AIX media servers sharing the tape library via SSO, persistent binding should still be applied.

Marianne's picture

That's right - AIX does persistent binding by default.

Are ALL of your media servers running AIX? 
As I said above - you need to start troubleshooting at OS level.
On AIX, ensure syslogd is enabled so that device-related errors can be logged to /var/adm/messages.
Add VERBOSE entry to /usr/openv/volmgr/vm.conf on ALL media servers and restart NBU.
With syslogd running and Media Manager processes running in VERBOSE mode, you should be able to see device errors in messages files.
Also check errpt on AIX for possible HBA errors.

Ensure hba's on all your media servers have up-to-date firmware and drivers.

Check switch logs for errors.

Ensure tape drives have up-to-date firmware.

Check with your tape vendor for recommended configuration with AIX.

Check that the correct tape driver is used.

See TN regarding AIX syslogd: http://www.symantec.com/docs/TECH16310

 

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

SOLUTION