You're welcome. To elaborate a little, the way they 'coordinate' the backup between the dag nodes is by using the option 'MINIMUMBACKUPINTERVAL' with a single backup schedule, databases are marked on the exchange level when a backup is active so this prevents a schedule that gets picked up a few minutes later on another node from backing up a database again.
On Tue, Nov 20, 2012 at 4:51 AM, Prather, Wanda <wanda.prat...@icfi.com>wrote: > Outstanding! Thanks for the post. > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Stefan Folkerts > Sent: Monday, November 19, 2012 11:13 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Exchange 2010, DAGs, and Proxies? (oh my...) > > I might be one of the first here to implement this in a dag cluster at a > customer site today, I can report that it is easy to setup and it runs fine > with the 6.4 TSM BA client. > > This feature "Back up DAG databases to a common node." is nice and works > fine with the testing I have done so far. > This feature "Coordinate backups between DAG members so only one copy is > backed up per backup cycle." is true but "coordinate" is a funny choice of > words. > :-) > > > > On Thu, Nov 15, 2012 at 4:23 PM, Bill Mansfield < > bill.mansfi...@us.logicalis.com> wrote: > > > Wanda, it looks like this is fixed in the TSM 6.4 TDP-E. This is from > > the IUG. > > > > You can back up Exchange Server Database Availability Group (DAG) > > servers by using a common policy. By coordinating backups between DAG > > servers, you can prevent duplicate or redundant backups. The following > > features are available for DAG environments. > > > > - Back up DAG databases to a common node. The backups can be > > managed by a single policy regardless of which DAG member (server) > > performed the backup. > > > > - Coordinate backups between DAG members so only one copy is > backed > > up per backup cycle. > > > > - Reduce the load on the production Exchange server in a DAG by > > setting > > a preference for backing up a healthy passive database copy unless no > > healthy passive copy is available. If no healthy passive copy is > > available, the backup is taken from the active database copy. Whether > > the backup is taken from the active or the passive copy, the backup is > > managed as a single entity. > > > > Bill Mansfield > > Technical Consultant, Data/Storage Integrated Practice Logicalis, Inc. > > >
