Comments on: Exchange 2010 RTM DAG using Server 2008 R2 – Part 1

By: g0b3ars

g0b3ars — Mon, 04 Apr 2011 15:26:35 +0000

Enterprise edition of either flavor of Windows is required, since DAGs use cluster components which are only available when running enterprise… The Exchange license itself can be standard, however.

By: Carl

Carl — Mon, 04 Apr 2011 12:27:53 +0000

Nice guide :)

A quick question. Do any of the servers running the nodes need to be enterprise edition?

A technet article says;
If you're installing the Mailbox server role and you intend the server to be a member of a database availability group (DAG), you must be running the Enterprise Edition of Windows Server 2008 or Windows Server 2008 R2. The Standard Edition doesn't support the features needed for DAGs. You can't upgrade Windows when Exchange is installed on the server.

Does this mean;

"Enterprise Edition of Windows Server 2008" or "Any version of Windows Server 2008 R2"

"Enterprise Edition of Windows Server 2008" or "Enterprise Edition of Windows Server 2008 R2.

I think it's a bit ambiguious.

By: Jonathan

Jonathan — Fri, 25 Feb 2011 22:19:30 +0000

Niroshan,

What was the resolution to this issue? Somehow it is happening to my setup.

There is a error as (The Cluster Network Name is not online)
I am Using Server 2008 R2 Hyper V

Event Ids
1205
1069
1240

Thanks
Jonathan

By: g0b3ars

g0b3ars — Tue, 22 Feb 2011 07:26:24 +0000

You can distribute the load however you see fit – if you have significantly faster storage on node1 you could keep all DBs active there and rely on node2 only for a failover event, but given similar performance characteristics it is nice to spread the load evenly between the two to get the highest performance…

By: @abimons

@abimons — Tue, 22 Feb 2011 06:57:47 +0000

Hi team, in the lab architecture i could see that some active databse on NODE1 and some on NODE2, what is the possibilty of keeping all active database on NODE1 and paassive db's on NODE2 , Does it make any sense on increasing i/o rates in NODE1, please calrify it ?

By: Elan Shudnow

Elan Shudnow — Wed, 25 Aug 2010 14:10:31 +0000

Don't put it on a DC. The reason I didn't is because in order for Exchange to manage the FSW on a non-Exchange Server, you must put the Exchange Trusted Subsystem Group in AD inside that machine's Administrator's group. Because a DC doesn't have the SAM database anymore, in order to do this, you would have to nest the Exchange Trusted Subsystem inside the Domain's Administrator group which is a security issue. I would place it on an Exchange Server outside of the DAG or a member server, but not a DC.

By: satish

satish — Wed, 25 Aug 2010 12:11:36 +0000

can anyone plz confirm wer to have fsw either on dc or hub& cas or in a separate member server

By: eshudnow

eshudnow — Mon, 12 Jul 2010 11:45:19 +0000

No, it's just a file share so there's no real requirements other than it being a Windows Box. If you're putting the FSW on a non-Exchange box, make sure you add the Exchange Trusted Subsystem group into the Local Administrators group of that Windows Server to ensure that Exchange can remotely manage the FSW.

By: Ferry Kho

Ferry Kho — Mon, 12 Jul 2010 07:04:14 +0000

Hi Elan

Does the FWS have to be a Ent version of Windows Server running Failover Cluster Service?

Regards,
-ferry-

By: Andrew Suthanah

Andrew Suthanah — Wed, 23 Jun 2010 19:59:00 +0000

Hi there,

I have read Mark Russinovic's article about machine SIDs and he obviously knowa a lot more about the subject than I do but… The other day (in a lab) I was trying to create a forest trust where all the DCs had been deployed from the same VM template and had the same SID. This flatly failed every time. Once I ran NewSID on one machine I could create the trust, so there is definately something going on with duplicate SIDs.