Media Erase

[Andy_Dodd]

Product Version: Netbackup 6.5.4

Hi,

I am having a few problems trying to erase some old tapes to reuse them again. When I attempt to erase the media in the active monitor window I get a status code 98. 

In the job details window I receive this from the detailed status: 

10/12/2009 09:49:50 - begin Erase
10/12/2009 09:49:50 - started process bplabel (3508)
10/12/2009 09:49:50 - requesting resource Monthly:EPO091
10/12/2009 09:49:51 - Error nbjm(pid=2604) NBU status: 830, EMM status: No drives are available   
10/12/2009 09:49:53 - end Erase; elapsed time: 00:00:03
error requesting media (tpreq)(98) 

However, all tape drives in the library are empty.

Has any one come across a problem like this before?

Many Thanks

[Andy_Welburn]

have they been used in this environment before?

>> NBU status: 830, EMM status: No drives are available

Indicates, possibly, NB is looking for a 'type' of drive that is not available so:

Are the tapes the same density as the drives? (e.g. HCART, HCART3 etc)

[Andy_Dodd]

Yes the tapes have been used in the environment before.

There has been no change of drives or media. As we only use LTO3 tapes and drives.

Thanks

[Andy_Welburn]

points to either drive down or tape/drive/storage unit mis-configurations:

STATUS CODE 830: "All compatible drive paths are down, but media is available". ...

which references:

STATUS CODE: 800, NetBackup 6.0 jobs are failing with Status 800 (resource request failed). ...

Except the following, which mentions illegal characters in the media_id? Just wondering if the ":" in Monthly:EPO091 is an illegal character??

STATUS CODE: 98, Backups fail with a status 98 "error requesting media (tpreq)". ...


***EDIT***
Or am I reading the media_id incorrectly in your OP, as I was led to believe they were a maximum of 6 characters??
Maybe needs re-labelling?

***EDIT #2***
My bad!!!  Didn't realise it put the pool before the media_id so ignore that last bit.

[shans]

Hi

Please check the following link .

http://seer.entsupport.symantec.com/docs/278533.htm

Also please check whether the Drive and media type remains to be same .

[Andy_Dodd]

Tape Drives are up.

C:\Program Files\VERITAS\Volmgr\bin>tpconfig -d
Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   AMXXX1               hcart3 TLD(0)  DRIVE=1
      nrst2a (AMxxx1)                                                  UP
1   AMXXX2               hcart3 TLD(0)  DRIVE=2
      nrst2a (AMxxx2)                                                  UP

Currently defined robotics are:
  TLD(0)     SCSI coordinates = {5,0,6,0}

EMM Server = amarchive1

Storage Units:

C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpstulist
amarchive1-4mm 2 amarchive1 0 -1 12 2 0 "*NULL*" 0 1 1048576 *NULL* 0 1 0 0 0 0
*NULL* amarchive1
amarchive1-hcart3-robot-tld-0-XXXXX1 3 amarchive1 8 0 20 1 0 "*NULL*" 0 1 104857
6 AMFAS1 0 1 0 0 0 0 *NULL* amarchive1
amarchive1-hcart3-robot-tld-0-XXXXX2 3 amarchive1 8 0 20 1 0 "*NULL*" 0 1 104857
6 AMFAS2 0 1 0 0 0 0 *NULL* amarchive1
amarchive1disk 0 amarchive1 0 -1 -1 1 0 "R:\Netbackup" 1 1 524288 *NULL* 0 1 0 9
8 80 0 amarchive1disk amarchive1

Here is a lot more info about the failed job:

