No, they tried VM's once and the performance was poor. They had to switch back to physical servers which have 4 cores (32 processors) and 384GB of ram each.
On Sun, Feb 18, 2018 at 10:37 AM, Stefan Folkerts <stefan.folke...@gmail.com > wrote: > Hi Tom, are the Exchange servers virtualized on vSphere? > > On Sat, Feb 17, 2018 at 12:55 AM, Tom Alverson <tom.alver...@gmail.com> > wrote: > > > > > > > > > > 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 > > >
