When importing a PST into Outlook 2010, the Exchange 2010 server overwrites the PST data

We have Exchange 2010 SP1 server. We've had issues with one of the Exchange 2010 databases, and now that EDB cannot come online.
So I've ended up doing is using a 3rd party tool (Lepide) to export the EDB into PSTs for each user.
I have the PSTs and I'm trying to import them into a new EDB I've created. There are 2 issues:
1) Importing into Exchange server directly with this command takes DAYS and does not finish at all for ANY mailbox even small ones:
New-MailboxImportRequest -Mailbox <userMailbox> - FilePath <pathToPstFile>
I read on forums that this is a EXC2010 SP1 bug.. But that's the main concern, since I can import the PSTs via Outlook. However, here's the second issue:
2) When I open the new user's Outlook profile and import the old PST data, the import works but the data gets overwritten by Exchange server!!! So all the imported emails are deleted! As example, I'm attaching a screen shot that shows the server data and Outlook  data.
server-does-not-syncronize-data-.png
cdesk458Asked:
Who is Participating?
 
cdesk458Connect With a Mentor Author Commented:
Resolved!

The whole issue was with Lepide Exchange Recovery Manager export options. After consulting with their support, this is the solution:

Open Lepide Exchange Recovery manager.
2.  Go to 'Tools' on the menu bar.
3.  Click on 'settings'.
4.  Now, check in the checkbox "Recovery from only basic properties of email items (such as from, to, attachments etc)".
If the chechbox is not visible in the settings option, then it must be in        the 'advanced settings' under the 'settings' menu.

That explains why I could perform imports of other PSTs but not PSTs generated by Lepide.

Thanks, Simon, I will update the Exchange Server to the latest when I can.

Yes, I did create a new database and created new mailboxes for each mailbox in the old database. The issue occurs when importing to those new mailboxes. (The old db is offline and cannot be mounted.)
With this resolution from Lepide support, the import works.
0
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
Exchange 2010 SP1 is end of life, has been for some time. You should really be on SP3 by now (SP2 is EOL next month).

Did you not have a backup of the database? If the database is knackered then you should have replaced it like with like, then restore the database and then replayed the transaction logs. That would have got you to the point of failure and is how Exchange is designed to work.

How exactly did you get to the point you have on the Exchange side? You have missed out quite a few steps.

Simon.
0
 
Adam BrownConnect With a Mentor Sr Solutions ArchitectCommented:
There's usually a lot you can do to get a Mailbox Database back online if it won't mount. You can usually use ESEUtil to fix most problems with a mailbox database. http://blogs.technet.com/b/exchange/archive/2004/06/18/159413.aspx has info on how to use that. It's a command line utility that is in the Exchange binaries folder. If you can export PSTs from the EDB file, you can get it fixed and mounted.

That said, the reason you are seeing a difference between what's in outlook and what's on the server is because you are in cached mode. If you import a PST file in cached mode, it will upload the emails you import the next time the outlook client checks in with the server. You can make that work better by disabling cache mode in the email profile.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
cdesk458Author Commented:
Yes I have ran the Repair, Replay and Defragment cmds numerous times, trying to recover the database, including the steps posted in your link, acbrown:
Eseutil /P
Eseutil /D
Eseutil /R E00 /A
Eseutil /R E00 /I
Isinteg -fix -test alltests

Simon, the reason we are in this mess is because the underlying SAN storage ran out of space on this particular volume, effectively hanging the Exchange server, and (as I found out) corrupting the database. Whenever I try to do a repair, the eseutil gives me a message saying "page checksum mismatch" 1018 error code.
I would love to restore the EDB, but it seems that I can't. Thus I ended up paying to a recovery tool to extract the PSTs.

But yeah.. I'm looking at this page, it seems like this Exchange server had auto Win updates turned off, since it is an older 14.1 build (SP1): http://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx
So my course of action should be to update it.
0
 
cdesk458Author Commented:
Then there is this Outlook import issue... I have an update:
- When I find the old OST file on each user's desktop, and convert it to a PST file (using SysTools OST Recovery), I AM able to import the data and sync to Exchange server mailbox. This works in both cached and uncached mode.
- BUT this process requires me to login and copy the OST file from every affected user's desktop, which takes a while.

I really wanted to extract the PSTs on the Exchange server (currently using Lepide Exchange Recovery Manager). It has an option to convert a corrupt EDB file to PSTs for every user. The issue is when with importing THESE PSTs extracted with Lepide. The behavior is:
a) I see messages being imported
b) then after 10 seconds the imported messages are deleted!!
It's as if Exchange is rejecting the data from the PSTs extracted from the EDB file...
Hope this makes sense.
0
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
My instinct is that there is still a problem with the database and Exchange isn't accepting the data for that reason. Have you tried creating a new database, moving users to it and see if that improves matters?

Exchange service packs don't come down in Windows Updates, so even if Windows Update was enabled it would still be on 14.1 - unless someone installed the service pack.

Simon.
0
 
cdesk458Author Commented:
The real solution did not come from any other member. I had to get on a support call with a Lepide rep, and obtain the solution for myself, which I posted here.
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.