Hi Wanda, I have a few ideas for you...
-------------------------- Are you running in a DAG environment? If so, you could do some load balancing between DAG Servers: Most of this in the Exchange book under "Managing Exchange Database Availability Group members by using a single policy": http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/index.jsp?topic=%2Fcom.ibm.itsm.mail.exc.doc%2Ft_dpfcm_bup_reduce_redundant_exc.html The key to "load balance" when setting up the scheduled backup script is to have a separate invocation of each database. For example: TDPEXCC BACKUP DB1 FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE TDPEXCC BACKUP DB2 FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE TDPEXCC BACKUP DB3 FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE TDPEXCC BACKUP DB4 FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE TDPEXCC BACKUP DB5 FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE Then, run this command from each of the Exchange servers at or about the same time. -------------------------- Here are a few more things to look at: To help with some performance issues, some customers have split their backups into multiple "threads" or "processes" in two ways: 1. Increase the value of the RESOURCEUTILIZATION parameter in the DSM.OPT file for the DSMAGENT. Trying setting this to "10". Important: This needs to the DSM.OPT file for the DSMAGENT not the DP/Exchange options file. 2. Split the backups into multiple parallel instances of the TDPEXCC backup execution. i.e. the create separate invocations of DP/Exchange that back up a different set of databases. For example: TDPEXCC BACKUP db1,db2,db3,db4 FULL TDPEXCC BACKUP db5,db6,db7,db8 FULL TDPEXCC BACKUP db9,db10,db11,db12 FULL Put these in separate command files and stagger the launching of them by 10 minutes or so. The key here is that you need to make sure that you don't have any LUNs that appears in more than one invocation. In other words, you don't want to snapshot the same LUN in separate invocations. Note: The integrity check is a Microsoft tool. IBM has no control over the speed of that tool. DP/Exchange invokes the Microsoft ESEUTIL program to perform the integrity check. It's a very I/O intensive program that must examine every page of the database file (.EDB) and all log files. -------------------------- If none of these help, you should open a PMR to get the performance team to look at your environment. Thank you, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 02/07/2014 06:04:01 PM: > From: "Prather, Wanda" <wanda.prat...@icfi.com> > To: ADSM-L@vm.marist.edu, > Date: 02/07/2014 06:06 PM > Subject: Exchange 2010 backup performance > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > Are Exchange 2010 VSS backups affected by TXNBYTELIMIT settings in > the baclient dsm.opt? > Or is there anything else I can tweak to improve TSM throughput of a > 2010 full backup? > Got a 10G network, but Exchange full backup performance not impressive. > > Thanks for any ideas - links to relevant doc also appreciated! > > Wanda > > > **Please note new office phone: > Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | > www.icfi.com<http://www.icfi.com> | 410-868-4872 (m) > ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md > |443-718-4900 (o) >
