Forum Discussion

Lotfi_BOUCHERIT's avatar
11 years ago

Netbackup shows: Media is in use

Hello,

Suddenly, I see in the Netbackup console, when i start a backup task, the state is MEDIA IS IN USE and not running at all. I tried to cancel the job, restart the Storage library, restart the server, but remained the same state Media is in Use till sometime later after restart...

I would like to know from where, and what could help diagnosing this issue...

Thanks in advance!

  • Try these:

    1. Run /usr/openv/netbackup/bin/admincmd/nbrbutil -dump | grep <mediaID>
    2. If nbrb still has an open assignment for this tape, you will see quite a few lines of information, but look for the line containing “MdsAllocation
    3. Next to this will be a number so that it looks like this: MdsAllocation allocationKey=4838
    4. This is the assignment that needs to be released using this command: /usr/openv/netbackup/bin/admincmd/nbrbutil -releaseMDS 4838(Make sure it is nt active job id...if its nt a active job id go ahead and relase it)
    5. Run the dump command again step 1 to verify the assignment has been released from the tape
    6. Resume/restart the job

4 Replies

Replies have been turned off for this discussion
  • Try these:

    1. Run /usr/openv/netbackup/bin/admincmd/nbrbutil -dump | grep <mediaID>
    2. If nbrb still has an open assignment for this tape, you will see quite a few lines of information, but look for the line containing “MdsAllocation
    3. Next to this will be a number so that it looks like this: MdsAllocation allocationKey=4838
    4. This is the assignment that needs to be released using this command: /usr/openv/netbackup/bin/admincmd/nbrbutil -releaseMDS 4838(Make sure it is nt active job id...if its nt a active job id go ahead and relase it)
    5. Run the dump command again step 1 to verify the assignment has been released from the tape
    6. Resume/restart the job
  • Hello, thanks for your answer!

    I will try this solution next time once i'll have the same problem. But do you have an explanation about what caused this issue please?

    Thanks in advance!

    Regards!

  • Probably it may happened because of the orphaned media allocation in the EMM server..

    If you face this error again verify tape is not already mounted or stuck in a tape drive via robtest  and proceed with the given steps.

    If the above steps dint resolve ur issue verify the nbemm logs for further troubleshooting.

    All the best :)

     

  • I have seen this happening quite often in NBU 6.5. Easpecially where a number of media servers are involved and comms/network issues are seen between master and media server.

    I have also seen this in NBU 7.x, but less often. It seems that NBU 7.x is better equipped to deal with allocations. Each and every version of NBU contains enhancements/fixes for the Resource Broker (nbrb).

    I have also seen this when a long list of media-id's (VTL) is reserved at the beginning of a duplication job (e.g. SLP) although not yet in use.

    Some TNs:

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

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

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

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