Forum Discussion

NBFREAK's avatar
NBFREAK
Level 4
15 years ago

media manager - system error occurred(174)

Hi Folks,

when im trying to run the catalog backup in unix server, it is failing with the error
media manager - system error occurred(174). Could any one please help me after looking at the below logs?

2/3/2009 16:17:25 - begin Catalog Backup
12/3/2009 16:17:25 - mounting 012345
12/3/2009 16:17:25 - started process bptm (573)
12/3/2009 16:17:26 - Error bptm(pid=573) media id 012345 is in media manager database, cannot be used for NB database backup or restore
12/3/2009 16:17:26 - Error bpbackupdb(pid=571) load of media id 012345 failed, media manager - system error occurred
12/3/2009 16:17:26 - end Catalog Backup; elapsed time: 00:00:01
media manager - system error occurred(174)
12/3/2009 16:17:26 - Error bpbackupdb(pid=571) NB database backup to media id 012345 FAILED
 
 
If I try to give any other media id, in nbu catalog configuration, it gives below error.
 
saving properties returned error number : 97
requested media id is in use, cannot process request.

Note : these medias are used before in Data protector. now im trying to use in veritas netbackup.
Server os : unix , we are using java console.

Unable to lable the media as it is failing with 93 error code(media manager found wrong tape in the drive).

 Please help me how can i fix ?

Regards all
7.1.x and Earlier
Backup and Recovery
NetBackup
Tip-How to
  • Marianne's avatar
    Marianne
    15 years ago
    The media got frozen on 10/30/2009, but according to vmquery the media was added today?
    Did you by any chance did a manual deassign and then deleted and re-added the tape to Media Manager?
    This should never be done - as you can see: although you managed to get rid of the assigned status in volDB, the media is still frozen in mediaDB. This causes major database inconcistencies.
    Unfreezing it should clear the status and delete the entry from mediaDB.
    bpmedia -unfreeze -m 012345 -h xxxxxxxx

    Re-label the tape via the GUI - remove the tick to verify label or use '-o' with bplabel.

3 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    15 years ago
    Please post output of the following:
    vmquery -m 012345
    bpmedialist -m 012345

    Which version of NBU?
  • NBFREAK's avatar
    NBFREAK
    Level 4
    15 years ago

    Hi These are the details as requested.

    XXXXXXX:/.root#->/usr/openv/netbackup/bin/admincmd/bpmedialist -m 012345

    Server Host = xxxxxxxx

    id rl images allocated last updated density kbytes restores

    vimages expiration last read <------- STATUS ------->

    --------------------------------------------------------------------------------

    012345 10 0 10/30/2009 21:34 N/A hcart 0 0

    0 N/A N/A FROZEN

    Some how the same media show as below when i run available media command.
     

    012345 HCART TLD 0 201 - - - AVAILABLE

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    ================================================================================

    media ID: 012345

    media type: 1/2" cartridge tape (6)

    barcode: 012345

    media description: ---

    volume pool: NetBackup (1)

    robot type: TLD - Tape Library DLT

    robot number: 0

    robot slot: 201

    robot control host: XXXXXXX

    volume group: 00_000_TLD

    vault name: ---

    vault sent date: ---

    vault return date: ---

    vault slot: ---

    vault session id: ---

    vault container id: -

    created: Thu Dec 3 16:00:14 2009

    assigned: ---

    last mounted: Thu Dec 3 17:48:17 2009

    first mount: Thu Dec 3 17:48:17 2009

    expiration date: ---

    number of mounts: 1

    max mounts allowed: ---


    XXXXXXX:/usr/openv/netbackup/bin#->/usr/openv/volmgr/bin/vmquery -m 012345

    ================================================================================

    ITS NBU 5.1 MP4 - Master server is unix.

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago
    The media got frozen on 10/30/2009, but according to vmquery the media was added today?
    Did you by any chance did a manual deassign and then deleted and re-added the tape to Media Manager?
    This should never be done - as you can see: although you managed to get rid of the assigned status in volDB, the media is still frozen in mediaDB. This causes major database inconcistencies.
    Unfreezing it should clear the status and delete the entry from mediaDB.
    bpmedia -unfreeze -m 012345 -h xxxxxxxx

    Re-label the tape via the GUI - remove the tick to verify label or use '-o' with bplabel.