I'm sure Wanda has thought of this, but since she didn't explain why she ruled it out, I'll throw it out just in case:
BACKUP NODE allows for a management class. I presume the customer is doing a mix of full differentials and fulls. Why not do an extra differential with a different management class specifically to get something to expire early and thus start the dedupe process? I love my NDMP clients, too. They really do screw up the tape expiration patterns, especially when a weekly full fails and a prior full lasts an extra week. Nick On Nov 21, 2011, at 10:40 PM, Prather, Wanda wrote: > Have a customer would like to go all disk backups using TSM dedup. This > would be a benefit to them in several respects, not the least in having the > ability to replicate to another TSM server using the features in 6.3. > > The customer has a requirement to keep their NDMP dumps 6 months. (I know > that's not desirable, but the backup group has no choice in the matter right > now, it's imposed by a higher level of management.) > > The NDMP dumps come via TCP/IP into a regular TSM sequential filepool. They > should dedup like crazy, but client-side dedup is not an option (as there is > no client). > > So here's the question. NDMP backups come into the filepool and identify > duplicates is running. But because of those long retention times, all the > volumes in the filepool are FULL, but 0% reclaimable, and they will continue > to be that way for 6 months, as no dumps will expire until then. Since the > dedup occurs as part of reclaim, and the volumes won't reclaim -how do we > "prime the pump" and get this data to dedup? Should we do a few MOVE DATAs > to get the volumes partially empty? > > > Wanda Prather | Senior Technical Specialist | > [email protected]<mailto:[email protected]> | > www.icf.com<http://www.icf.com> > ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | > 410.539.1135 (o) > Connect with us on social media<http://www.icfi.com/social>
