We are implimenting a disaster recovery solution for our Exchange server. The question keeps crossing our minds that since exchange cached mode is used, each person's computer has a backup of their mailboxin the OST file. Can this OSTbe used to re-populate a backup exchange server? Two scenarios: 1. The backup exchange server has empty mailboxes on it 2. The backup exchange server has 24 - 48 hour old data on it.

Hi, That is only doable for small numbers of users. See this about ost encryption keys: http://support.microsoft.com/kb/282496 Leif

We have find best answer and solutions visits us : http://www.osttopstconversion.us/ Admin Exchange Server USA harry

If your ost files are corrupted then for accessing the Offline file is firstly converted to a new working PST file such that the data can be used. Lepide Exchange Manager efficiently and effectively converts damaged, corrupted, unusable, inaccessible OST files to PST files after recovering the data from OST files. For more information - http://www.exchangedatabaserecovery.co.uk

I've personally run into this situation Exchange 2010 mailbox database was lost, with no passive or restorable copy available. The solution was to set up a new empty database. Outlook 2010 prompted each user saying the data on the server had changed, they could access the new data (which took them to an empty mailbox) or to their old data (cached .ost file on their local PC). We instructed users/staff to connect to the old profile and export it to .pst. Then attach to the new profile and import it. Flaws in this are: * Ensuring everyone is using cached mode and .ost's are in good condition. * The .ost only has the mail from the last connection to Exchange. Any mail delivered and not downloaded would be lost (think about if someone was on vacation for a week how out of date the .ost could be!) It's nice to have as an option, but I wouldn't base my DR strategy around it!

I've personally run into this situation Exchange 2010 mailbox database was lost, with no passive or restorable copy available. The solution was to set up a new empty database. Outlook 2010 prompted each user saying the data on the server had changed, they could access the new data (which took them to an empty mailbox) or to their old data (cached .ost file on their local PC). We instructed users/staff to connect to the old profile and export it to .pst. Then attach to the new profile and import it. Flaws in this are: * Ensuring everyone is using cached mode and .ost's are in good condition. * The .ost only has the mail from the last connection to Exchange. Any mail delivered and not downloaded would be lost (think about if someone was on vacation for a week how out of date the .ost could be!) It's nice to have as an option, but I wouldn't base my DR strategy around it!

You will have to export the OST to a PST before the user connects to the Exchange Server otherwise as soon as the user connects to the Exchange Server the OST will be wiped off with New Data i.e Empty Mailbox Data Thanks Syed MM - Messaging SME - IBM || MCTS: Microsoft Exchange Server 2007/2010 || MCSE || MCSA ||