Exchange 2010 High Availability of Public Folders?
skreel
configure public folder replication. How then does one make this highly
available to outlook clients?
Outlook clients connect directly to the mailbox server for public
folder access and do not go through the CAS or CAS array. So no
HA/redundancy there.
In previous versions of exchange 2003/2007, public folder HA was
available since the clustering happened at the server level. Now that
DAGs are required and clustering happens at the database level this
isn't so available since DAGs don't support public folder databases.
It is my understanding that the client has one default public folder
database associated to it. This is set on the mailbox database
(Exchange Management Console->Organization
Configureation->Mailbox->Properties on Mailbox->Client Settings
Tab->Default public folder database). When the server that hosts that
public folder database goes offline for routine maintenance or an
unscheduled outage, all public folder access is lost. How can one keep
public folders up and accessible without having to manually switch the
"Default Public Folder Database" on the mailbox database? I thought
referrals might work, but that doesn't seem to work since the clients
main PF server is down.
Is maintaining a legacy 2003 or 2007 exchange box the only option to
have public folders highly available?
--
skreel
http://forums.slipstick.com
Russ Kaufmann
news:skreel.4aerdn@invalid...
>
> configure public folder replication. How then does one make this highly
> available to outlook clients?
>
> Outlook clients connect directly to the mailbox server for public
> folder access and do not go through the CAS or CAS array. So no
> HA/redundancy there.
In the event public folders are not available on the MB server, other
servers in the same site will be checked, and then servers in other sites
will be checked according to costs.
If you configure public folder replication, then you have achieved HA for
public folders.
Or am I missing something here?
--
Russ Kaufmann
MVP, MCT, MCITP x7, MCTS x9, MCSE x4, CTT+
ClusterHelp.com, a Microsoft Gold Certified Partner
Email:ru...@clusterhelp.com
http://www.clusterhelp.com
Blog: http://msmvps.com/clusterhelp
skreel
Russ Kaufmann;144159 Wrote:
> In the event public folders are not available on the MB server, other
> servers in the same site will be checked, and then servers in other
> sites
> will be checked according to costs.
>
> If you configure public folder replication, then you have achieved HA
> for
> public folders.
>
> Or am I missing something here?
>
It doesn't appear to work that way in my test environment. I have two
servers. They're using DAG for the mailbox db and each server has a
public folder db with replication between the two. If the server is
down that contains the default public folder database, clients can not
access public folders until I do one of two things. I either turn the
server back on or I switch the default public folder database setting on
the mailbox database to use the public folder database on the second
server. Clients will not automatically use the second database. Thus
no HA.
--
skreel
http://forums.slipstick.com
Russ Kaufmann
news:skreel.4ag3iy@invalid...
>
> It doesn't appear to work that way in my test environment. I have two
> servers. They're using DAG for the mailbox db and each server has a
> public folder db with replication between the two. If the server is
> down that contains the default public folder database, clients can not
> access public folders until I do one of two things. I either turn the
> server back on or I switch the default public folder database setting on
> the mailbox database to use the public folder database on the second
> server. Clients will not automatically use the second database. Thus
> no HA.
I am sorry to hear that. I do not know of a reason that this would be a
problem.