Re: TSM7.1.7 DB growing with Dedup

, April 20, 2017 9:38 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM7.1.7 DB growing with Dedup You're welcome Bill. And yes, you need to bring down TSM for an offline reorg, they are very fast however, especially if you run them on SSD's as a target location for the reorg and you do

Re: TSM7.1.7 DB growing with Dedup

hanks! > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Stefan Folkerts > Sent: Friday, April 14, 2017 2:02 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM7.1.7 DB growing with Dedup > > Hi Bill, > &g

Re: TSM7.1.7 DB growing with Dedup

-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM7.1.7 DB growing with Dedup Hi Bill, I don't know what is going on the the protect stgpool command vs replicate node in regards to DB usage but the conversion growth...i've been there a few times before, it happens with every conversion because

Re: TSM7.1.7 DB growing with Dedup

Bill, I forgot to link this document from IBM, some good info here : https://www-01.ibm.com/support/docview.wss?uid=swg21992410 On Fri, Apr 14, 2017 at 8:02 AM, Stefan Folkerts wrote: > Hi Bill, > > I don't know what is going on the the protect stgpool command vs

Re: TSM7.1.7 DB growing with Dedup

Hi Bill, I don't know what is going on the the protect stgpool command vs replicate node in regards to DB usage but the conversion growth...i've been there a few times before, it happens with every conversion because the directory containerpool stores it's metadata differently than the filepool.

TSM7.1.7 DB growing with Dedup

I converted a server over to directory container polls and replication. Their previous FILE stgpool was around 140TB of data. After defining everything I used the TSMOC dialogs to enable replication and then started running the CONVERT STGPOOL command. At the start of this I had 430GB of available