E2K7 + CCR and public folders

E2K7 + CCR and public folders (Full Version)

All Forums >> [Microsoft Exchange 2007] >> High Availability

Message

schnibitz -> E2K7 + CCR and public folders (30.Nov.2006 6:36:57 PM)
I am evaluating Exchange 2K7's features now and actually had a question: Did I read correctly that with an exchange CCR cluster, that public folders will not be replicated: http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/a26a07fc-f692-4d84-a645-4c7bda090a70.mspx?mfr=true Does that mean that after a failover, and a previously passive node gets the cluster resources, public folders will not be available? Thanks, Schnibitz

Henrik Walther -> RE: E2K7 + CCR and public folders (4.Dec.2006 5:43:46 PM)
Yes you can only have one Public Folder database when using CCR as PF replication will be disabled. Unfortunately PF and continuous replication cannot run at the same time.

armani132 -> RE: E2K7 + CCR and public folders (26.Feb.2007 10:36:17 AM)
What will be the migration scenario, if you want to migrate from Exchange 2003 to Exchange 2007 CCR. How do you get your public folders on the CCR node. Thanks, ----------------------------- Found the answer: Disable CCR and start replication. After replication completed succesfully, stop replication and enable CCR. To make sure that there is only one active copy of the public folders, dismount the pf store on the legacy environment and make sure that the public folder store is the default store that is used.

bhfoto -> RE: E2K7 + CCR and public folders (23.Apr.2007 3:35:47 PM)
I disagree with your comment: “Unfortunately PF and continuous replication cannot run at the same time.” According to Microsoft: If you have a single mailbox server in your Exchange organization, and that mailbox server is a clustered mailbox server in a CCR environment, the mailbox server can host a public folder database. In this configuration, there is a single public folder database in the organization. Thus, public folder replication is disabled. If you have multiple mailbox servers and only one of the mailbox servers contains a public folder database, the public folder database can be on a clustered mailbox server in a CCR environment. In this configuration, there is a single public folder database in the organization. Thus, public folder replication is disabled. As it seems, so long as you limit yourself to one PF database you can run this database successfully in a CCR environment. Your comments would be greatly appreciated. Thanks, bhfoto quote: ORIGINAL: Henrik Walther Yes you can only have one Public Folder database when using CCR as PF replication will be disabled. Unfortunately PF and continuous replication cannot run at the same time.

Henrik Walther -> RE: E2K7 + CCR and public folders (23.Apr.2007 4:12:00 PM)
I don't disagree and actually that was what I tried to say. But sometimes my replies goes very quick. So to make sure my message gets out properly. Yes you can store a PF database in a CCR cluster, but replicating this PF database with PF database instances on other mailbox servers isn't a supported scenario.

BeTaCam -> RE: E2K7 + CCR and public folders (24.Apr.2007 3:32:43 AM)
Simple rule of thumb. If there is only a single cluster ( and no other servers holding or intend to hold replica of Public folder) then - You can have 1 PF store with No replica. Else. on the cluster, you cannot hold a PF store under any other scenario. Hth BC

SSV -> RE: E2K7 + CCR and public folders (3.Apr.2008 11:06:01 AM)
In CCR Failover Passive server becomes Active and now Public Folders will be on Passive server, how this affects users accessing PF’s and what will happen to direct mails to PF’s, do the bounce or stay in the Q until reverse fail over happens? What is the alternative to overcome this with one mailbox server CCR cluster.

Lord Melch -> RE: E2K7 + CCR and public folders (29.Jul.2008 9:35:47 AM)
All, Does the below mean if you are migrating from E2K3 to a E2K7 CCR cluster you can create a single PF store (plus all your mailbox stores), on the CCR, replicate the PF's from E2K3 to the E2K7 CCR , remove the replica's from the E2K3 server and the failover between CCR nodes of the PF store will work ? Cheers, LM quote: ORIGINAL: BeTaCam Simple rule of thumb. If there is only a single cluster ( and no other servers holding or intend to hold replica of Public folder) then - You can have 1 PF store with No replica. Else. on the cluster, you cannot hold a PF store under any other scenario. Hth BC

Lord Melch -> RE: E2K7 + CCR and public folders (29.Jul.2008 12:08:53 PM)
Thinking about it I presume you mean if the PF on the CCR is replicating to somewhere else in the E2K7 org it can't fail over.. So you can only have one PF store in a E2K7 Org ??

a.grogan -> RE: E2K7 + CCR and public folders (5.Aug.2008 2:47:13 PM)
Hiya chap; Public Folder replication is not compatible with CCR replication, therefore IF you have more than one server hosting public folders in a CCR environment - in the event of a "lossy" failover there is a fair chance that the public folder database will not mount on the Passive CCR node. Cheers A

