As we discussed in previous article
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook
We had to move public folder database out of CAS server to some other server that didn’t had the CAS role.
So here is the approach that we have used for doing it, this approach can only be used if you have multiple replicas of Public folder database.
Open shell & change the directory where exchange scripts are present
.\MoveAllReplicas.ps1 -Server OldServer -NewServer NewServer
Note:- Public folder database must be created on the new server(than only above command will work)
Reference Shell command for creating Public folder database: New-PublicFolderDatabase Nameofdb -server nameofserver -EdbFilePath e:\pf\pf.edb -LogFolderPath e:\pf
MoveAllReplicas.ps1 –> will remove the old server name as replica & adds the new server in the list of replicas. It will take time for replication to complete & populate the new Public folder database.
In our case 45 GB of content took a complete day to get replicated.
You can use below command to check the status of new server & old server
Get-PublicFolderStatistics -Server servername
Old server should not display anything, it means replication has been moved to new server. (you can remove the old database after checking it)
If you found some public folders that are still using old server than fix them individually to use new server as replication partner & remove old server from replica list.
For replication to complete you have to wait & be patient.
Thanks for reading…
11 thoughts on “Move Public Folder database from One server to Another”
I try to move my public forder database from mailbox server srv01 to mailbox server srv02 but I can’t.
Can you give me more information please ?
I only have the db_pb01 on server srv01.
What I need to do ? Just create a database db_pb02 to srv02 and use the command MoveAllReplicas.ps1 ? The command MoveAllReplicas.ps1 must be run on which server ?
The MoveAllReplicas.ps1 copy the content from db_pb01 to db_pb02 ?
Thank you for your help.
Have a nice day.
I will say first Add the replica…\AddReplicaToPFRecursive.ps1 to add other server to replication ones its replicated than use the MoveAllReplicas.ps1 …
Ok thank you. I do this, it replicated the hierarchy but not the content.
It’s the MoveAllReplicas that replicate the content ?
Thank yous so much
AddReplicaToPFRecursive.ps1 should replicate the content as well, ones the content is replicated than only use move replica…You need to check why content is not getting replicated…
Thank you for the answer.
Only new content is replicated… For old content, I need to use exFolders as I read in other post. Is it true ?
exfolders helps in troubleshooting the issue, some times thee is a corrupted item thats’ why replication stops…
Thank you 🙂
I followed your steps above. After the data replicated. I dismounted the old public folder database. And now, none of the public folders are there. When I mount the old public folder database, it works again. Just seems odd that all the public folder data replicated correctly (not all system folders did, I see 401 items for “exchangeV1.”
So my question is, if I replicated all my public folders to the new public folder database, and pointed the default public folders to the new location, why is it, that the public folders do not show when I dismount the old public folder store?
Have you changed the exchange database property to point to new database under client settings ?
Yes I did in EMC for each database mounted.
Nm, I guess the replication did not finish. Took over 3 days. Just tested it again. Data still shows online now with old public folder dismounted.
Thanks for replying earlier Vikas