we’re getting about 0% dedup savings (3 * full, plus diffful, plus log backups) and about maybe 20% compression savings.
> On 21 Feb 2018, at 16:03, PAC Brion Arnaud <arnaud.br...@panalpina.com> wrote: > > Hi Remco, > > No direct answer to your question, but your statement " dedup on SQL is > non-existant" is kind of astonishing me ... > > Here an extract of the output for "q stg DIR_SQL f=d" on my server (you > guessed it, this stgpool is dedicated to SQL backups ...) : > > Deduplication Savings: 34,513 G (60.21%) > Compression Savings: 17,517 G (76.81%) > Total Space Saved: 52,030 G (90.77%) > > Altogether 90,7 % data reduction ! > > I would be curious to hear what our TSM fellows in this list are achieving ... > > Cheers. > > Arnaud > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Remco Post > Sent: Wednesday, February 21, 2018 3:06 PM > To: ADSM-L@VM.MARIST.EDU > Subject: empty containers? > > Hi All, > > today I ran into something new: an empty directory container. No, not an > empty directory, and empty container. We’re moving SQL backups from > directories to traditional tape, dedup on SQL is non-existant, so tape is > cheaper, and after the expiration period the container pool should be empty. > Well this being the real world and all, of course I have a few containers > left. Move container bla bla to reduce disk usage. All nice, exceprt for some > containers that are now empty, thus can’t be moved… How do I get rid of > those? TSM server level 8.1.1.100 > > -- > > Met vriendelijke groeten/Kind Regards, > > Remco Post > r.p...@plcs.nl > +31 6 248 21 622 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622