Environment:
NetBackup 7.1.0.4
RHEL6 master and media server
Overland Storage FC Neo 8000e tape library (tld)
LTO5 tape drives
Our new tape library has frozen a couple of times and needed to be rebooted.
When it comes back online, the media server assigns the robot a new device name
which
Forgot to mention: The media server is an HP Proliant DL380p Gen8 with an HP
QLogic Fibre Channel HBA.
On Mar 27, 2013, at 12:07 PM, Neil Conner n...@mbari.org wrote:
Environment:
NetBackup 7.1.0.4
RHEL6 master and media server
Overland Storage FC Neo 8000e tape library (tld)
LTO5 tape
-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Neil Conner
Sent: Wednesday, March 27, 2013 3:12 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Fiber channel robot device numbers auto-incrementing
Forgot to mention: The media
Hi Neil,
This sounds like persistent binding is not set on the HBA and causes the OS
to keep recognizing it as new and adding it again. I'm not too familiar
with how that is setup on Linux, but it should be in your HBA config file.
Good luck!
Rusty
On Wed, Mar 27, 2013 at 2:07 PM, Neil Conner
Take all look on your master and media servers to see if you have the entry
AUTO_PATH_CORRECTION=YES in the /usr/openv/volmgr/vm.conf file. This will
tell NetBackup to rescan the system devices and update the NetBackup device
configuration with the new/changed node information. The rescan is
