08-15-2014 06:46 AM
Hi,
I am having this error:
"EMM status: No media is available
unable to allocate new media for backup, storage unit has none available(96"
The current status of media is AVAILABLE.
Please help.
Solved! Go to Solution.
08-15-2014 07:27 AM
Check :
Density of media matches Density of drive
Check the media hasn't hit the max mouonts limit (seen in vmquery -a output)
Check the media does not have a 'expiration date', also seen in vmquery -a output
EG
media ID: TAPE01
media type: 1/2" cartridge tape 3 (24) <<< Check density matches drives
barcode: --------
media description: ------
volume pool: mseo (4)
robot type: NONE - Not Robotic (0)
volume group: ---
vault name: ---
vault sent date: ---
vault return date: ---
vault slot: ---
vault session id: ---
vault container id: -
created: Mon Jul 28 18:44:37 2014
assigned: Fri Aug 15 12:18:53 2014
last mounted: Fri Aug 15 12:35:09 2014
first mount: Mon Jul 28 18:52:39 2014
expiration date: --- <<<< Check this
number of mounts: 30
max mounts allowed: --- <<< Check this
status: 0x0
08-15-2014 07:27 AM
Check :
Density of media matches Density of drive
Check the media hasn't hit the max mouonts limit (seen in vmquery -a output)
Check the media does not have a 'expiration date', also seen in vmquery -a output
EG
media ID: TAPE01
media type: 1/2" cartridge tape 3 (24) <<< Check density matches drives
barcode: --------
media description: ------
volume pool: mseo (4)
robot type: NONE - Not Robotic (0)
volume group: ---
vault name: ---
vault sent date: ---
vault return date: ---
vault slot: ---
vault session id: ---
vault container id: -
created: Mon Jul 28 18:44:37 2014
assigned: Fri Aug 15 12:18:53 2014
last mounted: Fri Aug 15 12:35:09 2014
first mount: Mon Jul 28 18:52:39 2014
expiration date: --- <<<< Check this
number of mounts: 30
max mounts allowed: --- <<< Check this
status: 0x0
08-15-2014 07:30 AM
If above doesn't give an answer, try this:
http://www.symantec.com/business/support/index?page=answers&type=wizard&wizardid=NBU090&wizardstepid=1A&question_box=status+code+96
08-15-2014 08:10 AM
And check that the media is in the correct pool (or the scratch pool)
Or that its assigned to another host (media server) and not the one trying to do the backup.
08-15-2014 09:09 AM
The Status 96 wizard in Martin's post should help you to find the reason for status 96.
If you are still battling, please show us output of one of the AVAILABLE tapes:
nbbemmcmd -listmedia -mediad <media-id>
as well as STU config specified in the policy that failed with status 96:
bpstulist -label <STU-name> -U
and policy config:
bppllist <policy-name> -U
All commands are in ...\netbackup\bin\admincmd.
08-19-2014 03:17 AM
Hi,
Here is the output for nbemmcmd -listmedia -mediad <media-id>
NBEMMCMD, Version: 7.5
===================================================================
Media GUID: 41336af3-52b1-41bd-94ac-a79e29043f72
Media ID: A00001
Partner: -
Media Type: DLT
Volume Group: 000_00000_TLD
Application: Netbackup
Media Flags: 1
Description: Added by Media Manager
Barcode: --------
Partner Barcode: --------
Last Write Host: NONE
Created: 06/04/2014 03:42
Time assigned: -
First Mount: -
Last Mount: -
Volume Expiration: -
Date Expiration: -
Last Written: -
Last Read: -
Robot Type: TLD
Robot Control Host: backup-svr-pr
Robot Number: 0
Slot: 2
Side/Face: -
Cleanings Remaining: -
Number of Mounts: 0
Maximum Mounts Allowed: 0
Media Status: ACTIVE
Kilobytes: 0
Images: 0
Valid Images: 0
Retention Period: -
Number of Restores: 0
Optical Header Size Bytes: 0
Optical Sector Size Bytes: 0
Optical Partition Size Bytes: 0
Adamm Guid: 00000000-0000-0000-0000-00000000000
Rsm Guid: 00000000-0000-0000-0000-00000000000
Origin Host: NONE
Master Host: -
Server Group: -
Upgrade Conflicts Flag:
Pool Number: 4
Volume Pool: Test
Previous Pool Name: -
Vault Flags: -
Vault Container: -
08-19-2014 03:38 AM
We need output of the rest of commands that were requested as well.
nbemmcmd output shows the following:
Media ID: A00001
Media Type: DLT
Barcode: -------- <<<<-----------
You are using non-barcoded media as explained in this discussion:
Can not take backup in Tape (error coder - 98)
So, neither NetBackup, nor the robot knows what kind of media this is and assigns the default of DLT density and A000... media-id when you perform an Inventory.
Media type MUST match the drive and Storage Unit density.
If hcart tape drives and STU, the media must also be hcart.
If hcart2 tape drives and STU, the media must also be hcart2, etc....
PLEASE purchase some barcode labels, or else be prepared to battle with media management from now on....
08-19-2014 05:05 AM
run the available media script in INSTALL_PATH/veritas/netbackup/bin/goodies/ or INSTALL_PATH\Veritas\NetBackup\Bin\goodies
Post the results
08-19-2014 05:41 AM
08-19-2014 05:44 AM
Available media:
media media robot robot robot side/ ret size status
ID type type # slot face level KBytes
----------------------------------------------------------------------------
CatalogBackup pool
A00004 DLT TLD 0 5 - - - AVAILABLE
A00005 DLT TLD 0 6 - - - AVAILABLE
DataStore pool
NetBackup pool
A00006 DLT TLD 0 7 - - - AVAILABLE
A00007 DLT TLD 0 8 - - - AVAILABLE
A00008 DLT TLD 0 9 - - - AVAILABLE
A00009 DLT TLD 0 10 - - - AVAILABLE
A00010 DLT TLD 0 11 - - - AVAILABLE
A00011 DLT TLD 0 12 - - - AVAILABLE
A00012 DLT TLD 0 13 - - - AVAILABLE
A00013 DLT TLD 0 14 - - - AVAILABLE
A00014 DLT TLD 0 15 - - - AVAILABLE
A00015 DLT TLD 0 16 - - - AVAILABLE
A00016 DLT TLD 0 17 - - - AVAILABLE
A00017 DLT TLD 0 18 - - - AVAILABLE
A00018 DLT TLD 0 19 - - - AVAILABLE
A00019 DLT TLD 0 20 - - - AVAILABLE
A00020 DLT TLD 0 21 - - - AVAILABLE
A00021 DLT TLD 0 22 - - - AVAILABLE
A00022 DLT TLD 0 23 - - - AVAILABLE
A00023 DLT TLD 0 24 - - - AVAILABLE
A00024 DLT TLD 0 25 - - - AVAILABLE
A00025 DLT TLD 0 26 - - - AVAILABLE
A00026 DLT TLD 0 27 - - - AVAILABLE
A00027 DLT TLD 0 28 - - - AVAILABLE
A00028 DLT TLD 0 29 - - - AVAILABLE
A00029 DLT TLD 0 30 - - - AVAILABLE
None pool
Scratch pool
A00041 DLT TLD 0 42 - - - AVAILABLE
A00042 DLT TLD 0 43 - - - AVAILABLE
A00043 DLT TLD 0 44 - - - AVAILABLE
A00044 DLT TLD 0 45 - - - AVAILABLE
A00045 DLT TLD 0 46 - - - AVAILABLE
A00046 DLT TLD 0 47 - - - AVAILABLE
A00047 DLT TLD 0 48 - - - AVAILABLE
Test pool
A00000 DLT TLD 0 1 - - - AVAILABLE
A00001 DLT TLD 0 2 - - - AVAILABLE
ZESCODATA pool
A00002 DLT TLD 0 3 - - - AVAILABLE
A00003 DLT TLD 0 4 - - - AVAILABLE
A00030 DLT TLD 0 31 - - - AVAILABLE
A00031 DLT TLD 0 32 - - - AVAILABLE
A00032 DLT TLD 0 33 - - - AVAILABLE
A00033 DLT TLD 0 34 - - - AVAILABLE
A00034 DLT TLD 0 35 - - - AVAILABLE
A00035 DLT TLD 0 36 - - - AVAILABLE
A00036 DLT TLD 0 37 - - - AVAILABLE
A00037 DLT TLD 0 38 - - - AVAILABLE
A00038 DLT TLD 0 39 - - - AVAILABLE
A00039 DLT TLD 0 40 - - - AVAILABLE
A00040 DLT TLD 0 41 - - - AVAILABLE
08-19-2014 06:27 AM
I was asking for the output of a Storage unit name:
bpstulist -label 'STU-name' -U
and failing policy config:
bppllist 'policy-name' -U
You seem to have 4 different Storage Units configured for the SAME robot:
backup-svr-pr-qscsi-robot-tld-0
backup-svr-pr-hcart-robot-tld-0
backup-svr-pr-hcart2-robot-tld-0
backup-svr-pr-hcart3-robot-tld-0
The only difference seems to be the density in the different STUs.
Do you really have 4 different drive types in robot 0?
Anyway, the DLT density of the media cannot be used with any of the above STUs.
So, you need to understand that densities/type in NBU must match.
Go check the drive types in the Device configuration.
What is the density/drive type of the tape drives?
hcart drive types need hcart (NOT DLT) media and hcart STU.
hcart2 drive types need hcart2 (NOT DLT) media and hcart2 STU.
Again:
PLEASE purchase barcodes for the tapes in the robot.
As explained in the post that I have linked above: Media management is a nightmare without barcode lables.
08-19-2014 06:28 AM
All your media is DLT and all your drives are HCART. The media is incompatible from NetBackup's point of view.
What type of drives and media do you actually have (not what is defined in NetBackup)?
DLT, SDLT, LTO-1, LTO-2, LTO-3, LTO-4, etc,etc.
08-19-2014 07:32 AM
Hi Marianne,
We have one backup device with four different Storage units.
I am new to Netbackup environment and i was not here when this device was first configured.
Here is the (bpstulist -label ) output from one Storage Unit:
Label: backup-svr-pr-qscsi-robot-tld-0
Storage Unit Type: Media Manager
Host Connection: backup-svr-pr
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 1
Density: qscsi - 1/4 Inch Cartridge
Robot Type/Number: TLD / 0
Max Fragment Size: 1048576 MB
And the (bppllist ) output :
C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist E-cash_backup -U
------------------------------------------------------------
Policy Name: E-cash_backup
Policy Type: MS-Windows
Active: yes
Effective date: 07/08/2014 07:38:35
Backup network drvs: no
Collect TIR info: no
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: backup-svr-pr-qscsi-robot-tld-0
Volume Pool: ZESCODATA
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: Windows-x64 Windows2008 prepaidsvr1-ndl
Include: ALL_LOCAL_DRIVES
Schedule: Full
Type: Full Backup
Frequency: every 1 day
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 9 (infinity)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 18:00:00 --> Monday 05:00:00
Monday 18:00:00 --> Tuesday 05:00:00
Tuesday 18:00:00 --> Wednesday 05:00:00
Wednesday 18:00:00 --> Thursday 05:00:00
Thursday 18:00:00 --> Friday 05:00:00
Friday 18:00:00 --> Saturday 05:00:00
Saturday 18:00:00 --> Sunday 05:00:00
08-19-2014 12:32 PM
Sorry, I am missing something here.
We have one backup device with four different Storage units.
Why?????
What are the drive types in the robot?
The 4 STUs says that you have 4 drives types in the robot.
What do you see in Device config?
From cmd under ...\volmgr\bin :
tpconfig -l
As I have said above:
hcart drive type needs hcart (NOT DLT) media and hcart STU.
hcart2 drive type needs hcart2 (NOT DLT) media and hcart2 STU.
qscsi - 1/4 Inch drive type needs qscsi - 1/4 Inch (NOT DLT) media and qscsi - 1/4 Inch STU.
So, you have DLT media and qscsi - 1/4 Inch Storage Unit.
The densities do not match.
That is why you are getting status 96 error.
PLEASE get barcode labels for the media and ensure that densities match:
drive type, media type, STU type.