Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 320
  • Last Modified:

Public Folder Replication Issues During Migration To Exchange 2007

Hi,
I am experiencing issues with public folder replication in Exchange 2007. We are in the process of P2V'ing our infrastructure and upgrading our Exchange environment to 2007. We had an Exchange 2003 server running on a physical box and installed Exchange 2007 into our environment on a VMware ESX host. I moved pub folders using moveallreplicas.ps1 and  after about 4 days when the public folder data had moved to our 2007 box we moved all user mailboxes. All was working well but the next day the SAN died. We restored the Exchange 2007 server to a physical box in the hope that we could P2V it when the SAN was fixed. The problem is we have do not have enough downtime available to P2V the box - it just takes too long. I have therefore installed a fresh Exchange 2007 server on an ESX host my aim being to move all data to the virtual Exchange 2007 server and retire the old 2007 server. I ran the moveallreplicas.ps1 script about 24 hours ago and running the following command shows all replicas are on the new 2007 server -- "Get-publicfolder \ -recurse |ft Name,Replicas". The problem is that we have about 200GB of public folder data and the new Pub folder database is currently only 60MB in size, it was also last updated more that 12 hours ago, even though people have been making changes to the folders all morning, we have about 250 users. I'm confused - why has it not been modified even though users are making changes? I'm also worried - I only have a few days to get this done and at this rate it will take weeks, I need the physical box back that Exchange is running on for another very urgent project. Is there any way that I can speed the data transfer up?

Thank You  

Sophie
0
SophieP1981
Asked:
SophieP1981
  • 2
1 Solution
 
SurajCommented:
You should perform the moveallreplicas only after complete public folder replication. You can add back the public folder replica to the old server and then wait for 24-48hrs depending upon the bandwidth and how busy your server is it would replicate the content. Once you have everything in sync you can remove the replica for the old server.

thanks,
x-sam,
0
 
SophieP1981Author Commented:
Really sorry - I forgot about this question. We took your advice Sam and that helped us clear the problem - we weren't being patient enough! Thanks for your response.

Apologies again for the delay.

Thanks,

Sophie
0
 
SurajCommented:
Nice to know that the issue is resolvd by my suggestion. But why are u deleting this question.. why not giving Points?
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now