Learn how to a build a cloud-first strategyRegister Now


I would like to copy my production exchange database to the new exchange lab

Posted on 2008-11-17
Medium Priority
Last Modified: 2013-12-24
Hello exchange admins,
I would like to get some help if the universe has help for my issue.

 Here is the background, Lab: I finished setting up a test lab& it has 2 DC, 2 dns, 1 dhcp, ad 2003, exchange 2003 front-end and back-end and 2 PC for user based testing. No internet connection ( I used my wireless set-up temporary to update all the servers then set the servers up with static IPs and cut off internet connection).

Issue: I would like to copy my production exchange database to the new exchange lab.

What has been done:
I copied the information store from my production server (back-end) and placed it on an external hard drive.

I then copied the .edb and .stm from the external drive over to the L3 (back-end server in the LAB) on the exsrvr folder, I have not merge the information... I have not done anything else.

What do I do next?
How do I complete this process?
Also, how will AD act???
This is a flat network&&
Thank you&

Question by:Tencha
  • 3
  • 2
LVL 58

Assisted Solution

tigermatt earned 1000 total points
ID: 22980239

Do the lab and the production network have the same Exchange organization name, Active Directory domain name, server names etc.? If they do, you should be able to replace the databases on L3 with your existing .edb and .stm files, and then mount them. The mailboxes should come back, but to have them reconnected to user accounts, you'd need to re-create all the user accounts so they are on the lab network too, then re-connect the Exchange mailboxes in Exchange System Manager to each user's account.

When I set up labs, I just create several test users on the Active Directory, along with mailboxes, rather than trying to copy the live user base across to the lab environment. You should worry more about configuring the settings of the software applications the same, rather than bringing over data which will instantly be out of date.

It is doable, but not the main concern in a lab environment.


Assisted Solution

butor69 earned 200 total points
ID: 22980245
firstable , you have to copy the AD also to the new environment. several solution, : if the production DC hardware is the same as the labao DC hardware : full backup and restore.

If not, install a DC in the production environment,  set it as GC, be sure that synchro is OK then take it to the labo environement and seize the role (see on google seize role )
You will have the complete AD  in you lab.
Then for the Exchange, you have to install an exchange with the same name, create a store as it is created on the actual one, dismount it,  and then you can normaly replace the edb and log files (e carefull to use the same locations)  and then remount it.

Author Comment

ID: 22980363
No the name is no the same...
prod is CXXXXCITY(all caps, no space)
test is CXXXX City (space caps and lower case)

AD lab:
l1.cXXXXXcity.ad  is a DC and it has all the roles, I seized them last week to get exchange to run. (Problems with froest prep).

I can recreate the user accounts and connect them (I assume) if I can get the database to load...any other suggestions?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

LVL 58

Assisted Solution

tigermatt earned 1000 total points
ID: 22982624

Since the test network has a different name to the production network, you cannot just copy the Exchange .edb and .stm files across from the old server and expect them to work. Those files NEED the domain name, Exchange organization name and the Exchange server name to be the same on the lab network as on the production network.

Your only option as far as I can see is to do a backup of your Information Store using NTBackup, then copy the backup file to the lab and restore that to the lab network. You will still need to reconnect accounts to user accounts, though.


Author Comment

ID: 22986955
Thank you, I will backing this afternoon.

Accepted Solution

Tencha earned 0 total points
ID: 23045105
I have move forward and created some other accounts. I am moving along with the install of Exchange 2007 in lab.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question