Lord Melch -> RE: E2K7 + CCR and public folders (6.Aug.2008 3:44:45 AM)
Hi There, Yep makes sense, thanks..

Lord Melch -> RE: E2K7 + CCR and public folders (26.Sep.2008 8:53:12 AM)
MS does infer that if you are migrating from E2K3 to a E2K7 CCR cluster you could replicate all the PF's to the CCR cluster. Then decommission the "old" E2K7 PF's, decommission the E2K3 server and CCR + PF will failover.. This is what the below seems to say.. http://blogs.technet.com/andym/archive/2008/04/14/exchange-2007-ccr-with-public-folder-store.aspx quote: If you are migrating public folder data into a CCR environment, you can use public folder replication to move the contents of a public folder database from a stand-alone Mailbox server or a clustered mailbox server in an SCC to a clustered mailbox server in a CCR environment. After you create the public folder database in a CCR environment, the additional public folder databases should only be present until your public folder data has fully replicated to the CCR environment. When replication has completed successfully, all public folder databases outside of the CCR environment should be removed, and you should not host any other public folder databases in the Exchange organization.

neilho -> RE: E2K7 + CCR and public folders (26.Sep.2008 9:11:53 AM)
That's correct. As Andy said earlier, the problem only occurs if you have a lossy failover in your CCR environment at the time other public folder databases exist outside of the public folder database in the CCR environment. In this case, the public folder database on the passive node will not mount until the previously active node is available again. I've migrated customers from E2K3 -> E2K7 CCR using public folder databases in both environments. The key for me was to do the public folder migration as quickly as possible and decommission the public folder databases from the E2K3 environment. It works but you must understand the risk that is presented during the coexistnence period where public folder databases exist outside of the public folder database configured in the CCR environment. It's very hard to word this in product documentation without creating a misunderstanding. [;)]

Lord Melch -> RE: E2K7 + CCR and public folders (26.Sep.2008 1:30:37 PM)
quote: It's very hard to word this in product documentation without creating a misunderstanding. [image]http://forums.msexchange.org/image/s4.gif[/image] Nice one, thanks for the info

chris meehan -> RE: E2K7 + CCR and public folders (8.Oct.2008 9:30:10 AM)
I have a fairly complex Exchange project underway which is part of an aquistion and was looking for some public folder advice. Call it company A and company B. Two seperate forests both being consolidated into a new forest / exchange organization hosted at an off-site facility. We are not migrating any mail so the plan is to not go the route of an intra-org migration with forest trusts and so on. There will be new accounts and mailboxes created in the new org and a cut-off date will be determined to start using the system. However, I do need to come up with a way to get the public folder data into the new org. I'm not really concerned about security and access permissions right now as it is a small users count and they can be handled as the issues arise. My main concern is getting the data into the organiztion. Company A is using Exchange 2007 SP1 with all roles on a single box. Company B is using Exchange 2003 SP2 - single server. Both Company A and Company B need to have their public folder data brought into the new Organiztion which will be a CCR cluster 2007 SP1 org. Are their any microsoft guides, tools, discussions that I can refer to? Any third party tools that can assist with my scenario? Thanks, Chris

rogerecust -> RE: E2K7 + CCR and public folders (14.Oct.2008 1:08:53 AM)
You can use "Inter-Organization Replication tool" ,a small tool from Microsoft to sync your PFs from EX2K3 to EX2K7, or EX2K7 to EX2K7accross forest. I used it and worked well.

Lord Melch -> RE: E2K7 + CCR and public folders (14.Oct.2008 5:54:55 AM)
A possible gotcha unless I am incorrect..[;)] I have migrated PF's to CCR and CASHT before. When you kick off the replication from E2K3 ESM (Wizard) it starts then and there. Even if you set a schedule on the PF store.. This can - normally does - create high Util on the host (E2K3) and target (E2K7) server(s) so watch out..

chris meehan -> RE: E2K7 + CCR and public folders (14.Oct.2008 7:40:25 AM)
Hmm... I will look into that thank you. Can i use the tool to get public folders from both the 2007 exchange org and the 2003 org into the third new 2007 org? Thanks

Lord Melch -> RE: E2K7 + CCR and public folders (14.Oct.2008 8:27:08 AM)
Sorry, never used that tool. Info here : http://www.microsoft.com/downloads/details.aspx?familyid=e7a951d7-1559-4f8f-b400-488b0c52430e&displaylang=en Maybe rogerecust can help

Exchange_Geek -> RE: E2K7 + CCR and public folders (14.Oct.2008 11:55:48 AM)
Sorry, you cannot do what you are trying to achieve - it is an inter-organization tool and not a three-way, four-way replication tool. You can run the tool specifically to work with replicating information to-and-fro between 2 Exchange organization.

Page: [1] 2 next > >>