Re: [ADSM-L] Exchange 2010 backup and restore in DAG configuration
Regarding using "asnode" (mentioned by Stefan) ... I see page 10 of the DP for
Exchange install guide says: "Do not set the ASNODENAME option in the dsm.opt
file when using DP or Exchange. Setting ASNODENAME can cause VSS backups and
VSS restores to fail.
State of Kansas - Department of Administration - Office of Information
Harold.Vandeventer AT da.ks DOT gov
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Tuesday, March 13, 2012 6:11 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Exchange 2010 backup and restore in DAG configuration
As you pointed out, if you back up from different servers, the backups
are managed separately. This is why the User's Guide states that the
best practice is to back up from the same server every time.
It is a known requirement that it would be better if DP/Exchange
could back them up from anywhere and manage them as a single entity
on the TSM Server. If you are really interested in this aspect,
please have your IBM rep send Mary Anne Filosa (IBM TSM Beta Coordinator)
an email. There is a beta program that you might want to be a part of.
Until then, there are customers that use the same DP/Exchange
NODENAME on all of their Exchange Server to help mitigate
some of the issues if you back them up from different Exchange servers.
It does not solve the problem completely, but it does back them up
under the same NODENAME.
Again, the best practice as quoted from the book:
"Backups for a given database should be run from the
same Exchange server, if possible. Backups performed from
different Exchange servers are managed separately."
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 03/13/2012
> From: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 03/13/2012 04:50 AM
> Subject: Exchange 2010 backup and restore in DAG configuration
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> Hello all,
> I am working with a customer who has an Microsoft Exchange 2010 DAG
> and wants to implement TSM backup for mail.
> DAG uses active and passive databases and, of course, the customer only
> wants to backup the passive databases (replica's).
> Each database has two passive copy's for redundancy.
> Each Exchange server has it's own node on the TSM server the passive /
> active database float around the Exchange cluster and thus the node that
> makes the backup changes.
> This makes restores a bit of an issue because the data is spread amongs
> multiple TSM nodes, we also have our doubts about the expiration of data
> with this configuration.
> We currently run ;
> tdpexcc backup * full /tsmoptfile="D:\Program
> Files\Tivoli\TSM\TDPExchange\dsm.opt" /EXCLUDEDAGACTIVE
> /configfile="D:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.cfg"
> The documentation doesn't give much information rather than (PDF
> Acrobat page 34/35.
> Can we, like we do with VMware use 'asnode' or something similar to
> the backup data in a single nodename or are there any other clever
> supported tricks?