Exactly what I needed to know. Thanks Remco. (.... and saves me the trouble of putting in another RFE!)
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco Post Sent: Thursday, December 27, 2012 12:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Help with NDMP dump & diff expiration Hi, I once raised an RFE for managing diffs separately from the fulls. Unfortunately the answer is NO. workaround: use multiple nodenames and make fulls on both nodenames and diffs only with one.... yes a pita and a waste of tapes... if only IBM could think of something better ;-) On 27 dec. 2012, at 18:05, "Prather, Wanda" <wanda.prat...@icfi.com> wrote: > Need some help from folks doing "external" NDMP dumps, where TSM triggers the > dump but it's done by the NAS device across the fibre to pool defined as > TYPE=NDMPDUMP, not a standard TSM storage pool. > > Have a customer installing an EMC (VNX) NAS which will store multiple > millions of .pdf files. The data change rate is very low, but can't back up > via the CIFS mount using the regular client, too many files to scan the > filesystem. And VNX doesn't support snapdiff. > > So the plan is to have the VNX do full and diff dumps under TSM control. > Customer wants monthly fulls + daily diffs between, and wants to be able to > go back a year. > > My experience is with NDMP via TCPIP in a normal TSM storage pool, but the > thing I see there is that when you do a new full, the previous diffs don't > expire. > > There's no reclaim for a pool defined as TYPE-NDMPDUMP, so how do you handle > this without keeping 365 cartridges tied up in the vault? Is there a good > way to blow way those "in between" diffs? > > Thanks and Happy New Year > > Wanda (NDMP is Evil) P > > > Wanda Prather | Senior Technical Specialist | > wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. > Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o) -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
