Dear ,
Thanks for your response . please find the answers below . It is most useful if you state which version of TSM server you are running. -------------- > TSM 6.2 The OS it runs on and the tape media (LTO3/4/5 etc.) would be helpful -------------------- > Windows 2008 Server , configured with SL3000 Library through ACSLS Software having 14 x HP LTO4 FC Tape Drives. What retention policies are in place for the domain copy groups? If NOLIMIT is in force, then data will never expire and will eventually use all of your tapes ---- > Retention Polices seems to be working fine as they are In place for more than two years & half years and we started facing this problem couple of weeks back . When you say tapes are becoming 'unavailable', is this the status of the volume within TSM? (Do a 'q vol f=d' to check). If so, this is often because you are trying to use tapes that have been physically removed from the library. If TSM wants to use that tape, it will eventually place the tape in an 'UNAVAILABLE' state because it cannot mount the volume in the library as a result of being removed. ----- > we are 100 % sure that the tapes are physically inside .The NEW/OLD tapes become UNAVAILABLE , whenever the TSM try to use them for backup or restore. but once we make them available , we could use them for some time . till they get unavailable again . In terms of running low on scratch, as the previous poster said, make sure expiration and reclaim is running. In particular, make sure reclaim is running and actually completing. The SUMMARY table will report on expiration and reclaim activity over a period of time (usually 28 days) ----- > we double check the same. How many versions of database backups do you retain? ------ > 14 versions These are common causes of tape problems. ------ > we are using Brand New Tapes and they are also getting UNAVAILABLE , also we opened a case with Library Vendor and they said all is well . Best regards, Adeel -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of white jeff Sent: Tuesday, July 9, 2013 12:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes Hi It is most useful if you state which version of TSM server you are running. The OS it runs on and the tape media (LTO3/4/5 etc) would be helpful What retention policies are in place for the domain copygroups? If NOLIMIT is in force, then data will never expire and will eventually use all of your tapes When you say tapes are becoming 'unavailable', is this the status of the volume within TSM? (Do a 'q vol f=d' to check). If so, this is often because you are trying to use tapes that have been physically removed from the library. If TSM wants to use that tape, it will eventually place the tape in an 'UNAVAILABLE' state because it cannot mount the volume in the library as a result of being removed. In terms of running low on scratch, as the previous poster said, make sure expiration and reclaim is running. In particular, make sure reclaim is running and actually completing. The SUMMARY table will report on expiration and reclaim activity over a period of time (usually 28 days) Establish the percent-reclaimable space of your tape volumes. Use this command: SELECT VOLUME_NAME, STGPOOL_NAME, PCT_RECLAIM, STATUS FROM VOLUMES WHERE VOLUME_NAME LIKE '%L3' (This is assuming you are using LTO3 tape. Change accordingly) How many versions of database backups do you retain? These are common causes of tape problems. On 8 July 2013 10:13, Adeel Mehmood <ad.mehm...@diyarme.com<mailto:ad.mehm...@diyarme.com>> wrote: > Dears , > > We are facing problem as the TSM scratch tapes are running out , also > the tapes becoming unavailable . > Please advise , how to handle this issue . > > Thanks , Adeel > > ________________________________ > > D I S C L A I M E R > > The information in this email and in any files transmitted with it, is > intended only for the addressee and may contain confidential and/or > privileged material. Access to this email by anyone else is unauthorized. > If you receive this in error, please contact the sender immediately > and delete the material from any computer. If you are not the intended > recipient, any disclosure, copying, distribution or any action taken > or omitted to be taken in reliance on it, is strictly prohibited. > Statement and opinions expressed in this e-mail are those of the > sender, and do not necessarily reflect those of the company. >
