SBS 2003 - 2008 Migration. Public folder seems to stop replicating

I started the migration of a server from SBS 2003 to SBS 2008 on Tuesday evening. I used the following reference : http://technet.microsoft.com/en-us/library/sbs-2008-2003-migration%28WS.10%29.aspx.

The language of the server is french, so I'm using the french version of the above document and will try to translate the more accurately possible the exchange terms (but be prepared for some differences).

The mailbox have successfully been moved. The new server has been configured to send and receive mail and is doing the job. Thinking that the move of the public folders was ok (not finished, but active), I do the following steps : suppress GP and scripts, migrate documents and user folders, install sql server (which I will need for LOB) and antivirus.

Now, Saturday morning, the public folder database has a size of ~10 GB on the source server, and ~3.8 GB on the destination server. It was something like 3.6 GB on Friday evening.

On the source server, at first when I was looking at the queue information (in Exchange management. First group of administration. Servers. SourceServer. Queue), there were a lot of activity in “SOURC_ESERVER – DEST_SERVER (Connector of routing group)”. Now there is no activity.

I tried to publish again by right click on public folder, then Move all replicas, but still no activity.

I activated loggin as in step2 of http://support.microsoft.com/kb/842273 and the only event I have on the source server is (translation !): Source: MSExchangeIS Public Store, Category: Message replication outgoing, Type: information, Id: 3017, Description: Type outgoing message 0x20, MessageId …

Is that normal ? Just incredibly slow, with that speed (400 KB / day) it will take 15 days to finish ...

Or should I begin to think restore of a backup of the source server, reinstall of the new server ...

Thanks for any idea
jpgeorgeAsked:
Who is Participating?
 
jpgeorgeAuthor Commented:
Rebooting both servers every 30 minutes until their is no more public folders to replicate does it!

Each reboot replicated ~50 folders very quickly.

It would be very interesting to know if it was a solution for those servers only, or if it works for other servers. So if somebody has the same problem, thanks to add comment to say if it works or not.
0
 
davorinCommented:
"Depending upon the replication interval you have set and the amount of information that must be replicated, this process may take from several hours to days to complete."
from http://technet.microsoft.com/en-us/library/cc527516(WS.10).aspx

The part of migration of public folders is really annoying. At one occasion it has taken me almost 3 days to migrate 50 MB of public folders!!!
As you have 21 days long grace period to finish the migration, I would wait and give time to migration of public folders to finish. If you look at whole amount of synced public folders, the speed is about 1,1 GB/day.
0
 
davorinCommented:
Now it is a little bit late to use approach of copying public folder data to destination sever over pst file.
http://forums.techarena.in/small-business-server/1216105.htm
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
jpgeorgeAuthor Commented:
For the slow and annoying part of migrating public folders, I completely agree. My last migration took 1 day for 10 GB, 3 days for the next 100 MB and took a week to migrate the remaining 10 MB !

That said, here I’m not sure that it is slow, I’m (was ?) afraid that it stopped completely as there were no events in application logs on both servers except ~40 events (ID: 3017) every 15 minutes for the complete Saturday. Public folder instances left doesn’t change either, was at 450 the all Saturday (and 500 Friday evening).

But this night, activity has happened and Public folder instances left is now 400 and db size has grown to 3.9 GB. There is more activity in the event logs too, not only ID 3017 (3018, 3010, 3016, 3072, 3021, …). But it seems, that it’s back to 40 events 3017 every 15 minutes.

I would be happy to transfer manually public folders to pst but I’m not sure how to proceed.

When I connect with a user whose mailbox is on the new server and ask for folder size of the root public folder in Outlook I get 3.3 GB. When I create a new user on the old server and connect to the old server with Outlook, I get the exact same size of 3.3 GB. When I look at folder content, they seem to be the same with both users. It seems that they are both connected to the new public folders on the new server.

I’m not sure of what should be or not in public folders (and I have to wait ‘til Tuesday to ask users), but I think all folders are on the new server, but a lot are empty (and shouldn’t).

So how can I connect to the old public folders on the old server ? Another question, when connected to the new server, will it show not yet replicated folder, or are they visible only after they have successfully migrated ?

Thanks for your help.
0
 
jpgeorgeAuthor Commented:
Update.

It seems that each time I reboot both servers, ~50 folders are migrated. Just created a task per server to reboot every 30 minutes for the next 7 hours.

At the moment still 260 folders to migrate ...

If it's the solution ...
0
 
jpgeorgeAuthor Commented:
@Davorin

Thanks to not let me alone for this looooooong weekend.
0
 
davorinCommented:
:) Interesting workaround. I have never tried it, but at some next migrations maybe I will.

I'm glad that you have finished your migration.
0
 
jpgeorgeAuthor Commented:
I accepted my comment as the solution because it is the solution. And why should I comment on that ? 8:)
0
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.