Hi,

If possible post the nbrb logs when the valut was hung....

Hi Manjunath,

Here are the logs:

Dec 31, 2012 9:04:28 PM - end Vault: Start Notify Script; elapsed time 0:00:01
Dec 31, 2012 9:04:28 PM - begin Vault: Execute Script
Dec 31, 2012 9:04:28 PM - started process bpbrm (pid=11283)
Dec 31, 2012 9:04:29 PM - requesting resource asprd222.aldc.att.com.VAULT_CREATE_SESSION_ID.LOCK_TLD(0)_Production
Dec 31, 2012 9:04:35 PM - granted resource  asprd222.aldc.att.com.VAULT_CREATE_SESSION_ID.LOCK_TLD(0)_Production
Dec 31, 2012 9:04:43 PM - vault session ID lock acquired
Dec 31, 2012 9:04:43 PM - vault session ID lock released
Dec 31, 2012 9:08:44 PM - Duplication skipped
Dec 31, 2012 9:08:44 PM - vault waiting for assign slot lock
Dec 31, 2012 9:08:44 PM - requesting resource asprd222.aldc.att.com.VAULT_ASSIGN_SLOT.LOCK_TLD(0)_Production
Dec 31, 2012 9:08:52 PM - granted resource  asprd222.aldc.att.com.VAULT_ASSIGN_SLOT.LOCK_TLD(0)_Production
Dec 31, 2012 9:08:58 PM - vault assign slot lock acquired
Dec 31, 2012 9:09:14 PM - vault assign slot lock released
Dec 31, 2012 9:09:15 PM - Catalog Backup skipped
Dec 31, 2012 9:09:15 PM - vault waiting for assign slot lock
Dec 31, 2012 9:09:30 PM - vault assign slot lock acquired
Dec 31, 2012 9:09:32 PM - vault assign slot lock released
Dec 31, 2012 9:09:16 PM - requesting resource asprd222.aldc.att.com.VAULT_ASSIGN_SLOT.LOCK_TLD(0)_Production
Dec 31, 2012 9:09:25 PM - granted resource  asprd222.aldc.att.com.VAULT_ASSIGN_SLOT.LOCK_TLD(0)_Production
Dec 31, 2012 9:09:35 PM - before eject, waiting for media to be unmounted; sleeping for 380 seconds
Dec 31, 2012 9:15:55 PM - starting eject operation
Dec 31, 2012 9:15:55 PM - begin Eject and Report
Dec 31, 2012 9:15:55 PM - connecting
Dec 31, 2012 9:15:55 PM - connected; connect time: 0:00:00
Dec 31, 2012 9:15:57 PM - vault waiting for eject lock
Dec 31, 2012 9:15:57 PM - requesting resource asprd222.aldc.att.com.VAULT_EJECT.LOCK_0
Dec 31, 2012 9:16:11 PM - Info nbrb (pid=7943) Limit has been reached for the logical resource asprd222.aldc.att.com.VAULT_EJECT.LOCK_0

this is where the prcess stops.

hi, looks like you have another Vault job running... For each vault name only one vault profile can be run at a time. This is by design in Netbackup vault feature and cannot be changed. If that is the case follow the below steps. •Create new vault along with existing one •Move the other profile to the new vault, or create a new profile under the new vault. Then try to run concurrently both profiles, will allow the two vault profiles.

*** EDIT ****

Hi,

It looks lke similar kind of issue found in below link. Refer below for more information.

https://www-secure.symantec.com/connect/forums/vault-job-gets-hung 

Thanks Manjunath

:)

let me try that !!