Hi Tom,

My original posting was an excerpt from best practices for container 
pools, and does not necessarily apply to other storage pool types. 

Yes, client-side deduplication and compression options should be avoided 
with a Data Domain storage pool. 

A fixed resourceutilization setting of 2 may underperform for clients that 
have a lot of data to back up and fast network connections, but this is 
not a black and white answer. There are various other conditions that can 
affect this and trying to narrow in on them in ADSM-L would be difficult. 
If you want some help with a performance issue, please open a PMR.


Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/25/2017 
12:20:43 AM:

> From: Tom Alverson <tom.alverson AT GMAIL DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 03/25/2017 05:40 AM
> Subject: Re: Best Practices/Best Performance SP/TSM B/A Client Settings 
?
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> Del:
> 
> We have been using these settings as our defaults.  Is our TCPWINDOWSIZE
> too large?
> 
> RESOURCEUTILIZATION 2  (we increase this up to 10 for some WAN backups)
> TXNBYTELIMIT 2097152
> TCPNODELAY YES
> TCPBUFFSIZE 512
> TCPWINDOWSIZE 2048
> LARGECOMMBUFFERS YES
> 
> Also we never use compression because our storage folks believe it will
> foul up the de-duplication that happens on our Data Domains??
> 
> On Mon, Mar 20, 2017 at 9:11 PM, Del Hoobler <hoobler AT us.ibm DOT com> 
> wrote:
> 
> > Hi Ben,
> >
> > Here are some items to get you started:
> >
> >
> > Backup-Archive client with limited, high latency network (WAN 
backups):
> > ===============================
> > TCPWINDOWSIZE           512
> > RESOURCEUTILIZATION     4
> > COMPRESSION             Yes
> > DEDUPLICATION           Yes
> > ENABLEDEDUPCACHE        Yes
> >
> > Tip:  Do not use the client deduplication caching for applications 
that
> > use the IBM Spectrum Protect API.  Refer to section 1.2.3.2.1 for
> > additional details.
> >
> >
> > Backup/Archive client or Client API with limited network (Gigabit LAN
> > backups):
> > ===============================
> > TCPWINDOWSIZE           512
> > RESOURCEUTILIZATION     10
> > COMPRESSION             Yes
> > DEDUPLICATION           Yes
> > ENABLEDEDUPCACHE        No
> >
> >
> > Backup/Archive client or Client API with high speed network (10 
Gigabit +
> > LAN backups)
> > ===============================
> > TCPWINDOWSIZE           512
> > RESOURCEUTILIZATION     10
> > COMPRESSION             No
> > DEDUPLICATION           No
> > ENABLEDEDUPCACHE        No
> >
> >
> > Tip:  For optimal data reduction, avoid the following client option
> > combination:
> >
> > COMPRESSION     Yes
> > DEDUPLICATION   No
> >
> >
> >
> >
> > Del
> >
> > ----------------------------------------------------
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/15/2017
> > 02:39:04 PM:
> >
> > > From: "Alford, Ben" <balford AT UTK DOT EDU>
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Date: 03/15/2017 02:39 PM
> > > Subject: Best Practices/Best Performance SP/TSM B/A Client Settings 
?
> > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > >
> > > I've looked at the IBM Blueprint documents but may have missed what
> > > I was looking for - the Best Practices for Best Performance for TSM
> > > B/A client settings.    As we move from 6.4 to 7.x or 8.x clients
> > > before the 6.4 EOL, we are looking to test with the current client
> > > settings optimized for things like TCPBUFFSIZE, TCPWINDOWSIZE,
> > > TXNBYTLIMIT, etc., etc.
> > > Thanks!
> > >
> > > Ben Alford
> > > IT Manager, Office of Information Technology
> > > Systems: Shared Services
> > >
> > > The University of Tennessee
> > >
> >
>