On Dec 7, 5:47 am, "Oliver Moazzezi [MVP]"
Post by Oliver Moazzezi [MVP]
I am presuming you're not going to restore your Exchange database, even
though that is the best practice scenario when dealing with a situation like
From what you said (syncing OST back to Exchange store) I assumed you had
mounted a new clean store, and was trying to get the OST data back.
This of course is not possible. You only course of action if you wanted to
pursue this would be to convert your OST files into PSTs. You could then
import these PSTs into Outlook and it would indeed put this mail back into
the Exchange database.
May I ask why you don't restore from backup? Even if your backup is a month
old, you will have Transaction Logs available (presuming you don't have
circular logging enabled) to be able to roll up to the point of failure?
You're assuming this wasn't a complete hardware failure, in which case
no transaction logs.
In a small enough environment, and if you can be sure EVERYONE has an
up to date cached OST thats it's not too critical. I wouldn't
recommend it for like 100 people, or something :)
But yeah, convert the OST to PST, reconnect to the new exchange and
have an empty inbox, mount/connect to the PST file, and drag/drop to
the inbox, viola, all back on the server .. You'll lose a few things
tho, a lot of more advanced things, such as server rules, a lot of
calendar functionality, so its worth rechecking everyones calendars
once done, especially events with multiple attendees, and recurrence,
etc. Also labels/colour coding i think is one of the things you'll
lose. If people rely on OLD calendar data, like, want to be able ot
look back to events scheudled 6 months ago, it might still be a good
idea to restore the 1 month old back, convert the OST -> PST, then
manually sync whats new only, that way all exchange functionality for
everything 1 month or older is maintained