C:\Program Files\VERITAS\NetBackup\bin>vxlogview -X "jobid=6455" -d all
10/12/2009 09:49:50.997 [Debug] NB 51216 mds 143 PID:2472 TID:2772 File ID:111 [jobid=6455] 1 [allocateMedia] INITIATIN
:
10/12/2009 09:49:50.997 [Debug] NB 51216 mds 143 PID:2472 TID:2772 File ID:111 [jobid=6455] 1 [allocateMedia] masterSer
er = amarchive1, client = , jobType = 24, capabilityFlags = 0, fatPipePreference = 0, statusOnly = 0
10/12/2009 09:49:50.997 [Debug] NB 51216 mds 143 PID:2472 TID:2772 File ID:111 [jobid=6455] 1 [allocateMedia] MediaRequ
st_Record: MediaServer = amarchive1, PreferredMediaServer = , MediaId = EPO091, MediaKey = 0, AssignedTime = 0, DriveNa
e = , DrivePath = , PoolName = Monthly, Density = 20, RequiredNdmpTapeServer = , PreferredNdmpTapeServer = , MediaType
 2, MediaSubType = 0
10/12/2009 09:49:51.044 [Diagnostic] NB 51216 nbrb 118 PID:3160 TID:3304 File ID:118 [jobid=6455] 1 V-118-108 [ResBroke
_i::failOne] failing resource request ID {E96B309F-7C4C-432B-9CEE-B3314DF4EA30}, status 2005001
10/12/2009 09:49:51.044 [Debug] NB 51216 mds 143 PID:2472 TID:2772 File ID:111 [jobid=6455] 1 [allocateMedia] EXIT INFO

10/12/2009 09:49:51.044 [Debug] NB 51216 mds 143 PID:2472 TID:2772 File ID:111 [jobid=6455] 1 [allocateMedia] EXIT STAT
S = 2005001 (EMM_ERROR_DriveUnavailable, No drives are available)

10/12/2009 09:49:51.154 [Application] NB 51216 nbjm 117 PID:2604 TID:2736 File ID:117 [jobid=6455 parentid=0] [Error] V
117-131  NBU status: 830, EMM status: No drives are available

10/12/2009 09:49:53.435 [Diagnostic] NB 51216 nbjm 117 PID:2604 TID:2728 File ID:117 [jobid=6455 parentid=0] 1 V-117-23
 [MediaOpJob::terminateJob] terminated job, jobid=6455, status=830

C:\Program Files\VERITAS\NetBackup\bin>

 

[Andy_Dodd]

I have been looking at a few of the other jobs and the ":" in question isnt being displayed in them, these are just normal backup jobs.

However, if you look at the unifed log from the job ID the ":" doesn't appear.

[shans]

Are you able to perform Backup & Rstore operation with the same Tape drive ?

[Andy_Welburn]

this was "My bad" - didn't realised the detailed status for the erase was showing volume_pool:media_id so the ":" was a bit of a red-herring, sorry.

[Andy_Welburn]

e.g. vmquery, nbemmcmd or similar?

[Andy_Dodd]

I am able to perform back up and restores with no problems, just erasing tapes is causing problems.

Thanks

[Andy_Dodd]

Ill get this info now.

Thanks

[Andy_Dodd]

C:\Program Files\VERITAS\Volmgr\bin>vmquery -m EPO091
================================================================================
media ID:              EPO091
media type:            1/2" cartridge tape 3 (24)
barcode:               EPO091L3
media description:     Monthly Tapes
volume pool:           Monthly (5)
robot type:            TLD - Tape Library DLT (8)
robot number:          0
robot slot:            24
robot control host:    amarchive1
volume group:          000_00000_TLD
vault name:            ---
vault sent date:       ---
vault return date:     ---
vault slot:            ---
vault session id:      ---
vault container id:    -
created:               03/03/2009 10:16:57
assigned:              03/03/2009 11:59:35
last mounted:          10/12/2009 10:01:33
first mount:           03/03/2009 13:14:40
expiration date:       ---
number of mounts:      3
max mounts allowed:    ---
status:                0x0
================================================================================

However, the erase problem is happening with every tape i have tried.

Thanks

[Andy_Dodd]

