Creating a CAS Array on 2 Exchange Servers with DAG

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Hi Tony

Thanks, much clearer.

I have the full VMWare but no shared storage at the moment (it's coming) so HA/FT is not possible right now.

I created the DAG partially for "experience" and partially for mailbox redundancy against failures.

I think I'll wait til the SAN is here (was going to use VSA but the space limitations are far too great right now) and do the single CAS on FT.

Thanks

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Which part of the answer is wrong?

>Simply you cannot create a CAS array without putting in two new Exchange servers.

DAGs and CAS arrays cannot exist on the same server. DAGs use aspects of Windows Clustering and this cannot run on the same server as NLB.<

This part, a CAS array has nothing to do with windows load balancing. a CAS array can be created on the 2 servers with any of the above stated scenarios

The fact that windows clustering and windows NLB does't coexist doesn't mean the OP can't create a CAS array or use a dedicated load balancer to balance his cas server without adding 2 new exchange servers

ASKER

Load Balancing is not a requirement, simply a nice to have feature. Automatic Failover is much more important to me.

Hardware LB is NOT an option.

So where does that now leave me? Point 3, "Create a CAS Array but point it to the DAG IP"?

Ok fair comment - however I read it as how to install a CAS array on the existing setup without additional hardware, so not wrong - just differences of interpretation.

I would go with what I originally said. VMware do now support HA for Exchange (including MBX servers). They have a support statement somewhere on their website from about a year ago.

I would use what you've already paid for and let VMware do the HA. No added complexity or licensing.

You could create an additional CAS (only) server if you're nervous about HA'ing a DAG partner.

That is - CAS (only) _virtual_ server...

ASKER

SAN is about 6-7 months away yet I think, but for the sake of my own knowledge:

With my current setup, I could create a CAS array on my existing 2 Exchange Servers that both hold all roles, but instead of using Windows NLB I could just point it to the DAG IP to achieve automatic failover, at the expense of no Load Balancing.

Is this correct?

@Tony1044 I have been here long enough to know you and I do know you are a valuable addition to the community, believe me I am not trying to put any pun on you and I am sorry if you got my comment wrongly

just for info starting SP1 exchange MBX DAG on virtual high available environment is now supported on both VMWare and HyperV

I have no idea myself about vmware or FTlockstep so I cannot talk about this part but I would go for the option of pointing to the cluster IP since I would need no extra servers to install or anything.

again I am a total ignorant if VMWare so take my decision with a grain of salt

>>With my current setup, I could create a CAS array on my existing 2 Exchange Servers that both hold all roles, but instead of using Windows NLB I could just point it to the DAG IP to achieve automatic failover, at the expense of no Load Balancing.<<

that is exactly what I would have done if load balancing is not curcial

ASKER

Cool.

So how do create the CAS Array :D All the guides out there dont vary much from the "default" scenario

ASKER

Running SP1 btw!

@Akhater - no offence was taken at all. No 'peeved' tone was intended in my response. I value a two way flow of information.

FYI I'm not disagreeing with any point you made, just clarifying how I read the initial question.

New-ClientAccessArray -name CAS01 -FQDN CAS01.domain.local -site "ADSiteName"

that's it nothing more to do, just make sure to change the RpcClientAccessServer to CAS01.domain.local

get-mailboxdatabase | set-mailboxdatabase -RpcClientAccessServer CAS01.domain.local

@Tony1044 thank you

ASKER

>New-ClientAccessArray -name CAS01 -FQDN CAS01.domain.local -site "ADSiteName"

that's it nothing more to do, just make sure to change the RpcClientAccessServer to CAS01.domain.local

get-mailboxdatabase | set-mailboxdatabase -RpcClientAccessServer CAS01.domain.local<

Sorry I'm a bit dumb.

Do I need to run this on both servers or just any one of them?

Also, how does this affect external (Outlook Anywhere) connected clients?

I assume I need to create a DNS entry: CAS01.domain.local > DAG IP?

>>Sorry I'm a bit dumb.

Not at all we are all here to learn

>>Do I need to run this on both servers or just any one of them?
Any of them

>>Also, how does this affect external (Outlook Anywhere) connected clients?
It will affect all your outlook clients, outlook is using the new CAS array as rpc server

>>I assume I need to create a DNS entry: CAS01.domain.local > DAG IP?
perfectly right

Just one thing you should be aware of, if you have clients already configured with outlook these will not switch (unfortunately) to the cas array name automatically

ASKER

Thanks.

Do I need to set any external DNS in reference to the new CAS Array name? Or is that resolved through the RPC Proxy settings in Outlook?

When you say Outlook Clients will not automatically switch, do you mean I need to reconfigure them as follows:

Instead of having ExchangeServer1.domain.local in the SERVER field, I should have CasArray1.domain.local instead?

ASKER

If I create a CAS Array (casarray1.domain.local) will clients still be able to connect to ExchangeServer1 directly, if I have not reconfigured them yet?

ASKER

I ask as I have some remote users which I may not be able to get to them all immediately

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial