Ejected media still showing in the library as TLD
Created: 26 Nov 2012 | Updated: 26 Nov 2012 | 11 comments
This issue has been solved. See solution.
After ejecting medias from the library. The medias re still displaying in the library as TLD. Please advice what to do.
Discussion Filed Under:
Comments 11 Comments • Jump to latest comment
Please share exact details of how eject was done.
If incorrect procedure is used, the eject will fail and tapes will be returned to slots.
Eject steps that we normally recommend:
Manually select the tapes in the Media section of the GUI, right-click, select “Eject Volume(s) from Robot….”
A new window will open with 'pre-checks' on the list of tapes to be ejected.
After a short while NetBackup will complete the eject pre-checks.
If the list is correct, click “Eject”.
This will eject all the media listed into the Media Ejection Port (MAP/CAP) on the library. Once all media has been moved into the CAP, a pop up will appear asking "Do you want to continue with the eject?". Do NOT click YES as yet.
You can now go to the Library and remove the tapes from the CAP.
Once you have removed the tapes and closed the CAP (wait ±2 mins), click on YES on the above screen.
NB. Only click “Yes” after you have removed the tapes from the CAP.
Once completed, “Eject success” will be displayed.
Click on Close to update Media List.
(Above process corresponds with second part of Andy's post: https://www-secure.symantec.com/connect/forums/eject-tape-media-stk-sl3000-tape-library-data-it#comment-7820411 )
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
I presume you ejected the media using the library in which case you need to run an inventory from NBU.
In the future, eject the media from within NBU.
Martin
The medias were actually ejected into the access port. After i took all the medias out, i clicked continue to eject. Then i got an error " media eject aborted' media eject ended with errors. Its strange because, this is like 1 thousand times i have ejected medias successfully. So i have no idea what happened. But please i need your expertise.
Do i need to inject the medias again, and re-start the process of ejecting all over?
How long between selecting “Eject” and then "... continue with the eject?"
There is an eject timeout. If I'm not mistaken, the timeout is something like 5 minutes.
Yes, it is 5 minutes - see this TN: http://www.symantec.com/docs/TECH163557
Add a directive to the /usr/openv/volmgr/vm.conf file on the robot control host, and restart MM daemons for the change to take effect. The directive is
For example, to set the amount of time to remove tapes from the MAP to 15 minutes, add the directive
and restart MM processes on the robot control host.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Just run Inventory - it will update NBU with actual robot contents.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Marianne, i am so greatful for your wonderful support on this portal. God bless you. case resolve after running inventory. Thank you ones again.
To be fair, mph999 gave you the solution 20 minutes before Marianne did.
revaroo you are right. mph999 please accept my apology. We are all here to make working fun. Marianne has been my personal instructor all the years, so i got hooked with her advice...."smile"
Marianne is a NetBackup Warrior :)
And I look up to Martin (mph999)!
The short-term solution is to run inventory.
The error you received is probably because of 5-minute timeout.
If you don't add the vm.conf entry, its going to happen again....
So, the post about MAP_CONTINUE_TIMEOUT is the permanent solution.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Would you like to reply?
Login or Register to post your comment.