Look at your storage pools and see which ones have collocation turned on: Select stgpool_name, collocate from stgpools where collocate<>'NO'
Does that match up against the storage pools that have lots of tapes: Select stgpool_name, count(stgpool_name) from volumes group by stgpool_name order by 2 desc If you have collocation turned on it will use a lot of tapes. Filespace collation will have at least 1 tape per filespace. YES location says at the node level. That means 1 tape per node at least. You referred to the second select. Is this the one you are talking about: Select cast(volume_name as char(7)) as "Volume", cast(substr(stgpool_name,1,25) as char(25)) as "Storage Pool ", cast(pct_utilized as decimal(5,2)) as "% Util", cast(status as char(10)) as "Status ", cast(access as char(10)) as "Access " from volumes where pct_utilized < 40 order by 3 Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Lai, Kathy KL [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 08, 2002 9:37 PM To: [EMAIL PROTECTED] Subject: Re: Consumption of new scratch tape increase abnormally Dear all, As I am new to use ADSM, the setup of the ADSM server is by some other body. Therefore, would anyone can explain more details to me that what can I do after I go the result from the SQL that Paul suggested to run? What kind of result show that I have some problem in my operation? And what should I do to solve it? I think there should be some problem, otherwise, tapes consumption should not increase so significant without much data growth. Thanks a lot! > Regards, > Kathy Lai -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 04, 2002 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Consumption of new scratch tape increase abnormally What the second SQL does is lists the tapes that are less than 40% utilized. I am betting you have collocation turned on by file space or something like that. Check that first before we go any further. If you have collocation turned on, you did it for a reason. There is a price to pay and you are experiencing it. You can cause the tapes to fill up by turning collocation off and doing move data commands to force the tapes to move their data to other tapes and then scratch. There is another option. You can create another storage pool with collocation turned off if this a primary pool problem. Then move all the tapes that have a very small amount of data on them to that pool. Consider how this may affect your backup stgpool commands also. Remember you cannot move a copy pool to another copy pool. I will help if I can. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Lai, Kathy KL [mailto:[EMAIL PROTECTED]] Sent: Monday, September 02, 2002 3:21 AM To: [EMAIL PROTECTED] Subject: Re: Consumption of new scratch tape increase abnormally Dear Paul, Thanks for you help. I've got the information base on the SQL you provided. How can I analyze my information so that I can know where my tapesss gone... I got around 1400 tapes from the result of the second SQL. Does it mean that I have great problem on that? If yes, how can I solve it? Thank you very much. > Regards, > Kathy Lai -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 29, 2002 1:16 PM To: [EMAIL PROTECTED] Subject: Re: Consumption of new scratch tape increase abnormally "I know the name of this tune." Is expiration running? What is the reclaim percent for your pools? Issue this command to see how your volumes fair on utilization on average: Select cast(avg(pct_utilized) as decimal(5,2)), stgpool_name, count(stgpool_name) from volumes group by stgpool_name order by 1 Issue this one to figure out what the bad ones are: Select cast(volume_name as char(7)) as "Volume", cast(substr(stgpool_name,1,25) as char(25)) as "Storage Pool ", cast(pct_utilized as decimal(5,2)) as "% Util", cast(status as char(10)) as "Status ", cast(access as char(10)) as "Access " from volumes where pct_utilized < 40 order by 3 And "my all time favorite", find out the tapes that were checked in private that should be scratch: select volume_name from libvolumes where status='Private' and libvolumes.volume_name not in (select volume_name from volumes) and libvolumes.volume_name not in (select volume_name from volhistory where type in ('BACKUPFULL', 'BACKUPINCR', 'DBSNAPSHOT', 'EXPORT')) Hope this helps. The quotes are from the Fifth Element, which character? Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Lai, Kathy KL [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 9:46 PM To: [EMAIL PROTECTED] Subject: Consumption of new scratch tape increase abnormally Dear all, I am using ADSM v3.1 with HSM and DRM option. Recently ( this half year ) I found that the consumption of new scratch tape increase abnormally. I have to initial 180 tapes in only 23 days!!! However, I have check that the backup volume doesn't have great change. What is the cause of the scenerio? Will there be any problem in my daily operation so that tapes that have been initilize cannot be reuse so the consumption of new tapes increase so significantly? Please help as it is a quite urgent issue as my management will not invest anymore to buy new tapes if the root cause of this scenerio cannot be found!!! Thank you very much. > Regards, > Kathy Lai > Outsourcing & Managed Services > Pacific Century CyberWorks > * 852-8101 2790 > [EMAIL PROTECTED] >
