Windows Server

STH · Guest

Is there any reason I shouldn't install LCS on our exchange cluster? The
servers have the resources and I'd like to consolidate servers.

Bob Christian · Guest

Note that LCS can't be "clustered" as the application is not cluster-aware.
It might not be advisable to install this on a clustered server. The SQL
back-end for LCS 2005 Enterprise Servers can be clustered.

Bob

"STH" <STH@discussions.microsoft.com> wrote in message
news:41F397CC-10DB-4E74-A238-323023298DA1@microsoft.com...

Bob Christian · Guest

Have you considered installing LCS on your front-end servers?

***Note: This configuration is not a supported configuration and there have
been threads where people have reported problems running LCS on their
Exchange 2003 servers. Microsoft has made it clear that this was neither a
tested configuration nor a supported configuration.***
That having been said: To date I have not had a problem with LCS on Exchange
2003 front-end OWA servers.

"Bob Christian" <BobChristian@removethis.gmail.com> wrote in message
news:OnhMebt%23EHA.2552@TK2MSFTNGP09.phx.gbl...

STH · Guest

Microsoft says the 2005 enterprise version of LCS is cluster aware.

"Bob Christian" wrote:

STH · Guest

It says on microsoft's site that LCS 2005 Enterprise is cluster aware. Is
this not true?

"Bob Christian" wrote:

STH · Guest

It says on the website that LCD enterprise version is cluster-aware. Is that
true?

"Bob Christian" wrote:

Steve · Guest

I think what is confusing is there are two componts to LCS 2005 - the front
end servers (a group of machines answering SIP requests) and the back end
servers (doing archiving and other LCS functions).

The Back End servers - running SQL can be clustered in true MSCS (what you
currently have for Exchange) however the front end servers running LCS 2005
must use either MS Network Load Balancing or a true hardware load balancer in
order to redirect SIP requests correctly.

Look at the document from MS on the design of the enterprise 2005 LCS and it
is clearer.

"STH" wrote:

Bob Christian · Guest

It is possible to load-balance LCS 2005 in a network load balanced
"cluster". That, however, does not mean that LCS is supported by Microsoft
Cluster Services. At least, that is my experience...but there is always the
possibility that I am mistaken.

If you have read something where LCS 2005 is supported by MS Cluster
Services (particularly if it is a change in LCS 2005 Service Pack 1, could
you point me to where it says this? I am curious by nature.

Thanks,

Bob

"STH" <STH@discussions.microsoft.com> wrote in message
news:9F9BFE13-C579-4D15-A4A5-00AD817A763D@microsoft.com...

STH · Guest

Here is the link I was looking at

http://www.microsoft.com/office/livecomm/prodinfo/compare.mspx

btw, sorry about the multiple replies. It kept telling me there was an
error so I didn't think it was going through.

"Bob Christian" wrote:

Bob Christian · Guest

No worries.

It is possible to cluster the LCS 2005 EE SQL back-end server. The LCS 2005
EE front-end/home servers can be put in a Network Load Balanced "cluster",
but it is recommended that a hardware load-balancer be utilized to balance
the servers rather than utilizing the NLB service.

I have not tried to cluster the Archiving Service, but one of the MSFT folks
may have. The Archving service sometimes sits on the SQL back-ends,
dependent upon the client's environment. Other environments (50k+), it may
sit on a separate server.

It may be possible for the front-ends to happily sit on a cluster box as an
(unclustered) application. Then again, the multiple NICs, virtual server
name, etc. would likely cause fits for them.

Bob

"STH" <STH@discussions.microsoft.com> wrote in message
news:481E1E4B-D5DD-4358-911A-A93FE2C2573B@microsoft.com...

toml@online.microsoft.com · Guest

I checked in on this and am able to provide further information on the
cluster support for LCS 2005. I have not worked with any cluster
configurations so I will not be able to answer anything beyond this at this
time.

LCS2005 EE SQL BE is supported in 2 node active passive cluster (only), you
will need W2K3EE, SQL2000SP3aEE and LCS2005EE. Details of spindles, RAIDs
etc are in the HP white paper see LCS2005 online doc partner section for
details.

LCS 2005 has not tested that the archiving service or that msmq is
cluster-aware, and have not end-to-end tested any archiving HA/failover
scenarios using clustering.

LCS 2005 has tested archiving HA via MSMQ (not using clustering) which
allows for a 30-45 minutes (not configurable) window for recovery – see
Planning Guide and Deployment Guide for more info here.

LCS 2005 has tested a deployment configuration (see topology #5 in the
planning guide) with EE servers of the same EE Pool using a different
archiving service but sharing a common archiving DB. This topology does
allow for the deployment of an EE-Pool where say each of the EE Servers has
its own archiving service component and sharing a common archiving DB (on a
sql cluster). However, this topology has more complexity given the higher
load on each EE server and the setup costs.
In this topology, each EE Server of the same EE Pool would be writing
to a local MSMQ which is picked up by a local archiving service that then
exports to a shared remote archiving DB on the SQL cluster. Each archiving
service component will need to be set-up to export to the same archiving
DB, and SQL service will have to be off when this setup happens.

I hope this helps
Tom LCS Kid

--------------------
From: "Bob Christian" <BobChristian@removethis.gmail.com>
References: <41F397CC-10DB-4E74-A238-323023298DA1@microsoft.com>
<OnhMebt#EHA.2552@TK2MSFTNGP09.phx.gbl>
<9F9BFE13-C579-4D15-A4A5-00AD817A763D@microsoft.com>
<eCbe9TS$EHA.2876@TK2MSFTNGP12.phx.gbl>
<481E1E4B-D5DD-4358-911A-A93FE2C2573B@microsoft.com>
Subject: Re: Installing LCS2K5 Enterprise on an Exchange Cluster
Date: Tue, 18 Jan 2005 22:29:36 -0500
Lines: 76
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <uuKYsdd$EHA.2012@TK2MSFTNGP15.phx.gbl>
Newsgroups: microsoft.public.livecomm.general
NNTP-Posting-Host: pcp449326pcs.wlmgti01.ga.comcast.net 68.51.138.137
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15
..phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.livecomm.general:5315
X-Tomcat-NG: microsoft.public.livecomm.general

No worries.

It is possible to cluster the LCS 2005 EE SQL back-end server. The LCS 2005
EE front-end/home servers can be put in a Network Load Balanced "cluster",
but it is recommended that a hardware load-balancer be utilized to balance
the servers rather than utilizing the NLB service.

I have not tried to cluster the Archiving Service, but one of the MSFT folks
may have. The Archving service sometimes sits on the SQL back-ends,
dependent upon the client's environment. Other environments (50k+), it may
sit on a separate server.

It may be possible for the front-ends to happily sit on a cluster box as an
(unclustered) application. Then again, the multiple NICs, virtual server
name, etc. would likely cause fits for them.

Bob

"STH" <STH@discussions.microsoft.com> wrote in message
news:481E1E4B-D5DD-4358-911A-A93FE2C2573B@microsoft.com...

	Windows Server Forum Index -> Live Communications Server	All times are GMT
Page 1 of 1