cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to release MDS allocation ley

Karthick_S
Level 3
Certified

Media Manager daemons not running even after bouncing NBU services.

# ./vmoprcmd -d
oprd returned abnormal status (96)
IPC Error: Daemon may not be running

LTID debug log

02:28:41.603 [7063] <16> InitLtidDeviceInfo: Drive XXXX is ACTIVE
02:29:11.603 [7063] <4> CheckShutdownWhileInit:

Unable to release allocations for this drive. I have tried reset media server option too. It did not work.

24 REPLIES 24

nbrbutil -releaseMDS 55846077

It did not give any error neither release the allocation.

Tape is not in the drive. Verified through robtest.

You can also try nbrbutil -resetMediaServer [mediaserver]

This command resets specific media server and should not affect other jobs.

 

Thanks

Sreekanth

  

Marianne
Level 6
Partner    VIP    Accredited Certified

Seems the OP has tried everything except -resetall option or complete restart of NBU on the master server.

I have honestly not seen 'stubborn' orphaned allococations such as this since 6.5 days.

Seems something 'unhealthy' with nbrb on the master server...

Probably a good idea to look at NBU patch levels on the master?
And perhaps OS resources on the master?

Both master and media server are in patch 7.6.0.3. Got downtime for next week to reset all and restart NBU services on Master server. 

Hope that would fix the issue!  Keep you posted.

MdsAllocation: allocationKey=55846077 jobType=1 mediaKey=4035269 mediaId=W91587 driveKey=2001252 driveName=DLT7_53_DP_19 drivePath=/dev/rmt/7cbn stuName=DP19_VTL masterServerName=wspebrms01-ebr mediaServerName=<media server name> ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverStateFlags=1

 

your previous command showed "mediaId=W91587" to be in drive, if robtest is showing no tape, im guessing there is conflict in your netbackup database, 

Can you run the command again and see if the command still shows above tape or any other tape , assuminig thse are VTL, 

 

Im no fan of resetting or restarting NB without actually knowing the cause ;) ;)