• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

exchange 5.5 and exporting public folders?

B

Busie23

Senior member
We tried replicating the public folders over to new server but only half of them made it. Nothing seems to work to get these things fixed, so I found a post on the web talking about exprting the public folders as a .pst and importing them on the new sever. Then use the exchange tools pfinfo.exe and pfadmin.exe to carry over the file permissions.

Anyone know anything about this or about defragging/compacting the mailbox databases offline? The exchange tool to do that seems kinda tricky and I'm not really finding to much good info on how to use it?
 
The way that I was told to migrate the Public folders was drop then down to pst also.

I just copied the items into a pst as I would any other mailbox items.

Wasn't much differnt than that.

Now for the defragmentation tool.

Here is microsoft's guide on using it.

How to Defragment with the Eseutil Utility

It mentions you will need 110% Free Hard Drive space in the directory of the datastore so DO NOT Begin unless you have the space.

Another thing that I highly recommend is to backup the datastore (file copy or tape copy over) before the procedure.

I have done around 20+ of these defragmentations so far and each time I still consider doing a direct copy of my database before beginning.

Here is another utility that you may need to use also if the data store can't be brought online right after the compaction.

ISINTEG Utility

You may need to run the Consistancy Adjuster also..

To run DS/IS consistency adjuster

Make sure botht he ISINTEG and DS/IS Consistancy Adjuster are used ONLY if you can't bring the datastore back online right after the defrag operation.

You should get clues in the event log telling you which you may need to run.

First and Foremost I highly recommend a backup of your datastore for this defragment and other operations are highly dangerous operations that could make your datastore unusable.

Good Luck

 
Microsoft recommends not doing an offline defrag unless you have a reason to - the built-in nightly maintenance does a decent job of it.
 
Here is how to estimate how much slack you have (white space) that can potentially be reclaimed during an offline defrag.

Event ID 1221

I also agree with bozo1 about the necessity of the defrag being determined prior to doing such an operation.

 
As Santa has already posted, run an ISINTEG -FIX -PUB ALLTESTS to check for any DB errors. But, if you were wanting to export your public folders, then you would use the Outlook client, create a PST file, and then just simply drag-and-drop your public folders to the local PST. Keep in mind that the PST will begin to become flakey at best when the size reaches 500MB in size. I would examine the PUB files to see how big they are.

I would disagree with the comments that the online defrag on Exchange 5.5 works quite well. I have always found that running an offline defrag once a month on my DB's improves not only performance, but also reduces the chance of physical errors with the DB. Also, Microsoft even recommends (fromt the engineers at the MPSS group) that if you have a DB that is over the size of 15GB, a monthly offline defrag is benefitial to the stability of the DB.
 
Ok, so what is the procedure to export as pst's? Do you first use pfadmin to get the rights/permissions, then setup an outlook client on both servers with admin access so you can export to the pst on one server and then import the new pst file on the other server in the outlook client? Then run pfadmin again to to copy over the permissions?

When we tried replicating from the old server to the new server we ended up getting about half of the public folders over. It was something like 273mb copied over out of 530mb, give or take. The mailboxes moved over just fine so we are currently running both servers in conjunction, the old is running the public folders, while the new sever has the mailboxes.

I have read up about the public folders all over the place and I'm under the impression that are backfilling is not working properly. When viewing the log files backfill request are being sent but they are getting denied? So I think it is trying to replicate but but isn't completing for some reason?

 
We are still having problems with our public folders. Does it matter if both servers are in the same site? Both of our servers are in the same site, thus when I log in as admin to drop them into a .pst on the old server I don't have any problem. But what do you do when you log into the new server and try to drop thrm into the public folders? The old public folders are showing up as if they are really there since we are running both in conjunction? Do the servers need to be on different sites in order to transfer the .pst over.


We are also now having a problem getting our internet mail connector to move over to the new server. So currently all intra office mail is on the new server, while outside email and public folders are on the old server and both servers are in the same site. I'm guessing they shouldn't be in the same site and then it will be easy to move everything over correct?

Thanks,

Busie
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top