cdesk458
asked on
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
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
- 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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
ASKER
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.