Also : >>32 cores, 256 GB RAM, DB and activelog on SSD.
Wow, that's pretty serieus. Also, if I might ask, what is your daily backup/archive ingest, how much data do you manage and what type of disk (system/config) do you use for your filepool storage? On Wed, Jul 2, 2014 at 12:58 PM, Bent Christensen <[email protected]> wrote: > Hi all, > > I remember noticing that there were some dedup housekeeping (removal of > dereferenced chunks) issues with TSM Server 6.3.4.200 and that a fix was > released. We used 6.3.4.200 for a while as stepping stone on our road from > 5.5 to 7.1 but without the fix. > > Now, on 7.1, I am seeing some stuff that makes me worry a bit - initiated > by a gut feeling that there are more data in my dedup pool than there > should be. > > SHOW DEDUPDELETEINFO shows that I have +30M chunks waiting in queue and > the number is increasing. It also shows that I right now have 8 active > worker threads with a total of 5.8M queued, but only approx. 4000 > chunks/hour get deleted. > > Any knowing if these numbers make sense? > > We use a full-blown TSM server on Windows, 32 cores, 256 GB RAM, DB and > activelog on SSD. > > - Bent >
