Exchange 2007 new mail store

Hi,

I have an Exchange 2007 where the information store does not want to mount due to corruption. To make a long story short, I want to create a new Exchange database and archive the existing users mail on their local PC's so Exchange can receive all current mails.

What is the best way to re-create a new Exchange 2007 database / the quickest way of creating a new Exchange database and have all Outlook users receiving new mails without losing any of the mails in their Outlook?

I just need all the new mails to be received, So in essence:

1) I need to archive all user mails in their Outlook (Kind f creating a PST file of their existing mail;
2) Have them receive new mails by having their Outlook connected to the new Exchange database

Please let me know if anyone had to start from a new Exchange database before, but at the same time, managing to keep all existing mails in Outlook.

Thank you.
LVL 3
wimpie_asgAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chanderpal singh rathoreMicrosoft Exchange EngineerCommented:
Hi wimpie_asg

1) Rename your old corrupt database
2) Create a new database with old name
3) mount this new database to your server and you will start receiving your new mails
4) You don't have to archive old mails of outlook and import it again as outlook will through the error something like use your old data or create new pst file, go for use old data.
5) you are all done
6) For corrupt database you can go for Eseutil tool ton recover your old database.

Let me know if you need further assistance.

Good Luck Man!!!!!!!!!!!!!
wimpie_asgAuthor Commented:
Hi chanderpal,

As the new mails are coming through, will it go to correct mailboxes, I dont have to re-created mailboxes do I? I remember this from Exchange 2003, as the mails were coming in, it created new mailboxes for the users.

But I am sure Exchange 2007 will treat this better than 2003?

I just created new Exchange mailbox with the exact name as the old Exchange. and mails that are coming in will go to the correct user?

Please let me know.
chanderpal singh rathoreMicrosoft Exchange EngineerCommented:
Hi wimpie_asg,

I have recently faced this issue and this worked perfectly fine with me. your mails will be delivered to same user. All other information is stored in active directory , your mails are with .edb file so don't worry it will work fine.

Thanks
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

wimpie_asgAuthor Commented:
One last question. Is there a way to disable user access to Exchange so they don't get the error message to auto archive their mails to PST files? I am scared they choose no or something and the user loses all their mails in Outlook due to the new Exchange database.
chanderpal singh rathoreMicrosoft Exchange EngineerCommented:
I don't think you have to do this as exchange uses active sync and it will upload the old mails back to new mailbox from outlook.

Your problem of corrupt database will also get resolved as you will get your mail back on new database.

Condition 2: If you lose any old mails we an go for repairing the corrupt mailbox and restore old mails of specific user.
wimpie_asgAuthor Commented:
Hi,

I renamed old Exchange database. In Exchange Management Console (EMC) It still has the entry for the old Exchange database, obviously, the AD users point to this location, I wont be able to remove this database as it would pickup the mailboxes being in this Exchange database. Removing this database entry in Exchange is obviously a vital part to create an Exchange databse with the same name?
chanderpal singh rathoreMicrosoft Exchange EngineerCommented:
Change name of old database in EMC and both .edb file and create the new database in the same folder as old database was created or rename the folder in which old database is placed and create new folder with old name. Give path of new database with same name and you are done now.
wimpie_asgAuthor Commented:
I am sorry for the stupid question, please tell me how you change the name of the database in EMC 2007 please?
tigermattCommented:
The above information is not totally correct.

The process you are asking to perform is a (variation of) a dialtone recovery, which you can find documented in the official documentation at https://technet.microsoft.com/en-us/library/bb310765%28v=exchg.80%29.aspx.

In particular, the specific steps you need to follow are found at https://technet.microsoft.com/en-us/library/bb310773%28v=exchg.80%29.aspx.

The relationship between a mailbox and the database is a pointer in Active Directory, informing Exchange which database object (and hence which storage group and mailbox server) hosts a given user's mailbox. You will not be able to -- and should not -- delete the entry for the database in the Exchange console, as Exchange will complain user mailboxes are still mapped to that object. However, that is the logical configuration; you can quite independently manipulate the raw database files on disk provided the mail store is dismounted.

