Solved

Manually move exchange 2013 database to 2007

Posted on 2013-12-14
4
662 Views
Last Modified: 2013-12-16
I have an exchange migration that has gone horribly wrong. We can't access ecp, owa, and exchange shell keeps saying that exchange commands are not recognized.

I just need to get the mailboxes that are on that server and move them back to the original 2007 exchange server.  Trying to do this from the 2007 management console or shell results in the following error:


Move-Mailbox : Error was found for ktest (ktest@aihfs.org) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: An unknown error has occurred., error code: -1056749262At line:1 char:12
+ Move-Mailbox <<<<
0
Comment
Question by:KMDComp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 11

Expert Comment

by:Marc Dekeyser
ID: 39719800
You cannot manually move the mailbox database to 2007. It will not work. Right now you're best bet is to move the mailboxes with the -configonly parameter which will note move any data. Once move you can restore a backup an recover the data you lost during the move.

And you should always initiate mailbox moves from the highest version server.
0
 
LVL 20

Expert Comment

by:Peter Hutchison
ID: 39719868
I agree with Geminon on this. Any mailbox moves should be performed on 2013 web admin console to move mailboxes back to 2007 system.
0
 
LVL 14

Accepted Solution

by:
Radweld earned 500 total points
ID: 39720442
I guess the problem he's got is that he can't run the required commands in order to do this. you really will have to fix Exchange 2013 first. If things are that bad, If you can't fix it, your best option might be to backup the databases blow away the server, rebuild it using the recover server option and re add the database as a dial tone database.
0
 
LVL 37

Expert Comment

by:ArneLovius
ID: 39720640
How about shutting down the IS, copying the databases off, doing a clean install of 2013 on a "new" server, then attaching the databases that were copied off ?

if that then works, shut down the "faulty" 2013 server and manually remove it from AD

http://technet.microsoft.com/en-us/library/dd876873(v=exchg.150).aspx
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

627 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