Re: Space Reclamation Eating Tapes
On Nov 28, 2005, at 11:42 AM, Sung Y Lee wrote: It has been my experience that, if primary tape pool maxscratch value is set greater than tapes used when reclamation kicks off, it mounts a brand new scratch tapes. ... I've never seen that behavior - that would result in a large number of tapes in Filling state, and that does not happen. TSM requests a fresh tape when the would-be candidate filling tape is in an unusable state (as from previous tape errors) or that volume is in use (current output volume or being dismounted). If a TSM instance was always calling for new volumes, that would constitute a violation of its design, and should be reported as a defect. In any case, this thread is largely proceeding without substantive information. We need to see the results of analyses which examined tape states, Activity Log, and volume contents. Richard Sims
Re: Space Reclamation Eating Tapes
It has been my experience that, if primary tape pool maxscratch value is set greater than tapes used when reclamation kicks off, it mounts a brand new scratch tapes. I suspect that there is some logical reason how tapes are reclaimed ... such as why not taking already used tape. However I have had success by lowering the maxscratch count less than tapes used will allow TSM not to use new scratch tapes but use already used tapes. Now, if one is using collocation, I tried to think of a reason why one would starting reclamation. My experience shows that since any gain of tapes by performing reclamation of collocation pool is short lived because TSM will shortly attempt to use new scratch tapes. Sung Y. Lee "ADSM: Dist Stor Manager" wrote on 11/28/2005 09:21:45 AM: > I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 > and since then, it seems that whenever I kick off space reclamation for > my primary tape storage pools, it eats up scratch tapes, instead of > freeing them up. Is there a reason for this? I understand that > occasionally TSM will need a scratch tape to combine other tapes, but it > should then free those other tapes up and return them to the scratch > pool. I've checked the reuse delay on the storage pools, and they are > set to 0, so I know that isn't the problem. > > > Mel Dennis
Re: Space Reclamation Eating Tapes
Such as? :) Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Things have changed in 5.3. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:35 To: ADSM-L@VM.MARIST.EDU Subject: Re: Space Reclamation Eating Tapes Don't think that is it, I only have 2 storage pools out of like 12 that have collocation turned on (these storage pools are for large file servers). So collocation shouldn't be affecting most of them. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Things have changed in 5.3. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:35 To: ADSM-L@VM.MARIST.EDU Subject: Re: Space Reclamation Eating Tapes Don't think that is it, I only have 2 storage pools out of like 12 that have collocation turned on (these storage pools are for large file servers). So collocation shouldn't be affecting most of them. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Don't think that is it, I only have 2 storage pools out of like 12 that have collocation turned on (these storage pools are for large file servers). So collocation shouldn't be affecting most of them. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Space Reclamation Eating Tapes
I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
