This issue is discussed regularly, both within Tivoli and among Tivoli, business partners, and users.
The largest technical issue with doing this is the issue of aggregates. When TSM backs files up, it does so by aggregating files together and sending those aggregates to storage pools. To be able to retain active versions of files in one storage pool while sending inactive copies to cheaper or less-available pools would require massively and regularly tearing aggregates apart. This would just about negate the advantages of aggregates altogther. I don't know personally how large an impact that would have on overall TSM response time, but I've been told by Tivoli developers that the difference would be "orders of magnitude"; at that point, I said, "Oh. Never mind." -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627 >-----Original Message----- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Matthew Glanville >Sent: Friday, September 09, 2005 2:56 PM >To: [email protected] >Subject: Re: A quick question about stgpool. > >"ADSM: Dist Stor Manager" <[email protected]> wrote on 09/09/2005 >03:21:35 PM: > >> I was just mulling about the Idea to speed up large restores of small >files, >> without resorting to image backup, keeping everything on disk, or >> collocating tapes. If I could keep just the active copy on >disk I could >> speed up the restore considerably while keeping inactive >copies on tape. >> > >This would be a great addition to TSM. > >Instead of spending extra $'s on 'flash copy' type >hardware/disk solutions >and time consuming image backups we could accomplish the same thing >through a simple TSM incremental and save the day on a large >restoration! > >Let us all request it and get it in TSM 5.4! > >Matt G. >
