Link to home
Start Free TrialLog in
Avatar of Tyler Laczko
Tyler LaczkoFlag for Canada

asked on

Exchange 2010 migration from 2003 (public folder issue)

I am currently in the process of migrating a 2003 exchange server to a new 2010 exchange server.
I have half of the users moved over and started replicating some of the public folders.

The synchronization of public folders has been causing many issues.

I set a sync schedule (it does not follow it)
I trying to limit the amount of connections from the virtual smtp connector (it does not follow it)
I have finally got it to stop synchronizing all of the folders and have been adding one at a time to sync after hours.

My major issue now is that the Public Folder database file is not growing. It has stopped at 24 043 520 KB

And the amount of log files has gone crazy. It is currently at 125 926 log files. (they are 1 MB each)



It seems like the synchronization that I am doing is being stored in the log files and not the public folder database.
Avatar of peakpeak
peakpeak
Flag of Sweden image

Avatar of Robberbaron (robr)
I can confirm that the export to PST and reimport works well except that you need to ensure that the DefaultUser has full rights to all folders prior to the export as the import will not have the indenties of other groups that may be assigned special permissions.  r

run PFDavAdmin on the 2003 server (or the subfolder under review), then export. Reset permissions after import using ExFolders (the 2010 update to PFDavAdmin)

out PF tree had some logical branches, so we exported each branch to its own PST file using 5 workstations. Then ran the import. about 40G took 6 hrs but was overnight.

Avatar of Tyler Laczko

ASKER

I have 120 GB and hundreds of folders.

Does the PST keep the user permissions
maintain per user read / unread, etc?
Unfortunately, no. You can, however, use a tool. Here's a myriad:
http://clintboessen.blogspot.com/2011/01/exchange-public-folder-tools.html

Note that ExMerge does not work with Public Folders
I believe we are getting off topic.

I would like to emphasis on:
My major issue now is that the Public Folder database file is not growing. It has stopped at 24 043 520 KB
And the amount of log files has gone crazy. It is currently at 125 926 log files. (they are 1 MB each)
Do a backup. That will purge the log files.
ASKER CERTIFIED SOLUTION
Avatar of Tyler Laczko
Tyler Laczko
Flag of Canada 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
Please read back
read back or reply back?

I'm not sure what you mean?
Do a backup. That will purge the log files.
This was the reason


It may be that the exchange database allocated that much room when I had public folder replication turned on for all folders. Then I turned it off for 90% of the folders.

I will continue to test the migration as soon as I get all of the users off of the old server. When I start replicating it really bogs down the 2003 server.
The public folder had allocated space for the files ahead of time.