05-09-2013 01:29 AM
Hi,
Our vault jobs are running, saying they are to eject media, but the robot doesn't actually move the media to the mailslots. The job keeps running and doesn't finish. As you can see, the job is still running from yesterday. We have two tape libraries and it's the same on both.
Any ideas?
08/05/2013 10:38:14 - Info nbjm(pid=5132) starting backup job (jobid=4903088) for client XXXX75, policy Vault_eject-xxxxbkp, schedule Daily 08/05/2013 10:38:14 - Info nbjm(pid=5132) requesting NO_STORAGE_UNIT resources from RB for backup job (jobid=4903088, request id:{085B6062-F7DB-477B-81E3-CC143621F230}) 08/05/2013 10:38:14 - requesting resource XXXX75.NBVAULT.MAXJOBS 08/05/2013 10:38:14 - requesting resource XXXX75.NBU_POLICY.MAXJOBS.Vault_eject-xxxxbkp 08/05/2013 10:38:14 - granted resource XXXX75.NBVAULT.MAXJOBS 08/05/2013 10:38:14 - granted resource XXXX75.NBU_POLICY.MAXJOBS.Vault_eject-xxxxbkp 08/05/2013 10:38:15 - begin Eject/Report 08/05/2013 10:38:15 - connecting 08/05/2013 10:38:15 - connected; connect time: 00:00:00 08/05/2013 10:38:15 - estimated 0 Kbytes needed 08/05/2013 10:38:15 - begin Parent Job 08/05/2013 10:38:15 - begin Vault, Start Notify Script 08/05/2013 10:38:15 - Info RUNCMD(pid=7216) started 08/05/2013 10:38:15 - Info RUNCMD(pid=7216) exiting with status: 0 Status 0 08/05/2013 10:38:15 - end Vault, Start Notify Script; elapsed time: 00:00:00 08/05/2013 10:38:15 - begin Vault, Execute Script 08/05/2013 10:38:15 - started process bpbrm (4728) 08/05/2013 10:38:16 - vault waiting for eject lock 08/05/2013 10:38:16 - requesting resource XXXX75.VAULT_EJECT.LOCK_1 08/05/2013 10:38:16 - granted resource XXXX75.VAULT_EJECT.LOCK_1 08/05/2013 10:38:17 - vault eject lock acquired 08/05/2013 10:38:20 - suspend media for this session: failed to suspend 1 of 43 media at eject time 08/05/2013 10:38:20 - starting eject of 18 media
Solved! Go to Solution.
05-09-2013 06:44 AM
It picks some media for eject ...
05-09-2013 04:48 AM
Check your actual mailslot and make sure they're emptied out if occupied with tapes. It may have ejected some , and is waiting for available mailslot to eject further.
If mailslot has no tape at all, check the session details in \vault\sessions\sid###\logs\detail.log to see what it's waiting for.
05-09-2013 05:39 AM
Thanks for the reply but of course I have checked the mailslot!!
I've uploaded the latest detail.log (renamed to txt), if anyone would like to take a look.
Cheers
05-09-2013 06:44 AM
It picks some media for eject ...
05-09-2013 06:51 AM
Thanks Martin. We haven't changed the configuration and this was working ok until this week. Why would you use deffered instead of immediate?
05-09-2013 07:40 AM
Simply to prevent the tapes ejecting at the time th evault runs. Somepeople like to control this as a separate step.
Perhaps you could check the vault profile (under the eject tab) to see if deferred eject really is set, there is always a possibility I have mis-understood the log.
Though I have to say it seems quite clear in this case:
16:03:59.621 [10412.7840] <2> vltrun@VaultJobMonitor::_send_try_msg^1315: At 1368025439 sent TRY_MSG: VAULT_EJECT_DEFERRED 1368025439
Martin
05-09-2013 07:49 AM
It's set to deferred in the vault profile.
How can I make it immediate as a one off?
05-09-2013 01:41 PM
Try running this command vlteject -eject
from the Vault Admin Guide:
Ejecting media
If you configure a profile to defer ejection, you must perform or schedule another
action to eject media.
You can use one of the following actions to eject media that was not ejected by a
profile that selected or duplicated images:
■ Manually by using the Vault Management node in the NetBackup
Administration Console
■ Manually by using the Vault Operator Menu
■ Manually by using the vlteject command
■ Automatically by creating and scheduling a Vault policy and entering the
appropriate vlteject command and options in the file list
05-09-2013 11:10 PM
Unfortunately, you cannot set this as a one-off - it is either set as deferred or not.
Martin