C:\Program Files\VERITAS\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid epo091
NBEMMCMD, Version:6.5.4
====================================================================
Media GUID:                     bc552a61-be9d-4530-aea2-015582eb50a8
Media ID:                       EPO091
Partner:                        -
Media Type:                     HCART3
Volume Group:                   000_00000_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    Monthly Tapes
Barcode:                        EPO091L3
Partner Barcode:                --------
Last Write Host:                amarchive1
Created:                        03/03/2009 10:16
Time Assigned:                  03/03/2009 11:59
First Mount:                    03/03/2009 13:14
Last Mount:                     12/10/2009 10:01
Volume Expiration:              -
Data Expiration:                12/17/2009 10:01
Last Written:                   -
Last Read:                      -
Robot Type:                     TLD
Robot Control Host:             amarchive1
Robot Number:                   0
Slot:                           24
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               3
Maximum Mounts Allowed:         0
Media Status:                   IMPORTED
Kilobytes:                      0
Images:                         2
Valid Images:                   0
Retention Period:               6
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             0
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    amarchive1
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    5
Volume Pool:                    Monthly
Previous Pool Name:             -
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
====================================================================
Command completed successfully.

C:\Program Files\VERITAS\NetBackup\bin\admincmd>

[Andy_Welburn · Accepted solution]

Appears to still have images on until the 17th, correct density. Notice it is imported, but that shouldn't make any difference as far as I'm aware.

Only other thing, but again not sure if this will have any bearing on the issue, is that the drives are attached to a filer - I know in the 5.x days we used to have issues labelling tapes that were attached to ndmp hosts, they failed but not sure what the error was & we had to ensure that we only used media manager type drives for labelling. I could try here but all our ndmp attached drives are in use at the mo & it may not prove anything anyway.

Have you managed to erase before? If so, any changes since?

Do you need to erase? We just label new & let the old tapes recycle naturally or force early expiration of older tapes when we used to run short.

Other than that I'm out of ideas at the moment.....& grasping at straws!

[Andy_Dodd]

I have never tried to erase tapes before. We just have so many tape that we have used once i am looking to wipe them and start again.

I was thinking expirating the media and then relabeling the tapes. However, I would like to erase the tapes if possible

Thank you for all your help so far.

Andy

[Andy_Welburn]

One of our ndmp attached drives became free, so I downed all the other drives/paths (media manager ones) leaving this as the sole available drive.

Then selected a scratch tape & tried a "Quick Erase". This resulted in the following in the Job Status:

10/12/2009 15:02:46 - awaiting resource Scratch_Pool:300844 Reason: Drives are in use, Media Server: xxxxxxxxx,
     Robot Number: 1, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A

[[ Altho' they just queued, no errors, which would make sense - we do have media manager drives, whereas you've only got ndmp attached ones. ]]

Then, as soon as I upped the media manager drives/paths, the erase started:

10/12/2009 15:07:52 - granted resource 300844
10/12/2009 15:07:52 - granted resource Drive_4
10/12/2009 15:07:56 - mounting 300844
10/12/2009 15:08:46 - mounted; mount time: 00:00:50

So is tape labelling/erasing not possible on ndmp-attached drives/paths? One for Symantec to comment on methinks? (or maybe someone with a little more technical know-how than me anyway!)

***EDIT***
Did find this which may (or may not) be relevant:

GENERAL ERROR: Imports of a NDMP Backup job to a NDMP Drive only attached to a NDMP Filer fails with...

***EDIT #2***
Altho' that being said, checked our settings for this: DISALLOW_NONNDMP_ON_NDMP_DRIVE="no" (does that mean non-ndmp is allowed on ndmp drive!?) so maybe it's not relevant.

[Marianne]

You will need to expire images before you will will be able to erase/label the tape.
If you are 100% sure you won't need the data on tape, run bpexpdate -m EPO091 -d 0

[Andy_Dodd]

That has made no difference.

[Andy_Dodd]

I have tired that link about the status code 800, as i believe it is some thing to do with NDMP directly attached drives.

SOLUTION/WORKAROUND:
 

Change the NetBackup setting to allow non-ndmp operations on NDMP Tape Drives.
 

nbemmcmd -changesetting -disallow_nonndmp_on_ndmp_drive 0 -machinename <NDMPAgentMediaServerName>

Now in the Netbackup Admin GUI i am getting a new error when trying to erase / relabel a tape.
 
"This operation is not supported when assigned media are selected"