Link to home
Start Free TrialLog in
Avatar of jmichaelpalermo4
jmichaelpalermo4

asked on

How do I migrate Public Folders into a DAG? (Exchange 2010)

Hello Experts!

I currently have a single all-in-one Exchange 2010 server supporting several clients using a Public Folder database heavily. I need to copy this database into my clustered Exchange environment before I can migrate the clients on the all-in-one server. How can I copy the contents on the PF database to the cluster and make it available for the clients migrating over?

On a side note, I migrated one of the clients over to the cluster and their Public Folders were not available.

Please let me know if I need to clarify anything!

Thank you!
J
ASKER CERTIFIED SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You will need to create a new PF database and move the content from one DB to the next.

Steps on how to do this:
http://technet.microsoft.com/en-us/library/bb331970.aspx
Avatar of jmichaelpalermo4
jmichaelpalermo4

ASKER

Wow Simon, that's such a bummer. I knew about the PF database per MBX server, but didn't know you couldn't automate the failover...

Where I'm at right now is sitting on the single exchange server, attempting to replicate the contents of the PF database to a new PF database on the MBX server and it will not replicate for whatever reason.

becraig, I used the EMC gui to replicate the contents, just due to the newness of the whole process. Is there a way to check the status of the replication somewhere?

Thanks!
J
You might want to just run Get-PublicFolderStatistics

Compare the output that should give you a baseline.


Get-PublicFolderStatistics -Server PFServer1            
Get-PublicFolderStatistics -Server PFServer2
How long have you waited for replication to happen.
If it isn't a week, then you haven't waited long enough.

No, I am not joking.

Public folder replication basically hasn't changed since Exchange 5.5, so is very conservative. Therefore it can take hours, and sometimes days for things to happen.

Simon.