Hi Robert,

- You may want to upgrade to DP/Exchange 7.1.1 released last month.
  It adds some nice enhancements when it comes to DAGs.

- There is a new section in the User's Guide with 
  pictures and details with it comes to DAGs. Read the
  "Database Availability Group (DAG) backups" 
  section here:

   
http://www-01.ibm.com/support/knowledgecenter/SSTG2D_7.1.1/com.ibm.itsm.mail.exc.doc/c_dpfcm_bup_replica_exc.html?lang=en


- I also encourage you to read the section titled,
  "Database Availability Group backup guidelines":

   
http://www-01.ibm.com/support/knowledgecenter/SSTG2D_7.1.1/com.ibm.itsm.mail.exc.doc/c_dpe_bup_dag.html?lang=en


As far as your question about filling up the log...
try to schedule your INCREMENTAL backups frequently enough
to never let that happen. If it does, you should try to run
a backup to clear the space, but it's possible that 
the Exchange server won't let you do anything until
you clear some space first.


Thank you,

Del

=======================================================

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/12/2014 
03:12:40 AM:

> From: Robert Ouzen <rouzen AT UNIV.HAIFA.AC DOT IL>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 10/12/2014 03:13 AM
> Subject: Exchange DAG question
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> Hi to all
> 
> I have an environment for my Exchange as:
> 
> 
> ·         2 servers with exchange 2010
> 
> ·         O.S Windows 2008R2 64B
> 
> ·         TSM client version  7.1.1
> 
> ·         TSM TDP for exchange version  7.1.0
> 
> ·         TSM server version 7.1.1
> 
> I backup those exchange server with DAG configuration  ( only one 
> filesystem) with the configuration of proxy as:
> 
> Target Node         Agent Node
> ---------------     ---------------------------------------------
> EXCHSRVAN_DB        EXCHSRVA
> EXCHSRVBN_DB        EXCHSRVB
> DAG_EXCHANGE        EXCHSRVA EXCHSRVAN_DB EXCHSRVB EXCHSRVBN_DB
> 
> All the databases’ are configure on each server as half active and 
> passive and vice versa.
> 
> I run every day 3 logs backups and one a week a full backup for each
> server with those commands:
> 
> Logs:
> 
> start /B tdpexcc backup * incr /MIN=60  /EXCLUDEDAGPASsive /
> SKIPINTEGRITYCHECK /tsmoptfile=dsm.opt  /DAGNODE=DAG_EXCHANGE  /
> logfile=excsch.log >> excincr.log
> 
> Full:
> 
> start /B tdpexcc backup * full /MIN=60 /EXCLUDEDAGPASsive /
> SKIPINTEGRITYCHECK /tsmoptfile=dsm.opt  /DAGNODE=DAG_EXCHANGE   /
> logfile=excsch.log >> excfull.log
> 
> 
> I understand via documentation that  DP/Exchange does not actually 
> truncate the logs, the Exchange Server does the actual truncation.
> 
> When a DP/Exchange backup completes successfully, it will tell the 
> Exchange Server that it has stored the backup and that it can 
> truncate the logs.
> 
> At that point, the Exchange Server decides on the appropriate time 
> to truncate the logs.
> 
> 
> 
> So if one or more of my DB log  got full I need first to increase 
> the space on each server  and only after it to run a log or full 
> backup of this specific DB  to clean the logs?
> 
> 
> 
> It’s a parameter /PREFERDAGPAS that I don’t quite understand the 
> purpose and if I need it on the commands ? Any other suggestions 
> will be appreciate too.
> 
> 
> 
> Best Regards
> 
> 
> 
> Robert Ouzen
>