Re: : TSM Running out of Scratch Tapes
Hello, From the errors, it seems you are getting these against 2 Drives. * You can check through the actlog messages just before and after ANR8355E message to see what ishappening? * You can check those Tape Drive Device names in their paths are correct as seen on from OS? * You can verify if the Firmware of Tape/Drives and Library are on compatible levels with your environment. * You can try to run Audit from ACSLS and from TSM Server to match the inventory on both. * While checking in brand new scratch tapes(volumes), Label Libvol command should be used. Thanks Regards, Faisal Khan On Tue, Jul 9, 2013 at 8:31 AM, Adeel Mehmood ad.mehm...@diyarme.comwrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes 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
Re: : TSM Running out of Scratch Tapes
Hello,
to add
1) Check if there is mismatch between tapes and drives (mean lto3 tapes for
LTO5 tapes)
2) check inf those tapes that you are inserting into library have been
properly labeled (check output from label libvol command)
3) I can not see in your log last 2 symbols about tape LTO generation I
mean xxxyyy*L4*
4) check to see in bar codes for new tapes are check summed or not and
verify library setting about this...
On Tue, Jul 9, 2013 at 9:09 AM, Faisal Khan faisal...@gmail.com wrote:
Hello,
From the errors, it seems you are getting these against 2 Drives.
* You can check through the actlog messages just before and after
ANR8355E message to see what ishappening?
* You can check those Tape Drive Device names in their paths are correct as
seen on from OS?
* You can verify if the Firmware of Tape/Drives and Library are on
compatible levels with your environment.
* You can try to run Audit from ACSLS and from TSM Server to match the
inventory on both.
* While checking in brand new scratch tapes(volumes), Label Libvol
command should be used.
Thanks Regards,
Faisal Khan
On Tue, Jul 9, 2013 at 8:31 AM, Adeel Mehmood ad.mehm...@diyarme.com
wrote:
Dears ,
We are receiving below errors and the Scratch tapes goes to ZERO
07/04/2013 22:58:44 ANR8355E I/O error reading label for volume
001736 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 32773)
07/04/2013 23:04:23 ANR8355E I/O error reading label for volume
000588 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 32799)
07/04/2013 23:04:35 ANR8355E I/O error reading label for volume
000482 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 32806)
07/04/2013 23:10:55 ANR8355E I/O error reading label for volume
001058 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34240)
07/04/2013 23:11:01 ANR8355E I/O error reading label for volume
002081 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34242)
07/04/2013 23:15:49 ANR8355E I/O error reading label for volume
000468 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34242)
07/04/2013 23:16:21 ANR8355E I/O error reading label for volume
000828 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34240)
07/04/2013 23:20:33 ANR8355E I/O error reading label for volume
002284 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34242)
07/04/2013 23:21:13 ANR8355E I/O error reading label for volume
002084 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34240)
07/04/2013 23:26:29 ANR8355E I/O error reading label for volume
001367 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34255)
07/04/2013 23:28:24 ANR8355E I/O error reading label for volume
000386 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34215)
07/04/2013 23:36:08 ANR8355E I/O error reading label for volume
001804 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34215)
07/04/2013 23:37:04 ANR8355E I/O error reading label for volume
002323 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34255)
07/04/2013 23:44:47 ANR8355E I/O error reading label for volume
001814 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34255)
07/04/2013 23:45:05 ANR8355E I/O error reading label for volume
002535 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 24769)
Thanks best regards,
Adeel Mehmood
From: Adeel Mehmood
Sent: Tuesday, July 9, 2013 7:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes
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
Re: : TSM Running out of Scratch Tapes
From the messages, TSM is using 6 character tape labels. Is that your intent and has it always been so? Is your tape library and OS also using 6 character tape labels or might they be using 8 characters? David -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Tuesday, July 09, 2013 1:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes 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
Re: : TSM Running out of Scratch Tapes
David If I remember right, ACSLS only ever uses 6 char labels, Adeel, you need to either buy your tapes pre-labelled or label them yourself before first use using the label libvol command,. Did you do that? If it is only the new tapes that are having the problem, that is what I would suspect. Regards Steve Steven Harris TSM Admin Canberra Australia On 9/07/2013 10:08 PM, Ehresman,David E. wrote: From the messages, TSM is using 6 character tape labels. Is that your intent and has it always been so? Is your tape library and OS also using 6 character tape labels or might they be using 8 characters? David -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Tuesday, July 09, 2013 1:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes 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
Re: : TSM Running out of Scratch Tapes
Dear All, below steps has been used to checkin the new or offsite tapes as SCRATCH to the library . Please advise , if they can be improved further to solve this issue checkin libvolume sl3kacslib search=yes status=scratch checklabel=no label libvolume sl3kacslib search=yes overwrite=no checkin=scratch Thx, Adeel -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Tuesday, July 9, 2013 3:47 PM To: Adeel Mehmood Subject: Re: : TSM Running out of Scratch Tapes Those messages, in conjunction with your statement that these are new tapes, indicates that the problem is simply that you have not labeled them, as is fundamental when adding new tapes to a library. See that message number in http://people.bu.edu/rbs/ADSM.QuickFacts. Richard On Jul 9, 2013, at 1:31 AM, Adeel Mehmood ad.mehm...@diyarme.com wrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood 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.
Re: : TSM Running out of Scratch Tapes
On Jul 9, 2013, at 9:12 AM, Adeel Mehmood ad.mehm...@diyarme.com wrote: Dear All, below steps has been used to checkin the new or offsite tapes as SCRATCH to the library . Please advise , if they can be improved further to solve this issue checkin libvolume sl3kacslib search=yes status=scratch checklabel=no label libvolume sl3kacslib search=yes overwrite=no checkin=scratch Thx, Adeel I would recommend reviewing your Activity Log during the above operations to see how those operations actually did. Take one of the problem tapes and perform a 'dd' or like command to pull in the leading content of the tape, to see if there is actually a standard label there, and compare that to what's on one of your good tapes. Perform an explicit labeling operation on one of the problem tapes and attempt to use it. Richard Sims
Re: : TSM Running out of Scratch Tapes
Do you use library sharing? If you do, make sure the encryption settings on the device classes are the same on all the library clients. The label itself will be encrypted if the device class allows, and a library client with encryption disabled will not try to re-label the volume if it sees an encrypted label. -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine On 07/08/13 22:31, Adeel Mehmood wrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes 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
Re: : TSM Running out of Scratch Tapes
If you first run a checkin libvol before labeling them, TSM won't probably find any tapes to label. Run the following command to checkout all new tapes: Checkout libvol libraryname volumename checkl=n remove=n Now run the following command to label them: Label libv libraryname search=y labels=b checkin=scratch This will put a label on the tapes and check them in as scratch. Kind regards, Eric van Loon AF/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: dinsdag 9 juli 2013 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: : TSM Running out of Scratch Tapes Dear All, below steps has been used to checkin the new or offsite tapes as SCRATCH to the library . Please advise , if they can be improved further to solve this issue checkin libvolume sl3kacslib search=yes status=scratch checklabel=no label libvolume sl3kacslib search=yes overwrite=no checkin=scratch Thx, Adeel -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Tuesday, July 9, 2013 3:47 PM To: Adeel Mehmood Subject: Re: : TSM Running out of Scratch Tapes Those messages, in conjunction with your statement that these are new tapes, indicates that the problem is simply that you have not labeled them, as is fundamental when adding new tapes to a library. See that message number in http://people.bu.edu/rbs/ADSM.QuickFacts. Richard On Jul 9, 2013, at 1:31 AM, Adeel Mehmood ad.mehm...@diyarme.com wrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood 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. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment
Re: : TSM Running out of Scratch Tapes
Hi, From the looks of it (at least) 2 drives got their windows ID changed. Check from windows end if the drive/serial/mt is still matching path defined in tsm. Also make sure persistent binding and persistent naming are turned on otherwise drives will keep on jumping all over the place. After confirming and fixing all hardware config issues tapes should be reusable again. Kind regards, Karel - Oorspronkelijk bericht - Van: Adeel Mehmood ad.mehm...@diyarme.com Verzonden: dinsdag 9 juli 2013 7:31 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIV [Het originele bericht is niet volledig opgenomen]
: TSM Running out of Scratch Tapes
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.
Antwort: [ADSM-L] : TSM Running out of Scratch Tapes
...mmh, without any details ..some ideas: ..TSM related: - do you use TSM DRM, and if so what about the no. of days/reusedelay settings - ..and with the same background, what about reusedelay on your primary tape pools - audit library to find lost tapes - is expiration running daily to free your tapes - is space reclamation running daily to free your tapes .. not TSM related: - any growth other admins or users did not inform you about, so you really need more tapes regards, Dierk | | Von: | | --| |Adeel Mehmood ad.mehm...@diyarme.com | --| | | An:| | --| |ADSM-L@VM.MARIST.EDU, | --| | | Datum: | | --| |08.07.2013 11:14 | --| | | Betreff: | | --| |[ADSM-L] : TSM Running out of Scratch Tapes | --| | | Gesendet | | von: | | --| |ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU | --| 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. Bürgel Wirtschaftsinformationen GmbH Co. KG Gasstraße 18 22761 Hamburg Geschäftsführer: Klaus-Jürgen Baum, Dr. Norbert Sellin, Stefan Duncker Registergericht: Hamburg HRA 85212 USt-IdNr.: DE 117 981 371 Steuer-Nr.: 27/541/00020 Sitz der Gesellschaft: Hamburg Geschäftsführende Gesellschafterin: Bürgel Wirtschaftsinformationen Verwaltungs-GmbH Registergericht: Hamburg HRB 45 704 Umfassende Informationen: Die neue Bürgel Vollauskunft. Jetzt mit noch mehr Euler Hermes Expertise. Informationen unter http://www.buergel.de und http://www.buergel.de/vollauskunft Professionelles Forderungsmanagement für mehr Liquidität. Debitorenmanagement, Inkasso, Forderungskauf. Informationen unter http://www.buergel.de/produkte-leistungen/forderungsmanagement.html DDMonitor - Deutscher Debitoren Monitor. Transparenz hinsichtlich potenzieller Bonitätsrisiken innerhalb Ihres Kundenportfolios. Informationen unter: http://www.buergel.de/produkte-leistungen/wirtschaftsinformationen/ddmonitor.html BÜRGEL Wirtschaftsinformationen seit 1885
Re: : TSM Running out of Scratch Tapes
Sounds like you are having tape library problems. A defective tape drive, where a tape won't eject properly, is a common cause of Unavailable, as is a bad gripper dropping a tape inside the library. A tape drive which can't read or write properly will rapidly cause tapes to be forced read-only, as if they are bad, but they are not. So, look into you hardware there. Richard Sims, still at Boston University On Jul 8, 2013, at 5:13 AM, Adeel Mehmood 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
Re: : TSM Running out of Scratch Tapes
Hi Richard, Thanks for the input ,you are right we have lots of volumes getting unavailable in couple of weeks. We have replaced the 4 tape drives of 14 tapes drives a , but no luck ! Still getting lots for volumes becoming unavailable and Scratch tapes becomes ZERO ! Thanks , Adeel Mehmood -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Monday, July 8, 2013 2:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes Sounds like you are having tape library problems. A defective tape drive, where a tape won't eject properly, is a common cause of Unavailable, as is a bad gripper dropping a tape inside the library. A tape drive which can't read or write properly will rapidly cause tapes to be forced read-only, as if they are bad, but they are not. So, look into you hardware there. Richard Sims, still at Boston University On Jul 8, 2013, at 5:13 AM, Adeel Mehmood 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.
Re: : TSM Running out of Scratch Tapes
You may be able to run diagnostics to try to get information on what's going on. Definitely inspect OS logs and the TSM Activity Log for any details on the error condition. Also, verify that your drive and library firmware levels are at an appropriate version: replacement drives may come with an old firmware level, which could cause problems. Your tape drive technology may support TapeAlert, which could then be turned on. If still problematic, you could try putting suspect drives offline to try to isolate the troublemakers. An unlikely cause of problems would be a bad batch of tapes. (I once unspooled a name-brand problem tape to see if it had a physical media problem - and actually found a factory splice!) Richard Sims
Re: : TSM Running out of Scratch Tapes
If your tapes have been marked UNAVAILABLE because they were temporarily unavailable to TSM for whatever reason, but are otherwise undamaged and available, you could use SET VOLUME ... ACCESS=READWRITE to get them back. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Monday, July 08, 2013 2:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] : TSM Running out of Scratch Tapes 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.
Re: : TSM Running out of Scratch Tapes
Dear Margaret , Below is FYI The tapes are getting unavailable in huge numbers , we make them available but they become unavailable . and its going into a loop now and resulting in running out of scratch tapes! Thanks best regards, Adeel Mehmood -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, Margaret Sent: Monday, July 8, 2013 6:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes If your tapes have been marked UNAVAILABLE because they were temporarily unavailable to TSM for whatever reason, but are otherwise undamaged and available, you could use SET VOLUME ... ACCESS=READWRITE to get them back. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Monday, July 08, 2013 2:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] : TSM Running out of Scratch Tapes 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.
Re: : TSM Running out of Scratch Tapes
Hi, check if your drives need cleaning. Dirty drives are the cause of unavailable tapes. brgds Wojtek -- Wojciech Zukowski Gdansk, PL W dniu 08.07.2013 18:03, Adeel Mehmood pisze: Dear Margaret , Below is FYI The tapes are getting unavailable in huge numbers , we make them available but they become unavailable . and its going into a loop now and resulting in running out of scratch tapes! Thanks best regards, Adeel Mehmood -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, Margaret Sent: Monday, July 8, 2013 6:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes If your tapes have been marked UNAVAILABLE because they were temporarily unavailable to TSM for whatever reason, but are otherwise undamaged and available, you could use SET VOLUME ... ACCESS=READWRITE to get them back. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Monday, July 08, 2013 2:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] : TSM Running out of Scratch Tapes 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.
Re: : 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 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.
Re: : TSM Running out of Scratch Tapes
You should use the Q ACTLOG command with a begintime and begindate just before a bunch of tapes were marked unavailable to see more information about why this is happening. Though you are searching for a needle in a hay stack you may be able to narrow it down with the SEARCH option on the Q ACTLOG command. For instance, search on the volume name of a tape that you know got marked unavailable during that time period. You could also search on UNAVAILABLE. The error messages giving the reasons are in the ACTLOG, though finding them may take some searching. Roger Deschner University of Illinois at Chicago rog...@uic.edu == You will finish your project ahead of schedule. === = (Best fortune-cookie fortune ever.) == On Mon, 8 Jul 2013, white jeff wrote: 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 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.
Re: : TSM Running out of Scratch Tapes
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.commailto: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.
Re: : TSM Running out of Scratch Tapes
Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes 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.EDUmailto: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
