01-17-2018 10:40 AM
Since our backup systemwas upgraded to NetBackup 7.7.3 about a month ago, I have not had a successful catalog backup. I get this error: - Error nbjm (pid=7312) NBU status: 96, EMM status: No media is available
unable to allocate new media for backup, storage unit has none available (96)
There is a catalog tape available, I have tried to use several different ones and even created a new one. The ones I'm using are not expired and are the same density as the drive (hcart) and are in the CatalogBackup pool. I have tried re-labelling the tape through the Media option in case the system thought the tape had data from the previous version of NetBackup.
Here's what I have from available_media for the catalog tapes:
C:\Program Files\Veritas\NetBackup\bin\goodies>available_media.cmd | more
media media robot robot robot side/ ret size status
ID type type # slot face level KBytes
----------------------------------------------------------------------------
CatalogBackup pool
CAT002 HCART NONE - - - 5 536060061 ACTIVE
CAT013 HCART NONE - - - 5 631126742 ACTIVE
CAT032 HCART NONE - - - 5 325732335 ACTIVE
CAT001 HCART NONE - - - - - AVAILABLE
CAT003 HCART NONE - - - - - AVAILABLE
CAT005 HCART NONE - - - - - AVAILABLE
CAT006 HCART NONE - - - - - AVAILABLE
CAT007 HCART NONE - - - - - AVAILABLE
CAT008 HCART NONE - - - - - AVAILABLE
CAT009 HCART NONE - - - - - AVAILABLE
CAT010 HCART NONE - - - - - AVAILABLE
CAT011 HCART NONE - - - - - AVAILABLE
CAT012 HCART NONE - - - - - AVAILABLE
CAT014 HCART TLD 0 2 - - - AVAILABLE
CAT033 HCART NONE - - - - - AVAILABLE
Let me know what other info I can provide.
Solved! Go to Solution.
01-18-2018 06:18 AM
So, you have 2 robots : TLD(0) and TLD(1)
Tape is in robot 0.
CAT014 HCART TLD 0 2 - - - AVAILABLE
Catalog policy specifies STU msilbus1-hcart-robot-tld-1
The tape in robot 0 cannot be used by robot 1.
You need to insert one or more AVAILABLE CatalogBackup tape(s) in robot 1.
01-17-2018 04:47 PM
What is the storage unit and volume pool that you have selected in the policy?
Is the density of the storage unit also hcart under robot TLD-0?
If tape - CAT014 is an empty tape can you try to manually right click the tape and select Label (The next popup that appears ensure that you unselect the verify operation). If the label operation is able to load and clean the tape header that would be a good test to verify the tape's availability as well.
01-17-2018 11:02 PM - edited 01-18-2018 01:56 AM
Please show us output of
nbemmcmd -listmedia -mediaid CAT014
*** EDIT ***
Please also give us output of:
bppllist <Policy-name> -U
bpstulist -L
tpconfig -l
Above commands should give us a full picture of all related components that will hopefully tell us where the problem is.
Verbose (level 3) bptm logging will also help to see how media is evaluated.
01-18-2018 01:49 AM
Please also check the density of the tape drives - if tape drives are a other density than HCART Netbackup will not mount CAT0?? because Netbackup think the media is incompatible.
01-18-2018 06:08 AM
Nicolai,
The drive density is hcart.
Amol_Nai,
I had run the label process before, but I went ahead and ran it again against CAT014 and made sure to deselect "Verify...", but I still got the same result.
Marianne,
Here's the info you requested:
C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid CAT014
NBEMMCMD, Version: 7.7.3
====================================================================
Media GUID: c9639693-110b-4eff-ae9d-3e7007b0527e
Media ID: CAT014
Partner: -
Media Type: HCART
Volume Group: 000_00000_TLD
Application: Netbackup
Media Flags: 1
Description: Added by Media Manager
Barcode: CAT014L4
Partner Barcode: --------
Last Write Host: NONE
Created: 01/12/2018 11:39
Time Assigned: -
First Mount: 01/16/2018 16:12
Last Mount: 01/16/2018 16:12
Volume Expiration: 01/16/2019 15:47
Data Expiration: -
Last Written: -
Last Read: -
Robot Type: TLD
Robot Control Host: msilbus1.msil.local
Robot Number: 0
Slot: 2
Side/Face: -
Cleanings Remaining: -
Number of Mounts: 1
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
Last Header Offset: 0
Adamm Guid: 00000000-0000-0000-0000-000000000000
Rsm Guid: 00000000-0000-0000-0000-000000000000
Origin Host: NONE
Master Host: -
Server Group: -
Upgrade Conflicts Flag:
Pool Number: 3
Volume Pool: CatalogBackup
Previous Pool Name: -
Vault Flags: -
Vault Container: -
Vault Name: -
Vault Slot: -
Session ID: -
Date Vaulted: -
Return Date: -
Media on Hold: 0
====================================================================
Command completed successfully.
C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist NBU-Catalog -U
------------------------------------------------------------
Policy Name: NBU-Catalog
Policy Type: NBU-Catalog
Active: yes
Effective date: 03/09/2015 22:10:24
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: 1
Disaster Recovery: 0
Collect BMR info: no
Residence: msilbus1-hcart-robot-tld-1
Volume Pool: CatalogBackup
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
Use Accelerator: no
HW/OS/Client: Windows-x64 Windows2008 msilbus1.msil.local
Include: CATALOG_DRIVEN_BACKUP
Schedule: Full
Type: Full Backup
Frequency: every 7 days
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 1
Retention Level: 0 (1 week)
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
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
Catalog Disaster Recovery Configuration:
Email Address: (none specified)
Disk Path: D:\DR_Recovery
User Name: xxxxxxxx
Pass Word: xxxx
Critical policy: (none specified)
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist -L
Label: msilbus1-hcart-robot-tld-0
Storage Unit Type: Media Manager
Host Connection: msilbus1.msil.local
Number of Drives: 5
On Demand Only: no
Density: hcart (6)
Robot Type/Number: TLD (8) / 0
Max Fragment Size: 1048576
Max MPX/drive: 1
Label: msilbus1-hcart-robot-tld-0-msilnas1
Storage Unit Type: NDMP
Host Connection: msilbus1.msil.local
Number of Drives: 5
On Demand Only: no
Density: hcart (6)
Robot Type/Number: TLD (8) / 0
Max Fragment Size: 1048576
Max MPX/drive: 1
NDMP attach host: msilnas1
Label: msilbus1-hcart-robot-tld-0-msilnas2
Storage Unit Type: NDMP
Host Connection: msilbus1.msil.local
Number of Drives: 4
On Demand Only: no
Density: hcart (6)
Robot Type/Number: TLD (8) / 0
Max Fragment Size: 1048576
Max MPX/drive: 1
NDMP attach host: msilnas2
Label: msilbus1-hcart-robot-tld-1
Storage Unit Type: Media Manager
Host Connection: msilbus1.msil.local
Number of Drives: 1
On Demand Only: no
Density: hcart (6)
Robot Type/Number: TLD (8) / 1
Max Fragment Size: 1048576
Max MPX/drive: 1
Label: msilbus1-hcart-robot-tld-1-msilnas1
Storage Unit Type: NDMP
Host Connection: msilbus1.msil.local
Number of Drives: 1
On Demand Only: no
Density: hcart (6)
Robot Type/Number: TLD (8) / 1
Max Fragment Size: 1048576
Max MPX/drive: 1
NDMP attach host: msilnas1
Label: msilbus1-hcart-robot-tld-1-msilnas2
Storage Unit Type: NDMP
Host Connection: msilbus1.msil.local
Number of Drives: 1
On Demand Only: no
Density: hcart (6)
Robot Type/Number: TLD (8) / 1
Max Fragment Size: 1048576
Max MPX/drive: 1
NDMP attach host: msilnas2
tpconfig -l
Device Robot Drive Robot Drive Device
Type Num Index Type DrNum Status Comment Name Path
robot 0 - TLD - - - - c80t0l1 (msilnas2)
drive - 0 hcart 2 UP - HP.ULTRIUM4-SCSI.000 c64t0l0
drive - 0 hcart 2 UP - HP.ULTRIUM4-SCSI.000 c64t0l0
drive - 0 hcart 2 UP - HP.ULTRIUM4-SCSI.000 {6,0,0,0}
drive - 0 hcart 2 UP - HP.ULTRIUM4-SCSI.000 {5,0,0,0}
drive - 1 hcart 4 UP - HP.ULTRIUM4-SCSI.001 c112t0l0
drive - 1 hcart 4 DOWN - HP.ULTRIUM4-SCSI.001 c112t0l0
drive - 1 hcart 4 UP - HP.ULTRIUM4-SCSI.001 {6,0,2,0}
drive - 1 hcart 4 UP - HP.ULTRIUM4-SCSI.001 {5,0,2,0}
drive - 2 hcart 3 UP - HP.ULTRIUM4-SCSI.002 c96t0l0
drive - 2 hcart 3 DOWN - HP.ULTRIUM4-SCSI.002 c96t0l0
drive - 2 hcart 3 UP - HP.ULTRIUM4-SCSI.002 {6,0,3,0}
drive - 2 hcart 3 UP - HP.ULTRIUM4-SCSI.002 {5,0,3,0}
drive - 3 hcart 1 UP - HP.ULTRIUM4-SCSI.003 {6,0,1,0}
drive - 3 hcart 1 UP - HP.ULTRIUM4-SCSI.003 c80t0l0
drive - 3 hcart 1 DOWN - HP.ULTRIUM4-SCSI.003 c80t0l0
drive - 3 hcart 1 UP - HP.ULTRIUM4-SCSI.003 {5,0,1,0}
robot 1 - TLD - - - - {6,0,5,1}
drive - 4 hcart 2 UP - HP.ULTRIUM4-SCSI.004 {6,0,4,0}
drive - 4 hcart 2 UP - HP.ULTRIUM4-SCSI.004 c128t0l0
drive - 4 hcart 2 UP - HP.ULTRIUM4-SCSI.004 c128t0l0
drive - 4 hcart 2 UP - HP.ULTRIUM4-SCSI.004 {5,0,4,0}
drive - 5 hcart 1 UP - HP.ULTRIUM4-SCSI.005 {6,0,5,0}
drive - 5 hcart 1 UP - HP.ULTRIUM4-SCSI.005 c144t0l0
drive - 5 hcart 1 UP - HP.ULTRIUM4-SCSI.005 c144t0l0
drive - 5 hcart 1 UP - HP.ULTRIUM4-SCSI.005 {5,0,5,0}
01-18-2018 06:18 AM
So, you have 2 robots : TLD(0) and TLD(1)
Tape is in robot 0.
CAT014 HCART TLD 0 2 - - - AVAILABLE
Catalog policy specifies STU msilbus1-hcart-robot-tld-1
The tape in robot 0 cannot be used by robot 1.
You need to insert one or more AVAILABLE CatalogBackup tape(s) in robot 1.
01-18-2018 06:21 AM
I also notice that the tape was mounted 2 days ago.
First Mount: 01/16/2018 16:12
Last Mount: 01/16/2018 16:12
Whas this to relabel it?
Seems you have also added a hardware expiration date for next year:
Volume Expiration: 01/16/2019 15:47
Any reason for that?
NBU default is Never.
01-18-2018 06:34 AM
You're right, it was to relabel it. And I did put in expiration date on it in the hopes that that might fix it.
01-18-2018 06:38 AM
I'll move the tape to the other robot. I don't know if the policy changed but I recall that we had always placed the catalog tape with the NDMP tapes on robot 0.
01-18-2018 06:43 AM
Robot 1 is also attached to your NAS (NDMP) servers as can be seen in STU names:
Label: msilbus1-hcart-robot-tld-1-msilnas1
Label: msilbus1-hcart-robot-tld-1-msilnas2
as well as multiple drive paths in tpconfig output.
01-18-2018 06:48 AM
What if I changed the policy to use robot0?
01-18-2018 06:53 AM
It will work.
01-18-2018 06:57 AM
When I change it to robot 0, I get a this message, "DR file is on the same partition as your catalog and will be unusable in an actual disaster or disk failure(2512)". Of course, I get the same message when I change it back to robot 1. Not sure it matters anyway since both robots are in the same rack.
01-18-2018 07:43 AM
I highly recommend moving the DR file to another location. The DR file is the cookbook in getting the NBU catalog back - each DR file is unique
Either mail it to a gmail / hotmail account or copy it to a network share.
01-18-2018 07:56 AM
I will do that.
I see that it's a separate issue from the NBU-catalog policy. Thanks!