Media status dbbackup NBU 7.0.1

that means database backup; a Catalog tape

DBBACKUP is status for Offline Catalog Backup tapes.
Since Offline Catalog Backup is obsoluted from NetBackup 7.0, this was caused by some timing issue. I guess cleanup process was in progress when you check status.
Check later again, or run "bpexpdate -deassignempty -force" and check again.

Hi,

These are not catalog backup tapes...these all are daily NDMP backup media tapes...

any idea why these tapes are showing DBBACKUP as a available status???? I mean in what condition they move to DBBACKUP status?

Please share the following output for one of these tapes:

nbemmcmd -listmedia -mediaid <media-id>

There used to be a bug in V5 that caused this, maybe it has crept back in:

http://www.symantec.com/docs/TECH6059

Hi Marianne,

:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid EOF227
NBEMMCMD, Version:7.0.1
====================================================================
Media GUID:                     ef7373db-2565-4660-bba1-fef0eb379a04
Media ID:                       EOF227
Partner:                        -
Media Type:                     HCART
Volume Group:                   000_00000_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    Added by Media Manager
Barcode:                        EOF227L4
Partner Barcode:                --------
Last Write Host:                NTBOMFS001
Created:                        06/26/2009 19:06
Time Assigned:                  11/28/2011 23:00
First Mount:                    06/28/2009 19:41
Last Mount:                     12/23/2011 18:21
Volume Expiration:              -
Data Expiration:                12/27/2011 23:00
Last Written:                   11/30/2011 23:00
Last Read:                      12/23/2011 18:25
Robot Type:                     TLD
Robot Control Host:             inmumvbs01
Robot Number:                   0
Slot:                           7
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               20
Maximum Mounts Allowed:         0
Media Status:                   FULL
Kilobytes:                      917972772
Images:                         9
Valid Images:                   0
Retention Period:               0
Number of Restores:             2
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             8995382
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    inmumvbs01
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    8
Volume Pool:                    Daily
Previous Pool Name:             Scratch
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -

Edit...

above output was showing right the media status is full...then why this script is showing BDBACKUP?

Interesting result ...

Media Data Expiration has passed, no valid images, status is FULL and it has a time assigned

Something is amis with this tape, not just the DBBACKUP part, as that tape should have expired unless it was Frozen (which it is not showing as being) or had a pending action against it.

Just check Device Monitor to make sure there are no pending mount requests that have confused this tape

Otherwise you may need to just try a pbexpdate against it to clean it up (unless you have other tapes with data expiration dates that have passed by more than one day in which case you need to find out why)

Hi Mark,

there are 20 more as such tapes......no pending mounts in activity monitor....

Images on tapes are already expired from the catalog database...even the image clean job runs fine manually and automatically.but tapes are not getting expired automatically with status DBBACKUP ...bpexpdate works fine...after expiring single tape, again I ran the script it is showing available status.....

Ok - it should happen automatically but try:

bpexpdate -deassignempty -force

This should deassign any empty (expired) tapes

NetBackup runs the command (without the force) every day but these may have slipped the net.

Try this and if they clear down then just keep an eye on things of a while - it may have just been a glitch