Forum Discussion

sksujeet's avatar
sksujeet
Level 6
14 years ago

NEtbackup manual tape eject

I am fairly new to netbackup and need your help.

 

we have netbackup 6.5 installed. 1 master server running on solaris and 3 media server on windows. I only have access to windows media server.
I manually ejected the 40 tapes from the library by selecting all the 40 and running eject.

Is there any way to get a report about the media ids of these 40 tapes.

  • I just had a look at the information kept in EMM database for media - there is no 'eject' date... just 'date vaulted':

    # nbemmcmd -listmedia -mediaid A00001
    NBEMMCMD, Version:7.0.1
    ====================================================================
    Media GUID:                     2b551fc8-fe5d-11df-8000-91a5c0c6ba38
    Media ID:                       A00001
    Partner:                        -
    Media Type:                     HCART2
    Volume Group:                   000_00001_TLD
    Application:                    Netbackup
    Media Flags:                    1
    Description:                    Added by Media Manager
    Barcode:                        --------
    Partner Barcode:                --------
    Last Write Host:                NONE
    Created:                        12/02/2010 19:43
    Time Assigned:                  -
    First Mount:                    -
    Last Mount:                     -
    Volume Expiration:              -
    Data Expiration:                -
    Last Written:                   -
    Last Read:                      -
    Robot Type:                     TLD
    Robot Control Host:             sdb-nbu-mas
    Robot Number:                   1
    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
    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:                    1
    Volume Pool:                    NetBackup
    Previous Pool Name:             -
    Vault Flags:                    -
    Vault Container:                -
    Vault Name:                     -
    Vault Slot:                     -
    Session ID:                     -
    Date Vaulted:                   -
    Return Date:                    -
    ====================================================================

     

    The only place where the eject might have been logged is Media Manager logs.

    Now in your case, I'm not sure where it should be - master or media. Since your media server is robot control host, you might be lucky enough that this where the logs will be written.

    These logs do not exist by default - a 'debug' directory needs to be created under Veritas\volmgr. Under debug, the following folders must be created: daemon and reqlib. These log directories will start logging when VERBOSE is added to vm.conf (in volmgr folder) and NBU is restarted on the media server.

    If I remember correctly, media operations will be logged in daemon log.

    I hope for your sake that these logs have been created in the past and that you will find your eject info...

  • I just had a look at the information kept in EMM database for media - there is no 'eject' date... just 'date vaulted':

    # nbemmcmd -listmedia -mediaid A00001
    NBEMMCMD, Version:7.0.1
    ====================================================================
    Media GUID:                     2b551fc8-fe5d-11df-8000-91a5c0c6ba38
    Media ID:                       A00001
    Partner:                        -
    Media Type:                     HCART2
    Volume Group:                   000_00001_TLD
    Application:                    Netbackup
    Media Flags:                    1
    Description:                    Added by Media Manager
    Barcode:                        --------
    Partner Barcode:                --------
    Last Write Host:                NONE
    Created:                        12/02/2010 19:43
    Time Assigned:                  -
    First Mount:                    -
    Last Mount:                     -
    Volume Expiration:              -
    Data Expiration:                -
    Last Written:                   -
    Last Read:                      -
    Robot Type:                     TLD
    Robot Control Host:             sdb-nbu-mas
    Robot Number:                   1
    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
    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:                    1
    Volume Pool:                    NetBackup
    Previous Pool Name:             -
    Vault Flags:                    -
    Vault Container:                -
    Vault Name:                     -
    Vault Slot:                     -
    Session ID:                     -
    Date Vaulted:                   -
    Return Date:                    -
    ====================================================================

     

    The only place where the eject might have been logged is Media Manager logs.

    Now in your case, I'm not sure where it should be - master or media. Since your media server is robot control host, you might be lucky enough that this where the logs will be written.

    These logs do not exist by default - a 'debug' directory needs to be created under Veritas\volmgr. Under debug, the following folders must be created: daemon and reqlib. These log directories will start logging when VERBOSE is added to vm.conf (in volmgr folder) and NBU is restarted on the media server.

    If I remember correctly, media operations will be logged in daemon log.

    I hope for your sake that these logs have been created in the past and that you will find your eject info...

  • There were various suggestions, but unfortunately no satisfactory resolution. Maybe there was something there that could assist:

    https://www-secure.symantec.com/connect/forums/log-injected-tapes

    If not, maybe someone's found something in the meantime?

  • Hey Andy, no luck.

    The tape library is connected to windows server (media server). I would like to know what tapes got ejected manually. We do eject using policy and that i can track in the vault report but my collegue ejected 40 tapes manually and i have to find those tapes. Is there any how i can get those tape labels.

  • I know I couldn't when I was looking for ChangeResidence or whatever in the unified logs per the other post - you'd think there'd be something somewhere but maybe not...

    If this is going to be a regular thing, maybe worth keeping a regular log of the robots contents (try vmcheckxxx) until someone comes up with a better solution?

  • This may not help with past event but what I do when ejecting volumes is to move them into a Volume Group that describes their location.  Makes it easy to locate them later.