Hi Rod! TSM stores backups as aggregates. An aggregate can contain multiple client backup files. The client files within an aggregate will expire over time and thus occupy space within the aggregate. When you use a file device class or a tape, you can reclaim the wasted space these expired files occupy within the aggregates by moving unexpired files to new aggregates. This is done through reclamation. Since reclamation is only available for sequential acces storage pools, you cannot reclaim diskpools and thus the wasted space within an aggregate will only be reusable when all the files in an aggregate are expired and the aggregate is deleted. If you have backups with a very long retention in your shop, it could take quite some time before an aggregate becomes completely empty. Hope this clears thing up for you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: donderdag 6 april 2006 15:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: Random Access Disk Pools anyone? Ideas? -----Original Message----- From: Park, Rod Sent: Wednesday, April 05, 2006 7:10 AM To: 'ADSM: Dist Stor Manager' Subject: RE: [ADSM-L] Random Access Disk Pools So, can someone explain the difference at the TSM level and aggregate level. Really I'm trying to understand, if I have a primary disk pool that does not migrate, it will be the final onsite resting place of data. As data expires and fragmentation occurs. That space is unusable if I'm not migrating to another primary area? Eventually I'll have to allocate more? Below is what comparison doc showed as "consideration of fragmentation" for random access pools. Guess I'm not sure what the diff is between tsm level and aggregate level. TSM level - fragmentation will occur as TSM allocates and frees space within the Storage Pool. Migration tends to relieve this fragmentation Aggregate level - fragmentation occurs as files expire within an aggregate. DISK pools cannot reclaim this wasted space until all files in the aggregate have expired -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim Sent: Tuesday, April 04, 2006 11:21 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools See http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21218415 for comparison of disk vs devclass=file This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. ********************************************************************** 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 is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
