Re: Ex2007 and Multiple Sites

Yes, Hub & CAS roles can co-exist on the same box.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"RdS" <RdS@xxxxxxxxxxxxx> wrote in message
news:uGgBOqMGHHA.2464@xxxxxxxxxxxxxxxxxxxxxxx
:(

Well what about combining the hub and client roles? I was planning to use
nlb on the client role servers for availability. If I combine the roles
on that server will that work? I only have the 4 servers and will not
have any more.

2 are enterprise and 2 are standard. the enterprise of course is the
mailbox servers.

thanks again.

"Bharat Suneja [MVP]" <bharatsuneja@xxxxxxxxxxx> wrote in message
news:eZAaPkMGHHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
The Clustered Mailbox Server role *does not co-exist* with any other
server role.
In other words, you need a separate Hub Transport server - you cannot
install it on an Exchange Server 2007 cluster node.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"RdS" <RdS@xxxxxxxxxxxxx> wrote in message
news:%232DTwgMGHHA.5104@xxxxxxxxxxxxxxxxxxxxxxx
ok. I believe the last question... :)

As I mentioned previously, the hub transfer and mailbox server roles
will be on the same server. Will I be able to still use CCR on the
mailbox servers with hub transfer role on same server? I know Exchange
handles availability for multiple hubs in an org so it doesn't need to
be clustered. But will CCR still work

Thanks.

"Bharat Suneja [MVP]" <bharatsuneja@xxxxxxxxxxx> wrote in message
news:%23lORkiLGHHA.1912@xxxxxxxxxxxxxxxxxxxxxxx
Yes, very small - so don't worry about performance or disk space
issues.
Haven't had a chance to observe the failure/failover behaviour with the
file share witness unavailable yet.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"RdS" <RdS@xxxxxxxxxxxxx> wrote in message
news:4B39C2A9-3BC3-420E-A768-0C21CF088DF4@xxxxxxxxxxxxxxxx
Will this file share be small? I really didn't want to share files on
my
CAS. What happens if the CAS that is the witness is unavailable
during a
failure. Will second server in cluster still come online?

Thanks.


"Bharat Suneja [MVP]" wrote:

You can locate the file share witness on any computer - including a
CAS -
all that's required is for the cluster to have access to that file
share. It
really comes into play only when the 2 cluster nodes cannot talk to
each
other but somehow are still available. In this case, the file share
witness
votes who should own the resources.

Together with the node that thinks it owns the resources, the file
share
witness forms a majority (of 2) - and therefore the name MNS.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"rJ" <RdS@xxxxxxxxxxxxx> wrote in message
news:D7D7EFCB-4FFC-4C7E-9F20-7C2FEE38ACA9@xxxxxxxxxxxxxxxx
Thanks so much Dave.

One further question...
right now I have two mailbox servers and two client access servers.
I see
that MS recommends the witness be on a hub transport server. But
how I
have
it configured and will in production environment is as followis:

Data Center 1:
exch1
- Mailbox server
- Hub Transport Server

exch2
- Client Access Server

Data Center 2:
exch3
- Mailbox server
- Hub Transport Server

exch4
- Client Access Server

The reason I want to be sure I have two CAS is because of the
autodiscover
service. If one data center becomes inaccessible or the other CAS
dies I
still need my Outlook 07 clients to know how to find their
mailboxes. I
only
will have 4 total Exch boxes so the only witness can be the CAS.
What
happens if the witness dies? How does the cluster still function?

Can I not put the witness on on of my client access servers?

Thanks again. much appreciated.

"daveberm" wrote:

In addition, as Bharat has already mentioned, if you already have
2
Exchange 2007 mailbox servers configured, you will need to build a
new
Exchange CCR cluster on different servers and move the mailboxes
to
this clustered Exchange server. Hopefully this is a POC in your
lab,
not production - right? And yes, your standby server will be
sitting
there doing nothing until it is called into service.

Dave

David A. Bermingham, MCSE, MCSA:Messaging

daveberm wrote:
Here is a pointer on client access server.

http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/eae08282-fed8-4ae3-8229-18a23499b53d.mspx?mfr=true

Any client other than Outlook will use the client access server.
So
your OWA client, IMAP, POP3, ActiveSync will all be configured
to point
at one of the two access servers. This article says to
configure
network load balancing for your CAS servers...

http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/d2efb6f9-f70a-4f96-9f8d-f7aad6ae83d7.mspx?mfr=true

As far as bringing the DR Site online, that is handled via MCSC.
The
Exchange resource is simply moved from one server to the other,
the
clients do not realize a failover has occured.

David A. Bermingham, MCSE, MCSA:Messaging
Senior Systems Engineer
www.steeleye.com

RdS wrote:
Thanks for your reply.

