cancel
Showing results for 
Search instead for 
Did you mean: 

NetBackup Media Import - Operator Action Required

SteveJD
Level 3

Hi... firstly, I'm running NetBackup v6.0 MP4, which is pretty old.

I built my server specifically to duplicate a load of legacy backups onto newer LTO6 tapes, and that process worked perfectly well. That piece of work was completed 5 years ago.

Using the exactly same server and the duplicate tapes, I'm now attempting to perform restores. However this hasn't started as easily as I thought it would.

I can see the required tapes listed in the Catalog, however the problem starts when I select the associated images to Import.

I right click an image, select Import, I enter the tape ID, the tape loads into a drive via the robot, I see a message on the robot display saying Reading... then after a couple of seconds it stops just sits there saying Ready.

The acitivty log shows the process starting, access is granted to the tape resource, then access is granted to the LTO drive and the tape loads.

I have seen the following error: 1620 error requesting media: TpErrno=Robot operation failed.

A pending request has been generated for this resource request. Operator action may be required.

Pending Action: Tape is unmountable

Media ID: DA0026

Barcode: DA0026

Access Mode: Read

Volume Group: 000_00000_TLD

I have successfully completed all tests against the robot, that's definitely working properly.

This has been driving me mad for a week, hopefully someone can help.

Thanks, Steve

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@SteveJD 

I am still battling to put puzzle pieces together. 

As Nicolai said - if the images have not expired, there is no need to import tapes. 

What does this state mean? 

When attempting a restore I hoped the images would be available, however nothing appeared.... 

Are you saying that you could locate files and folders in the Backup, Archive, GUI? 
Or not? 
I have no idea what 'nothing appeared' means. 

What I do see from your robtest output is that a mount and unmount worked from the robot side, but it seems that the OS device path never recognized the tape mount: 

"No media in drive {4,0,2,0}" 

The 2nd-last number is the scsi target if memory serves me right. 

If we look at 's d' output, we see that scsi id for drive 1 is 3, and scsi id for drive 2 is 4. 

So, it seems to me if device paths at OS-level has changed and NBU device config is now incorrect. 
This means that the tape library will mount the tape in a drive, but the OS device never sees and recognize the mount on the device path. 

To fix this, delete the currently configured tape drives (no need to delete the robot as functionality seems to be okay), run the Device Config Wizard and allow the wizard to restart services. 
(No need to re-config storage units, so you can skip that step)

Let us know how that goes. 

View solution in original post

7 REPLIES 7

Nicolai
Moderator
Moderator
Partner    VIP   

This sound like a device issue.

Can you share message or syslog or other relevant information  from the server and attach as a text file to a post ? This is to help identifying the problem.

Just a couple of idea;

Are you sure the tape drive is able to read the tape mounted. LTO6 can read two prior generations.

Are you sure the position in the robot, match Netbackup configuration, e.g does the robot mount the tape at index 1 when Netbackup thing it will be mounted on index 2 ?

Look for LTO sense key code, maybe there is a good reason for the tape being unmountable  - https://en.wikipedia.org/wiki/Key_Code_Qualifier

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@SteveJD 

This message is IMHO coming from the robot: 

Tape is unmountable

Please help us to help you - 

Aplogies for my lack of understanding, but I am a bit confused by your post - it seems that you have already duplicated tapes to LTO6, but then you say that you want to import images. 
Have the images that were duplicated to LTO6 expired? And now need to be imported again? 

You also say that you can see Images in the Catalog - that means that images have not expired.
Why then are you trying to import? 

To try and troubleshoot the 'mount' issue, please tell us more about devices and media: 

What tape drives are you using (Make/model) ?
Which media type is DA0026 ? If LTO6, does it have 'L6' at the end of the barcode on the tape? 

How are the tape drives and media configured in NBU - which density (hcart#) are the tape drives in NBU and which density is media (hcart#) ? 

Have you tried robtest to see if tape can be loaded in the drive outside of NBU? 
See this TN for robtest usage: https://www.veritas.com/support/en_US/article.100022873

You can try commands such as : 
s d            ### show contents of drives
s s            ###  show contents of slots - make a note of slot number for DA0026
m s# d1    ### move tape in slot # to drive 1
(wait for mount to take place) 
s d            ### show contents of drives to show media in drive
unload d1   ### eject tape from drive
m d1 s#    ###  move tape ejected from drive 1 to it's original slot #

Please let us know outcome of above testing (please copy the text output from the commands). 

For device-level troubleshooting, please locate vm.conf on the master/media server (<install-path>\Veritas\volmgr ).
Add this line:
VERBOSE
Save the file and restart NBU Device Management service. 
Please also check that bptm folder exists under <install-path>\Veritas\NetBackup\logs. If not, create the folder before attempting any imports or restores again.
bptm will log NBU actions. 

Device-level activity and errors will now be logged in OS Event Viewer System and Application logs. 

The tapes I'm using are LTO6 and they were duplicated from older tapes 5 years ago. During the duplication process I believe the tapes were set to never expire. If I run a Verify on a tape such as DA0026, currently loaded in the TLD, I can see images.

When attempting a restore I hoped the images would be available, however nothing appeared so I thought perhaps they need reimporting? When I right click an image to import, I end up cancelling the job and I see the error described.

The TLD is a Tandberg Exabyte Magnum 224 with HP Ultrium-6 drives, these are set to HCart3 in the config. The tapes have L6 on the barcode.

The system has been switched off for some time and I expected it to work when needed. I must admit that I've forgotten certain aspects about the operation, but it has previously worked fine when restoring files and without issue, so it's a bit weird that it's not playing ball.

I'll run those commands soon as I can and post them.... thanks.

 

 

Screenshot attached from Robtest.

 

 

Nicolai
Moderator
Moderator
Partner    VIP   

Tapes already imported does not need to be imported again unless data has been expired.

You can verify if a tape has data on it by running the command bpimmedia  :

# bpimmedia -L -mediaid CB7514 

Taken from : https://www.veritas.com/support/en_US/doc/123533878-127136857-0/v123538836-127136857 

If images are listed, try to run bpverify -id {barcode name of media}. This should demonstrate Netbackup can get access to the tape drives.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@SteveJD 

I am still battling to put puzzle pieces together. 

As Nicolai said - if the images have not expired, there is no need to import tapes. 

What does this state mean? 

When attempting a restore I hoped the images would be available, however nothing appeared.... 

Are you saying that you could locate files and folders in the Backup, Archive, GUI? 
Or not? 
I have no idea what 'nothing appeared' means. 

What I do see from your robtest output is that a mount and unmount worked from the robot side, but it seems that the OS device path never recognized the tape mount: 

"No media in drive {4,0,2,0}" 

The 2nd-last number is the scsi target if memory serves me right. 

If we look at 's d' output, we see that scsi id for drive 1 is 3, and scsi id for drive 2 is 4. 

So, it seems to me if device paths at OS-level has changed and NBU device config is now incorrect. 
This means that the tape library will mount the tape in a drive, but the OS device never sees and recognize the mount on the device path. 

To fix this, delete the currently configured tape drives (no need to delete the robot as functionality seems to be okay), run the Device Config Wizard and allow the wizard to restart services. 
(No need to re-config storage units, so you can skip that step)

Let us know how that goes. 

I deleted the tape drives and ran the wizard to add them back. I'm now able to initiate an Import and the tape is locating the required session. I'm surprised by this because technically nothing had changed and it was working perfectly in the past.

When the Import process completes I should be able to open the Backup/Restore GUI and see a session I can use to restore data.

Thank you for your guidance.