1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

TDP for Exchange 6.3 client SPEED ISSUES! (SLOW!!)

Discussion in 'TSM Client' started by rbnllobertk, Oct 15, 2012.

  1. rbnllobertk

    rbnllobertk New Member

    Joined:
    Nov 16, 2011
    Messages:
    24
    Likes Received:
    0
    We've recently introduced a number of WIN2k8(r2) servers running Exchange2k10 into our TSM environment. They're running the TDP6.3 client. This is the first time we've had to use this "newer" client version, utilizing the VSS backup and such. Since we started using this newer version of TDP our backups are running a LOT slower than they should, and definitely a LOT slower than they did on the v5.5 TDP client. Any thoughts? Anything we can do to the dsm.sys? Its becoming a serious issue in our environment as we're running out of enough hours in the day to get them backed up! thanks in advance! -Robert
     
  2.  
  3. ja954

    ja954 New Member

    Joined:
    Oct 18, 2002
    Messages:
    52
    Likes Received:
    0
    Occupation:
    TSM Administrator
    Location:
    Boston
    We see a performance hit when the Exchange integrity check runs before the backup. Every third party backup vendor is suggested to run this check as it reads every page of the Exchange data store to insure data is good for a backup. You can skip this check with the /SKIPINTEGERITYCHECK option. This is not recomended by Microsoft.
    You may not be having the same issue but in general we see the actual backups (data flowing to the TSM server) running faster then with pervious versions.
    Currently our command for doing a backup looks like this:
    tdpexcc back DB022,DB043,DB064,DB085,DB121 full /EXCLUDEDAGACT /SKIPINTEGRITYCHECK /LOGF=c:\tsm\logs\%cdate%\%cdate%_TDPEXC.LOG
     
  4. simonpie

    simonpie New Member

    Joined:
    Aug 20, 2014
    Messages:
    5
    Likes Received:
    0
  5. ja954

    ja954 New Member

    Joined:
    Oct 18, 2002
    Messages:
    52
    Likes Received:
    0
    Occupation:
    TSM Administrator
    Location:
    Boston
  6. simonpie

    simonpie New Member

    Joined:
    Aug 20, 2014
    Messages:
    5
    Likes Received:
    0
    Darn google which always bring me to obsolete pages for TSM. I cannot find the doc for 6.3, nor 6.4 which we have. But the doc for 7.1 seems to agree with you. Thanks, I will try it tonight anyway.
     
  7. BrianV

    BrianV New Member

    Joined:
    Dec 13, 2011
    Messages:
    83
    Likes Received:
    3
    Location:
    USA
    It's that damn ESEUTIL that Exchange uses. Microsoft will recommend skipping the integrity check as long as you have DAG's. You can also add the /PREFERDAGPASSIVE switch to exclude all passive copies.
     
  8. simonpie

    simonpie New Member

    Joined:
    Aug 20, 2014
    Messages:
    5
    Likes Received:
    0
    Hi, we have the preferdagpassive switch. We tried the skipintegrety check switch but the backup still takes 9 hours for about 1.3 TB. Something is clearly wrong. Any idea what I could investigate ?

    Here is the command we run
    Here is the output of tdpexcc q tdp

     
  9. BrianV

    BrianV New Member

    Joined:
    Dec 13, 2011
    Messages:
    83
    Likes Received:
    3
    Location:
    USA
    Well, the fact that this started happening when you installed 6.3 is strange. We moved from 6.1 to 6.4 and didn't encounter performance issues and didn't have to make any changes to our script or add any additional options. Have you opened a ticket with support?

    In the meantime, how many mount points have you allowed on the Exchange node, DAG node, and local dsmagent node? Also, what do you have as your RESOURCEUTILIZATION in the dsm.opt of the local dsmagent node?
     
  10. simonpie

    simonpie New Member

    Joined:
    Aug 20, 2014
    Messages:
    5
    Likes Received:
    0
    The problem did not happened when we installed 6.3. It just happened gradually as we started migrating exchange 2003 to 2010.
    We have nothing for resourceutilization, but I was planning trying a fairly high value tonight, probably 10 as this is a fairly powerful machine.

    The maximum mount point is 1, but we do our backup to disk and then destage to tape.
     
  11. Tiger22

    Tiger22 Member

    Joined:
    Jan 28, 2008
    Messages:
    166
    Likes Received:
    11
    Occupation:
    IT Consultant
    Location:
    London, UK
    Are you running your new Exchange servers within a clustered environment?
     
  12. simonpie

    simonpie New Member

    Joined:
    Aug 20, 2014
    Messages:
    5
    Likes Received:
    0
    Its a DAG. I have tried the RessourceUtilisation parameter (value of 10). No change, still almost 10hours. Most parameters are set to default parameters.

    dsm.opt for baclients :

    dsm.opt for tdpe
    and some basic server settings :

    There are way under 200 sessions most of the time. At peak hour, the server will receiver 750 GB per hour (for about one hour). Yet this backup will take around 10 hours for 625 GB.
     

Share This Page