Vault eject hung
Hi
Current environment:
Master server running on Redhat Linux 6 with NBU version 7.6.0.3
ACS robot.
While ejecting the vaulting tapes, the job fails with an error (278: Unable to collect pre eject information from the API).
I have searched through Symantec forums, and tried as suggested in various forum threads, but i am unable to get it to work.
From Admin GUI, when i choose deffered eject to eject the tapes, i clearly see that there is 2 session there, one which is the correct one with all the tapes that needs to be ejected, while there is another session there most probably a stuck job from previous eject: see attachment.
Anyhow, what i have tried so far, is to look for a Eject*.txt file in the following location on my Linux master server: /usr/openv/volmgr/misc
I do not have any eject files there at all. Files i have the are as follows:
bpdbm_upgrade.lock
DqDriveState
lmfcd.lock
ltitables
README
robotic_db
tl8cd.lock ----> already tried renaming them to resolve the issues, without any luck
tldcd.lock ----> already tried renaming them to resolve the issues, without any luck
tlhcd.lock ----> already tried renaming them to resolve the issues, without any luck
vmd.lock
and alot of acssel.lock files followed by the mediaservername and som sort of number. 13751.
Another issue i have is that, once i try to amment something and give it a go, i have to wait for 2 hours before the job cancels. I have tried the command line as well as GUI to cancel the job, but it just wont do anything, and i end up waiting for approx 2 hours before Netbackup stops the job. Any other way of cancelling it faster?
we resolved the issue by manually ejecting the tapes from acsls server. Problem with that is that net backup does not get updated, so even running an inventory would fail. Ended up creating a technical support case. We verified that no jobs were running on this particular media server, which also is a master server. Technician restarted the vmps services, some of them had to be killed by "kill -9" option. Then he ran the inventory from the command line. Everything cleared up after that. Now Even from GUI everything is working fine. Send like restarting the vmps services did the Job.