I only have two mailbox servers so are you saying it is better
to put
all
mailboxes on one server and simply ccr to dr site. If I do
this then
the dr
site server will just be sitting there 95% of the time doing
nothing
until a
failure.

Also, in event of failure, how do I switch dr site to online
so that
clients
know to use it? Also, I have two client access servers (CAS).
one
at each
site.

A question on CAS, if one of the CAS is down, how do the
outlook
clients
know to use the other CAS to find mailbox server? right now I
have
one cas
in each data center. Also, if both CAS are operational, how
do
clients no
to use one or the other? any q articles on this and how it is
set
up?

my ip scheme is 10.25.x.x. one data center is 10.25.50 and
the other
is
10.25.51. both have a subnet mask of 255.255.255.0 and i use
vlans.

thanks again.


"Bharat Suneja [MVP]" <bharatsuneja@xxxxxxxxxxx> wrote in
message
news:e$MrzXBGHHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
- CCR cannot be configured between 2 independent Exchange
servers
already
hosting mailboxes.
- You need to setup a Windows Server 2003 cluster using MNS
(Majority Node
Set) quorum - consisting of 2 nodes and 1 file-share
witness, and
then
setup the Clustered Mailbox Server role on both the servers.
Active/Active
clustering is no longer supported with Exchange Server 2007.
- CCR may be possible across WAN links, but both the nodes
need to
reside
on the same subnet, which requires the use of VLANs to have
the
subnet
span over 2 sites (afaik).
- In any case, I'm hoping you're simply testing this and not
using
it in
production yet. Exchange Server 2007 has not RTMed yet - as
of now
the
only supported way of doing this is if you are part of any
of
Microsoft's
early deployment programs like RDP or TAP. In that case,
Microsoft
provides the required support to enable you to setup CCR.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"RdS" <RdS@xxxxxxxxxxxxx> wrote in message
news:epeqUDBGHHA.2128@xxxxxxxxxxxxxxxxxxxxxxx
hi,

I have two data centers and 4 Exch 2007 Ent servers. The
roles
are:
1) Mailbox and hub transport servers at data center1
2) Client Access Server at data center1
3) Mailbox and hub transport servers at data center2
4) Client Access Server at data center2

I have 2 storage groups and 14 DBs per server and 100
mailboxes
per db.
The
data centers are connected via a sonet (1gb+

How do I configure log shippping, etc. between the servers
so that
if one
fails I can bring the other online to handle the mailboxes?
During a
failure, instead of only having 14DB and 700 mailboxes per
server
the
operational box would have 28dbs and 1400 mailboxes. My
client
access
servers should then know what server the mailboxes reside
on since
that
is
one of their purposes. Can CCR be configured to do this?
I have
read
that
CCR is used with clustering but when both servers are in
same data
center.
In my case the data centers are dispersed. How do I
accomplish
this.
Any
MS articles?

My IPs are 10.55.10.x for
one data center and 10.155.10.x at the other. Subnet is
255.255.255.0.

But can I still split workload between the data centers and
have
mailboxes
live on both servers, but still CCR datacenter1 to
datacenter2 and
then
datacenter2 to datacenter1? So when one server hosting 700
mailboxes
goes
down the other will pick up load of other server while
still
handling its
700 mailboxes.


















.

Relevant Pages

  • Excange 2003 to 2007
    ... Host name mail.sunshine.com does not match any name found on the server certificate CN=MAIL09 ... Exchange Remote Connectivity Analyzer has encountered an error. ... Recovery Storage Group on one of your production mailbox servers. ... Recovery storage groups and 32 bit Exchange ...
    (microsoft.public.exchange.admin)
  • RE: Troubles with Exchange 2003 Queue - waiting Mails for 1 user!
    ... First you restored server with ghost, that is not recommended on Windows ... you can backup and restore SBS with SBS backup. ... Exchange attributes. ... Export all mails in Mailbox as .PST file. ...
    (microsoft.public.windows.server.sbs)
  • RE: Outlook Web Access/Exchange Server 2003 on SBS2K3 Server
    ... In the Exchange System Management Console, ... Servers, First Storage Group, Mailbox Store, then Mailboxes. ... This newsgroup only focuses on SBS technical issues. ... Outlook Web Access/Exchange Server 2003 on SBS2K3 Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Frage zur Architektur von Exchange 2007
    ... Gegeben sei eine Installation mit Exchange 2003. ... Der E2k3 Frontend Server ... Servern (CAS) und einem Edge Transport Server (ETS). ...
    (microsoft.public.de.exchange)
  • Re: Transition from FE to ET and CAS
    ... the CAS is installed. ... Then move the mailboxes from the 2003BE to the 2007mailbox server. ... server can't front-end an Exchange 2007 mailbox server. ...
    (microsoft.public.exchange.setup)
Loading