High Availability Options for Public Folders and Exchange 2010

We currently are running two CCR (continuous cluster replication) Exchange 2007 servers on Server 2008 R2.  We also use mail-enabled public folders.  We would like to upgrade to Exchange 2010 so we can lose the external Hub Transport / Client Access server, which I see as one additional point of failure.  The problem is the new architecture of Exchange 2010 does not use CCR and its "successor," DAG (database availability group) does not work with public folders.  I assume this is part of Microsoft's continuing effort to force everyone onto Sharepoint.  Anyway, the question is what would be the best configuration that would let me upgrade to Exchange 2010, keep my mail-enabled public folders and accommodate some form of high availability?
Who is Participating?
AkhaterConnect With a Mentor Commented:
the best/only thing you can do is create 2 public folder databases, one on each server, with replication between the two.

install 2010 SP1 and rollup 2 which resolves the problem (at least partially)

check http://blogs.technet.com/b/exchange/archive/2010/12/14/3411676.aspx 

2409597 Implement OpenFlags.AlternateServer for PublicLogon

Herb-AvoreAuthor Commented:
Thanks.  Good info.  We have 200 public folders.  Would I have to configure replication for each one?  Or could I batch this using the Shell?
no of course you can use the

AddReplicaToPFRecursive.ps1 -TopPublicFolder \ -ServerToAdd OtherServer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.