According to the 7.1 blueprint you are a large deployment (for server side 
dedupe)

CPU: 16 core Power 8
Memory: 192GB
Directory for the active log: 300 GB
Directory for the archive log:4 TB

It was suggested to use that we make sure that these logs are all on SSD/flash 
for ideal performance.  We are just now trying to increase all of our files 
systems to jump into container pools in the very near future but we are on the 
larger size of a medium deployment.

That said, I've identified the risk of using less hardware than the blueprint 
suggests.  Time will tell if upgrading the server and all the SSD required, 
will end up saving money compared to a dedicated dedupe storage device.

---------------------------------------------------
David Nixon
System Programmer II
Technology Services Group
Carilion Clinic
451 Kimball Ave.
Roanoke, VA 24015
Phone: 540-224-3903
cdnixon AT carilionclinic DOT org

Our mission: Improve the health of the communities we serve.



________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] on behalf of Stef 
Coene [stef.coene AT DOCUM DOT ORG]
Sent: Thursday, December 10, 2015 5:02 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM troubles

Hi,

Some time ago I mailed in frustration that using DB2 as TSM backend was a bad
idea.

Well, here I'm again with the same frustration.

This time I just want to know who is using deduplication successful?
How much data do you process daily? Client or server or mixed?

We are trying to process a daily intake between 10 - 40 TB, almost all file
level backup. The TSM server is running on AIX, 6 x Power7, 128 GB ram. Disk
is on SVC with FlashSystem 840. Diskpool is 250 TB on 2 x V7000 with 1 TB
NLSAS disks, SAN attached. We are trying to do client based dedup.

The problem is that the active log fills up (128 GB) in a few hours. And this
up to 2 times per day! DB2 recovery takes 4 hours because we have to do a
'db2stop force' :(


Stef

________________________________

Notice: The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. Carilion Clinic 
shall not be liable for the improper and/or incomplete transmission of the 
information contained in this communication or for any delay in its receipt.