c.j.hund
ADSM.ORG Senior Member
Hello all,
I have a 2010 Exchange clustered environment I'm about to configure. Both the TDP and baclient are at version 6.4.*. The TSM server is at version 6.3. This is an active/passive cluster.
This is the first clustered 2010 TDP configuration I've done. I was wondering how others have set up the cluster to manage the TSM CAD for the DAG node? There's no clustered drive or quorum drive any longer, so how have you set up Failover Cluster Manager to manage that service?
I asked this of a peer earlier today and was told that the best way to manage this is to not have the cluster manager manage the service at all, but rather have local CADs on either side of the cluster running the same backup .cmd files out of separate schedules on the TSM server. Whichever side of the cluster starts first will start the backup, and the other side will fail when attempting to start its backup. Is that the best, or even only, way to manage a clustered CAD in Exchange 2010? Maybe what I need is a shared drive for the dsm.opt and log files? At the moment, there is no "cluster" drive which would fail back and forth to the active side of the cluster, and I'm really not sure if that's standard now in 2010 Exchange.
Has anyone else set up a clustered 2010 Exchange environment, and if so, how did you manage the CAD for the DAG node?
Sincere thanks,
C.J.
I have a 2010 Exchange clustered environment I'm about to configure. Both the TDP and baclient are at version 6.4.*. The TSM server is at version 6.3. This is an active/passive cluster.
This is the first clustered 2010 TDP configuration I've done. I was wondering how others have set up the cluster to manage the TSM CAD for the DAG node? There's no clustered drive or quorum drive any longer, so how have you set up Failover Cluster Manager to manage that service?
I asked this of a peer earlier today and was told that the best way to manage this is to not have the cluster manager manage the service at all, but rather have local CADs on either side of the cluster running the same backup .cmd files out of separate schedules on the TSM server. Whichever side of the cluster starts first will start the backup, and the other side will fail when attempting to start its backup. Is that the best, or even only, way to manage a clustered CAD in Exchange 2010? Maybe what I need is a shared drive for the dsm.opt and log files? At the moment, there is no "cluster" drive which would fail back and forth to the active side of the cluster, and I'm really not sure if that's standard now in 2010 Exchange.
Has anyone else set up a clustered 2010 Exchange environment, and if so, how did you manage the CAD for the DAG node?
Sincere thanks,
C.J.