locked
Exchange 2010 Database Move RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    As part of preparation to perform a server disk upgrade, the system image (full) backup was taken using the Windows Server Backup (WSB). However, after the disk replacement, and having performed the System state recovery, Exchange server 2010 failed to work. A new installation of Exchange Server 2010 was achieved on the server.

    My major challenge is moving the old database from the backup to the new Exchange installation.

    Can anybody help with the best method/approach to use in achieving the migration? The OS is Windows Server 2008 R2 Enterprise.

    Kind regards.

    Ben.

    Friday, April 22, 2016 9:23 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The server is back up and running, correct?  The cmdlet is Move-DatabasePath.

    https://technet.microsoft.com/en-us/library/bb124742(v=exchg.141).aspx

    I'm assuming you don't have multiple database copies since you said nothing about it.

    With or without a DAG, however, the method that requires no downtime and least risk is to create a new mailbox database on the new volume and move all the mailboxes to it, then remove the old database.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by David Wang_ Monday, April 25, 2016 7:53 AM
    • Marked as answer by David Wang_ Thursday, April 28, 2016 5:16 AM
    • Unmarked as answer by David Wang_ Thursday, April 28, 2016 5:18 AM
    • Marked as answer by David Wang_ Friday, May 6, 2016 8:32 AM
    Friday, April 22, 2016 2:58 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    The server is back up and running, correct?  The cmdlet is Move-DatabasePath.

    https://technet.microsoft.com/en-us/library/bb124742(v=exchg.141).aspx

    I'm assuming you don't have multiple database copies since you said nothing about it.

    With or without a DAG, however, the method that requires no downtime and least risk is to create a new mailbox database on the new volume and move all the mailboxes to it, then remove the old database.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by David Wang_ Monday, April 25, 2016 7:53 AM
    • Marked as answer by David Wang_ Thursday, April 28, 2016 5:16 AM
    • Unmarked as answer by David Wang_ Thursday, April 28, 2016 5:18 AM
    • Marked as answer by David Wang_ Friday, May 6, 2016 8:32 AM
    Friday, April 22, 2016 2:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    So if I'm understanding you correctly you had to execute a disk upgrade and

    1. During the recovery process it failed to work for some reason

    2. You then instead of determining a way to complete the recovery decided to build a new server, correct?  If so did you already create new mailboxes for the users, get mail flowing and now want to recover the data from the previous Exchange servers database?

    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 --> 2007 --> 2010 --> 2013 --> 2016 with Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp


    Friday, April 22, 2016 3:43 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Agreed with what Ed has suggested above.

    To accomplish this job faster, you can also try using this Exchange manager solution which provides the option to export and import all the required mailbox items into new mailbox database without losing or tempering any content.

    Monday, April 25, 2016 7:09 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Warning Lepide vendor shill post above.  I can't imagine that their product has any value since their employees constantly post phony endorsements under phony names.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, April 25, 2016 8:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am writing to check the status of thread.

    Are above replies helpful to you?

    According to your description, I understand you want to move the database to the new server.

    You can use database portability to move a Microsoft Exchange Server 2010 mailbox database between Exchange 2010 Mailbox servers in the same organization. This can help reduce overall recovery times for various failure scenarios.

    https://technet.microsoft.com/en-us/library/dd876926(v=exchg.140).aspx

    Regards,

    David 

    Thursday, April 28, 2016 5:50 AM