Tom,

I don't have a large on-premises Exchange environment.  I perform full backups 
daily and log backups hourly.  Things you could test to improve speed:
- test RESOURCEUTILIZATION option in dsm.opt to at least 5 (10 is max, I think) 
to see how it performs in your environment and adjust up or down as needed
- test dsm.opt settings TCPBUFFSIZE to 512, TCPWINDOWSIZE to 63, and 
TXNBYTELIMIT to 25600 and modify them to see what works best in your environment

You could test turning off error checking for the exchange backups.  If you do, 
I strongly recommend testing a restore "occasionally".
You don't need PowerShell to automate your Exchange backups.  You can, as it 
appears you already have, use batch files and tdpexcc.exe to do your backups.  
As someone else already pointed out, VSS will abort multiple simultaneous 
backups; so, stagger them by at least ten minutes (+/-)--it really depends on 
how long it takes for Windows to complete the snapshot in your environment.

Good luck!

Ray
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tom Alverson
Sent: Friday, February 16, 2018 6:56 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Exchange backup speed

>
>
> We are trying to speed up our Exchange backups that are currently only
using about 15% of the network bandwidth.  Our servers are running Windows
2012R2 and Exchange 2013 CU15 with TSM 7.1.0.1 and TDPEXC 7.1.0.1.
Currently we are backing up 15 DAGS per Exchange server (we have multiple 
exchange servers) and we are only backing up on servers that are standby 
replicas.  Currently we are trying a 14 day schedule were we do a full backup 
of a different DAG per day, and incrementals on the rest.  Even doing this we 
are having trouble completing them in 24 hours (before the next day's backup is 
supposed to start).

I saw an old posting from Del saying to increase RESOURCEUTILIZATION on the 
DSMAGENT.  Does that mean the DSM.OPT in the BACLIENT folder?  It was set at 2. 
 Do either the buffers or buffrsize options make any difference?

Also if we want to "parallelize" the backups does that mean separate scheduler 
services for each one?  We currently use 14 different batch files (for the 14 
days of the cycle) with something like this:

[day1.bat]

tdpexcc.exe backup dag1 full
tdpexcc.exe backup dag2,dag3,dag4,dag5 incr tdpexcc.exe backup 
dag6,dag7,dag8,dag9 incr tdpexcc.exe backup dag10,dag11,dag12,dag13 incr 
tcpexcc.exe backup dag14,dag15 incr exit

________________________________

CONFIDENTIALITY NOTICE: This email and any attachments are for the
exclusive and confidential use of the intended recipient. If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.