The dialtone procedure assumes you will be recovering the user mailbox data from an Exchange database backup, and simply provides you with a means of maintaining business continuity by providing users with an empty mailbox to send/receive mail while the recovery takes place. An online, Volume Shadow Service-aware backup of the Exchange database is the proper way to prepare for disaster situations with an Exchange Server; this is restored to a recovery database and the data manipulated to recover it to the users' new mailboxes. Relying upon the Outlook client-side cache is not a good strategy.

Nevertheless, if you do not have an Exchange Server backup, I would strongly recommend taking backups of relevant OST and PST files on the Outlook clients *BEFORE* completing the dial-tone procedure. "Cached Exchange Mode" in Outlook is merely a cache -- not a hard local copy of the data -- and the last effect you wish is to create a dial-tone database and have Outlook empty its cache because all the data has disappeared from the mailbox on the server.

If data are contained in an OST, there are third-party tools available to convert those files into PST files, which you can subsequently re-import into Exchange.

I strongly recommend familiarizing yourself with the dial-tone procedure documentation before carrying out the process, and if in doubt and the data are critical to business operations, consult a paid professional for a second opinion BEFORE CHANGING ANYTHING to minimize the risk of data loss.

exchange uses active sync
ActiveSync has nothing to do with Outlook client connectivity, at least not on Windows; ActiveSync is Microsoft's name for the protocol used to synchronize Exchange with mobile devices. Outlook connects to the Exchange organization using MAPI Remote Procedure Calls, or via Outlook Anywhere by tunnelling RPC over a secured HTTPS tunnel.
wimpie_asgAuthor Commented:
Hi tigermatt,

Thank you for your detailed reply, this is very much appreciated, and exactly what I needed, a name to the solution, dial plan disaster recovery. Internet was full step-by-step on how to. The current Exchange database is on a dial plan Exchange data base, and the client are receiving all their current mails.

As per chanderpal, Outlook is indeed asking for to either log on to temp folder, or old mails. When logging on to temp folder, they are receiving all their current mails, and are able to send, this bought me time to get all the old mails back from either OST or old exchange database using Kernel for Exchange.

Being here, having the client sending and receiving mails in this point of time. I don't need the old database to mount anymore, it is simply too big to run any utils against, and the result wont be guaranteed, which brings me to my next question, can I make my temp dial plan  database  and make it my main database in Exchange in an effort to get Outlook from stopping to ask the question of old or temp mailbox and just to go forward and import old mails in to their Outlook?

I want to make my newly and working dial plan database and make it my primary database in exchange, if I understand correctly, this will stop Outlook from asking the question at the start to which mailbox to log on to?

Please let me know what you think, and again, thank you for all your responses.
tigermattCommented:
The current Exchange database is on a dial plan Exchange data base, and the client are receiving all their current mails.
Excellent. Good work!

I don't need the old database to mount anymore, it is simply too big to run any utils against, and the result wont be guaranteed
Okay -- if you have as much data as you believe you can recover from either the old database or local Outlook tools on the client side, then there really is no need to continue to maintain the old database in any state. I would keep it around until the procedure is finalised, as would I also keep around the OST and PST file backups from the Outlook clients.

can I make my temp dial plan  database  and make it my main database in Exchange in an effort to get Outlook from stopping to ask the question of old or temp mailbox and just to go forward and import old mails in to their Outlook?
Sure. Exchange doesn't have any special configuration to indicate this is a dial-tone recovery; it just knows it has a new, clean database mounted at the relevant path, and knows the same user mailboxes remain to be mapped across to that database. However, since Outlook is running in cached mode, it knows something has gone on server-side, hence the message you get on opening Outlook.

You can keep using the new database as your main one, and use either the tools in Outlook or the tools provided at the server to import the PST file exports you exported from the old DB and client-side Outlook configuration. On the server, Import-Mailbox is your friend. See https://technet.microsoft.com/en-GB/library/bb691363%28v=exchg.80%29.aspx.

Once you have done that, purge the caches on the client side, either by deleting the OST file or by re-creating the Outlook profile. Outlook will forget all about the old mailbox at this point, and should then re-sync with the new database. Just do make sure you have a backup first, in case it turns out some data is missing later on. :-)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.