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

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.

By: SAT

SAT — Tue, 22 Jun 2010 02:40:04 +0000

Is the statement above regarding the deployment of VMs from a template the accepted situation or not? We have the same error adding second DAG members in the setup logs. Would appreciate feedback

Thanks
S

By: Exchange 2010 DAG Implementation « More Coffee Anyone?

Exchange 2010 DAG Implementation « More Coffee Anyone? — Mon, 29 Mar 2010 17:46:02 +0000

[...] good one already exists over at Shudnow’s Blog. Please see his 4 part series called “Exchange 2010 RTM DAG using Server 2008 R2″. You won’t regret it. I will update this post as I find issues with DAG that is not addressed [...]

By: dkroep

dkroep — Tue, 09 Mar 2010 14:41:21 +0000

I think I get it now. The FSW is mainly used to get a majority i thought the replication was also a part of the FSW's job. (Explains the resource question) But the replication NIC takes care of that. So when it goes down you still have 2 nodes replicating which can both have mounted databases in use. But when the FSW is down you can't get a 2/3 majority and that could cause split brain if something happens to the replication NiC.

Thanks for your time you've helped a lot.

By: Elan Shudnow

Elan Shudnow — Mon, 08 Mar 2010 17:01:12 +0000

Nothing really happens if the FSW goes down if you still have majority. Majority is 50% + 1. So if you have 2 DAG Nodes and 1 FSW, if your FSW goes down, you still have 2 nodes up so you still have majority. Just bring back up the server that has the FSW and all is well. The FSW doesn't take up much space at all. It's nothing you have to plan for. It's probably only a few MB in size (I'd have to check our server). The FSW takes up no real resources at all, nothing you would have to account for.

If for some reason, your FSW server dies, just set the Set-DatabaseAvailabilityGroup cmd to create a new FSW on a different server.

By: dkroep

dkroep — Mon, 08 Mar 2010 15:28:14 +0000

First of all thanks for the article Elan really nice.
I am going to install the FSW on a server outside of a 2 noded DAG like you did but what happens when the FSW server goes down?
Is it easy to recover?
How much HD space is required for the FSW?
Does the FSW take a lot of the server's resources?

By: brant

brant — Thu, 07 Jan 2010 15:32:37 +0000

Hi~~
Do you know how to disable Client Throttling in EXCHANGE 2010?
Thank you

By: Shijas

Shijas — Thu, 07 Jan 2010 07:31:09 +0000

Dear All..

I have Managed to Install Exchange 2010 on my Exchange 2007 Organisation, I am unable to move the mailboxes to the 2010. it says you don’t have permission. also i have created a test user on 2010- mails from 2007 to 2010 is flowing but i am unable to send mails from 2010 to 2007..

Shijas