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.

Exchange 2010 DAG node scheduling configuration

Discussion in 'Exchange / Outlook' started by lmcginutsw, Jul 27, 2010.

  1. lmcginutsw

    lmcginutsw New Member

    Jul 26, 2010
    Likes Received:
    We’re using TDP for Exchange 2010 and have successfully performed a manual full backup thanks to adsm.org forums. Now, we’re trying to figure out a scheduling strategy for DAG. Currently, there are 2 servers with a shared 8 databases ( shared 4 active, 4 passive on each ) for the DAG groups.

    Should we create a shared tdp node on the tsm server to receive backups from both server tdp clients at different times (similar to the virtual node on clusters), or should each server have a separate tdp node with passive backups ( using the /excludedagactive /excludedagpassive switches). The separate nodes concern us a bit because if one server dies then its mail database backups would start going to the alternate node. If later, the exchange admins needed to a restore a database from the failover window, they would have to know which tdp node held the data.

    There is discussion in the manual about scheduling legacy and cluster backups, but we could not find much pertaining to DAG.
  3. storagerocket

    storagerocket New Member

    Nov 30, 2010
    Likes Received:
    Hi Imcginutsw,

    how did you configure your TDP scheduling service?
  4. Mita201

    Mita201 Senior Member

    Apr 20, 2006
    Likes Received:
    System Engineer
    Beograd, Serbia
    You will probably like to check this:
    I will go with two separate nodes, and in case that you have described, I will temporarily present "live" node to TSM server as "dead" one, and will do restore.
    You can check trough GUI what backups one node "see" from TSM database.

Share This Page