cancel
Showing results for 
Search instead for 
Did you mean: 

HP MSL4048, Netbackup 7.5, replace tape drive

amdcler
Level 4

Hello!
We use the library HP MSL4048 + two tape drives HP Ultirum LTO5 Fiber Optic.
Recently, one of the drives fails, and we decided to replace it with a LTO6
After replacing the drive to define it I ran the wizard Configure Storage Device.
I added a new drive to an existing robot, he appeared in the list of available drives.

- But now stopped working backups, even on the old drive, an error Reason: Robotic library is down on server
- Not working robot inventory, an error robot inventory failed: Unable to open robotic path (201)
- new drive in the Windows Device Manager falls into the category of other devices.
- And the new drive has the status of Shared Drive: No

As now all I fix this? Thanks in advance.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

You will need to confirm that all drives are zoned to all media server and that the vendor tape driver is installed for all tape drives on all media servers.
Confirm that tape drives are visible and usable with 'scan -tape' on all media servers.

Start Device Config wizard again - ensure that robot control host and all media servers are selected.
If SSO licenses and Library Based tape drive licenses are present on media servers (in addition to Enterprise Server or Enterprise Client license), drives will be configured as Shared. 

View solution in original post

12 REPLIES 12

amdcler
Level 4

In this topic, the decision was the creation of the device file.
I have a similar error

bpps fails with the following error:

\Program Files\Veritas\NetBackup\bin>bpps
bpps - Error: Could not get process statistics.
       The system cannot find the file specified.
 
What is this file and how to create it?

Marianne
Level 6
Partner    VIP    Accredited Certified

Robotic library is down on server 

Was the robot door closed after drive replacement? 
An open robot door can cause this. Ensure the robot is fully functional with no errors or 'initializing' messages in the robot display panel.

Next thing to check is if the robot is responding to scsi-commands at OS-level.
If this is W2008 server, open cmd with 'Run as Administrator', cd to \Program Files\Veritas\Volmgr\bin and run:
scan -changer

PS: No idea what you are trying to accomplish with your second comment as far as 'creation of device file' is concerned...

amdcler
Level 4

The output of this command

C:\Program Files\Veritas\Volmgr\bin>scan.exe -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************

 

The robot is functioning correctly, here is a screenshot from a web interface

libr.jpg

inn_kam
Level 6
Partner Accredited

Is your OS detecting the Tape drives? please check?

if not then reboot, then re ran Configure devices

Marianne
Level 6
Partner    VIP    Accredited Certified

No output from scan -changer?

This means that the OS cannot see the robot.

Double-check physical connection, zoning, etc.

Forget about NBU until such time as 'scan' shows output from the robot.

inn_kam
Level 6
Partner Accredited

when running wizard . select properties , and properly label as one tape is LTO 5 and other is LTO 6

amdcler
Level 4

The OS sees the library (see screenshot)

What can be done?

devicemanager.jpg

lib2.jpg

libra3.jpg

 

libra4.jpg

 

amdcler
Level 4

I rebooted the library, and the result scan.exe -changer

 

C:\Program Files\Veritas\Volmgr\bin>scan.exe -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 2; Bus: 0; Target: 24; LUN: 1
Inquiry    : "HP      MSL G3 Series   8.70"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "8.70"
Serial Number: "DEC------"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   DEC-----F"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 3
Number of Slots  : 47
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU10-----"
Drive 2 Serial Number      : "HU12-----"
Drive 3 Serial Number      : "HUJ4-----"
Flags : 0x0
Reason: 0x0

amdcler
Level 4

Drive up after reboot NBU! Backup running on LTO5

But LTO6 drive assign with only one server. Not shared.

How as I share it?

drive.jpg

 

Marianne
Level 6
Partner    VIP    Accredited Certified

You will need to confirm that all drives are zoned to all media server and that the vendor tape driver is installed for all tape drives on all media servers.
Confirm that tape drives are visible and usable with 'scan -tape' on all media servers.

Start Device Config wizard again - ensure that robot control host and all media servers are selected.
If SSO licenses and Library Based tape drive licenses are present on media servers (in addition to Enterprise Server or Enterprise Client license), drives will be configured as Shared. 

amdcler
Level 4

Thank you very much!

After installing the drivers to drive on each server, and re-run the wizard, the drive became SHARED.

I have another question - how to hide the drive, which is disabled?

drive3.jpg

 

Marianne
Level 6
Partner    VIP    Accredited Certified

The NBU picture shows that there are 3 drive slots in the robot but the 1st one is blank/unavailable/etc.

You can see in your device config screenshots that the robot returned (unused element address) for Drive 1 .

Nothing can be done in NBU to change this - you need to fix it at robot level.