Agreed. The Exchange 2010 DAG cluster setup seems to be a brain damaged version of MSCS. We had to do the same thing – contact the DAG name via the public DAG name – essentially the cluster virtual
name. (Of course, in a firewalled environment this is painful.) Then, in the preferred server list for the DAG backup, we specified the names of the backup interfaces of the DAG servers. The initial communication and pre-processing occurs with the public DAG
name, but the backup data will go over the private backup network.
The DAG cluster is managed through the Exchange management tools, not through MSCS tools.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Lightner, Jeff
Sent: Wednesday, January 25, 2012 12:17 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Exchange 2010 DAG private backup network failover provision
My MS guy isn’t here but from my master’s hosts file I have comments that say:
Exchange DAG backup starts with DAG host name (DAG1, DAG2, DAG3 etc...) but
then dispatches to preferred node to do the actual data backup. It switches to other node if preferred isn't available.
So the DAG address (DAG1, DAG2, DAG3) is the 10.x non-private LAN but for the last DAG we added (DAG 3)
I created private LAN addresses in the 172.x range like the rest of our backup LAN IPs and it worked.
So if you had a 2 node DAG setup you might have entries for
DAG that had a single IP for that DAG in the non-private network.
host1 that has a private network IP for the first (preferred) node.
host2 that has a private network IP for the second (preferred) node.
Not sure how that is configured on the MS side though.
I am curious if anyone has implemented backups for Exchange 2010 DAG over a private backup network.
If the Exchange setup were an ordinary cluster, we could create a cluster resource for the backup NIC and have it reregister on another server if the main server fails. On exchange 2010, I understand that the is no real cluster but only
a “pseudo”-cluster. I am at a loss as to how to handle this.
SunTrust Banks, Inc.
Live Solid. Bank Solid.
The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination
or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.
By replying to this e-mail, you consent to SunTrust's monitoring activities of all communication that occurs on SunTrust's systems.
SunTrust is a federally registered service mark of SunTrust Banks, Inc. Live Solid. Bank Solid. is a service mark of SunTrust Banks, Inc.
Created for the Cause™
Making a Difference in the Fight Against Breast Cancer
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information
is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.