wirb
ADSM.ORG Member
- Joined
- May 7, 2004
- Messages
- 67
- Reaction score
- 0
- Points
- 0
- Location
- Western Washingtion, USA
- Website
- Visit site
Greetings, all,
I'm new to TSM. We're running 5.2.2 on Win2K using a 3583 library with 2 drives.
This is question is for my own information. I haven't been able to find it in any field guides nor has it turned up in searches on IBM's Tivoli-specific Web pages.
Why and how do tapes become marked unavailable? I know how to return them to R/W status, although it can be a pain to track down the specific volume coz I don't have all the command line syntax available, so I have to go via the Web admin GUI and look in the sequential storage. And this brings up a number of related questions:
Is there a way to configure TSM to send an alert when this happens, so a) I don't have to wade through the way-too-thorough log to find it and b) avoid getting "volume <volnam> is unavailable" messages when TSM tries to do a reclaimation or other process on that volume?
Is there a command-line command to track down the volume marked unavailable so I don't have to drill down through the GUI?
Is there a way to configure the log so it doesn't register EVERY TIME I open a GUI session, or make a change to a scheduled command (I've had to do a lot of adjusting of start and stop times), or register every time I issue a query or script from the command line?
My thanks to any who can answer.
I'm new to TSM. We're running 5.2.2 on Win2K using a 3583 library with 2 drives.
This is question is for my own information. I haven't been able to find it in any field guides nor has it turned up in searches on IBM's Tivoli-specific Web pages.
Why and how do tapes become marked unavailable? I know how to return them to R/W status, although it can be a pain to track down the specific volume coz I don't have all the command line syntax available, so I have to go via the Web admin GUI and look in the sequential storage. And this brings up a number of related questions:
Is there a way to configure TSM to send an alert when this happens, so a) I don't have to wade through the way-too-thorough log to find it and b) avoid getting "volume <volnam> is unavailable" messages when TSM tries to do a reclaimation or other process on that volume?
Is there a command-line command to track down the volume marked unavailable so I don't have to drill down through the GUI?
Is there a way to configure the log so it doesn't register EVERY TIME I open a GUI session, or make a change to a scheduled command (I've had to do a lot of adjusting of start and stop times), or register every time I issue a query or script from the command line?
My thanks to any who can answer.