From the Q STG out put, we only have a disk pool and a tape pool.
I have usually errors during backup because the tapes are full.
When there are no space available in the diskpool and tape pool, this is is correct if we are receiving the message that the server is out of storage space.
Maybe there is an error (like expiration etc) but i havent experience how to check and fix it (i am afraid)
You have the advantage on me.
Review the activity log. It's really not a log file, its a record of what is going on with the TSM Server.
Via the TSM Server Command Line (dsmadmc) issue: q act
For more information about the "
q act" via the dsmadmc issue: help q act
Or look up the q act in the TSM Server manual.
Or do a google search for TSM Server and query activity log.
Is good idea to delete all lto tapes and make backup such as first day the IBM installed TSM at our company using the current tsm schedule? (as i unterstand the lto tapes are using for backup of oracle DB , 2 AIX and 2 windows servers).
That all depends what you can tolerate and if the company is okay with you deleting all the data on the LTO tapes.
If we delete all the LTO tapes, an end user will not be able to restore any data that was previously backed up.
When the next schedule backup run, ALL the clients will perform a full backup and there will be heavy network traffic.
Can i free storage at stgpools so i don't need to delete lto?
- Increase the capacity of the disk pool. Of course, once we hit the high migration threshold, the TSM Server will try to move the data into the tape pool. The migration process will fail if there is no space in the tape pool.
- Add more scratch tape into the tape library.
How to find which lto tapes i can re-use?
Issue
q volume look for tapes that have low pct util, then issue a
move data
If the move data fails, then there is no space on other tapes to move the data to.
Good Luck,
Sias