10-29-2014 01:47 PM
Master (Linux, 7.0.1)
Media (Linux, 7.0.1)
Drives are in AVR mode for one media server. Server rebooted, drive reconfigured, but still issue is there.
Able to scan the drives on media server, tpconfig -l, scan -tape are working. Ran tpautoconf -a, but no luck.
Please assist.
[root@mediaserver bin]# ./scan -tape | more
************************************************************
*********************** SDT_TAPE ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/nst3"
Passthru Name: "/dev/sg5"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULTRIUM-TD3 93GM"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD3 "
Product Rev: "93GM"
Serial Number: "F001509031"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD3 F001509034"
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst4"
Passthru Name: "/dev/sg6"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULTRIUM-TD3 93GM"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD3 "
Product Rev: "93GM"
Serial Number: "F001509037"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD3 F001509027"
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst2"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00150900D"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00150902D"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst1"
Passthru Name: "/dev/sg2"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F001509007"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F001509009"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst0"
Passthru Name: "/dev/sg1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F001509001"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F001509006"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
============
[root@mediaserver bin]# ./tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path
robot 4 - TLD - - - - robotichost
drive - 3 hcart3 6 UP - drive-hcart3-004-10 /dev/nst4
drive - 7 hcart2 5 UP - drive-hcart2-004-04 /dev/nst3
drive - 8 hcart2 3 UP - drive-hcart2-004-03 /dev/nst2
drive - 9 hcart2 2 UP - drive-hcart2-004-02 /dev/nst1
drive - 10 hcart2 1 DOWN - drive-hcart2-004-01 /dev/nst0
Solved! Go to Solution.
11-19-2014 11:22 PM
The robot axis problem is why drives are in AVR state - robot control process in NBU will go down when there is a hardware issue with the robot.
No robot daemon/process will leave drives in AVR.
I am just surprised that fixing the robot is taking so long.
More than 3 weeks now?
How are backups done in the meantime?
10-29-2014 02:03 PM
Your tpconfig output shows robot on a different host, right?
AVR in this instance means that media server has lost network/port connectivity to robotichost.
Check that PBX ia running on media server, verify that PBX (port 1556) is open in both directions between media server and robotichost, double-check forward and reverse name lookup between media server and robotichost, that SERVER entries exist on media server and robotichost for one another.
If you feel that all of the above is fine, stop NBU on media server.
Add VERBOSE entry to vm.conf on media server, then start NBU.
Check /var/log/messages for errors if drives still come up in AVR status.
10-29-2014 04:26 PM
Please post output of "scan", "tpconfig -d"and "vmoprcmd" on both this media server and robotic control host.
10-29-2014 04:33 PM
11-05-2014 09:10 PM
A week later and no response? Seems this cannot be too much of an issue...
11-06-2014 08:21 AM
There is an issue with the library, working with the vendor on it.
11-06-2014 10:06 AM
Then there will be a problem on the robot control host as well, right?
Not only on this media server?
11-17-2014 03:38 AM
11-19-2014 12:59 PM
There are two drive faulty which causing the same issue again and again.
And also some robotic axis also found faulty, we are just working on this to get these part replaced.
11-19-2014 11:22 PM
The robot axis problem is why drives are in AVR state - robot control process in NBU will go down when there is a hardware issue with the robot.
No robot daemon/process will leave drives in AVR.
I am just surprised that fixing the robot is taking so long.
More than 3 weeks now?
How are backups done in the meantime?
11-23-2014 05:25 AM
The faulty parts replaced successfully, and configured. Now the drives are up and working fine.
For the time the backup goes to disk.
We are planning to move backup from Library to Data Domain. ( Would you please assist me, with DD usage along with netbackup) How to configure it and how it works.
11-23-2014 07:08 AM
You can download DD config docs with NetBackup from EMC website or ask your DD reseller.
Look for Data_Domain_Boost_Admin_Guide.
And download this planning and best practice white paper:
http://www.emc.com/collateral/software/white-papers/h7296-data-domain-boost-openstorage-wp.pdf
If you have never worked with Data Domain before, best to attend training first.
For anything else about Data Domain with NBU, please start a new discussion.