Hi Wanda, This is what gives you the "load balancing" for backups when you have multiple Exchange servers that are working together to perform a backup on a set up DAG databases. By having separate invocations, each of the Exchange servers will perform a backup of a database, then move on to the next one, checking to see if a backup has been performed within the "minimumbackupinterval", if it has, it is skipped, if not, it backs it up.
Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 11/10/2014 10:46:49 PM: > From: "Prather, Wanda" <wanda.prat...@icfi.com> > To: ADSM-L@VM.MARIST.EDU > Date: 11/10/2014 10:48 PM > Subject: Re: exchange 2010 > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > Del, > Can you elaborate a little more? > How is the separate invocation as you showed below different from doing > TDPEXCC BACKUP * FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE > > ? > Thanks > Wanda > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Thursday, October 30, 2014 3:49 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] exchange 2010 > > Hi Remco, > > The PREFERDAGPASSIVE tells DP/Exchange to only back up an active > database if there are no current healthy passive copies of the > database. If no healthy passive copy is available, the backup is > made from the active copy. > > Most of the DAG backup best practices and methodology is in the > Exchange book under "Database Availability Group (DAG) backups": > > > 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 > > > 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. > > > > Del > > ---------------------------------------------------- > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 10/30/2014 > 02:42:01 PM: > > > From: Remco Post <r.p...@plcs.nl> > > To: ADSM-L@VM.MARIST.EDU > > Date: 10/30/2014 02:42 PM > > Subject: exchange 2010 > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > Hi All, > > > > we're sort of struggling to get the full backups of our exchange > > environment completed. The good news is that the mail admins have > > decided to split the exchange env. into many small databases, so I was > > thinking to create a script that backups a number of databases full > > and the rest incrementally and rotating the selection of databases to > > be backed up fully each day. > > > > I was just wondering about the preferdagpassive parameter. If I say > > 'backup db1,db2,db3,db4 full /preferdagpasive' and db3 and db4 are > > active databases on this DAG node, will they or will they not be > > backed up? In other words, is there a difference in handling for * vs. > > explicitly naming the databases to be backed up? > > > > (of course I'll run the exact same command on the other DAG node at > > more or less the same time to backup those databases that are passive > > over there). > > > > -- > > > > Met vriendelijke groeten/Kind Regards, > > > > Remco Post > > r.p...@plcs.nl > > +31 6 248 21 622 > > >
