none
Manually copy the exchange database .edb file? RRS feed

  • Question

  • Hi,

    SBS 2008, Exchange 2007.

    Our backup is failing (a story for another time).

    I need a backup of our exchange database ASAP and I need to wipe the disk it currently sits on. I thought I would be able to un-mount the database then copy and paste the database onto a different drive, but during the paste section it fails with Invalid MS DOS Function.

    I then tried to move it through the SBS console. I did this when I first got the server to move the database onto the large RAID5 array rather than the OS C: drive. However, this also fails.

    I even tried moving the database through EMC and it also fails.

    Basically, I want some way of backing this database up, then I can get going rebuilding my array :-(

    Please help.



    Friday, September 14, 2012 4:48 PM

Answers

  • On Sat, 15 Sep 2012 14:52:24 +0000, Chris30-UK wrote:
     
    >
    >
    >Update:
    >
    >I found on another page where people were saying if they made this folder on the client PC which I'm running the command and create a registry key it should work. details here:
    >
    >http://social.technet.microsoft.com/Forums/en-GB/exchangesvrmigration/thread/a143664a-71b1-4c64-9928-71ec3ea809c9
    >
    >This did get me passed my initial error but I came up against another one "MAPI exceptionnetworkerror"
    >
    >It turns out this was because my database was unmounted and the MX Information Store was stopped (from when I was trying to copy the .edb file!)
    >
    >Finally, I am able to export the .pst files.
    >
    >
    >
    >EDIT: I've just noticed I'm getting a message at the bottom of the export output which says "Error occurred in the step: Moving messages. This mailbox exceeded the maximum number if corrupted items specified for this move mailbox operation."
    >
    >In the target destination folder I can see all the .pst files I've exported and they all seem like they are the correct file size etc. Should I be worried?
     
    You should be worried. Increase the "-BadItemLimit" value on the
    export-mailbox to some large value. The export stops after exceeding
    the limit.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by Chris30-UK Saturday, September 22, 2012 10:02 AM
    Saturday, September 15, 2012 4:28 PM

All replies

  • you can use eseutil /y to copy the DB, more about that here http://blogs.msdn.com/b/granth/archive/2010/05/10/how-to-copy-very-large-files-across-a-slow-or-unreliable-network.aspx

    However it sounds like you may be having some type of disk related issue and therefore the copy may not be able to complete from the source to the target.  So you may be forced to fix that array issue, i.e. ensure all is seated well, firmware up to date etc, else you may need to recover from backup.


    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

    Friday, September 14, 2012 5:12 PM
  • Hi,

    Thanks for the replies. I don't have a backup to restore from which is why I desperately need to figure out a way of getting a copy of this .edb file.

    I've been told by Dell tech support that my RAID5 is punctured, and the only way I can fix it is by wiping the RAID and recreating it. However, I can't wipe it without backing up the exchange information...


    Friday, September 14, 2012 5:24 PM
  • I've tried using ESEUTIL /Y as instructed here: http://technet.microsoft.com/en-us/library/aa996409(v=exchg.80).aspx but it doesn't work.

    From my exchange server (eg server1) I run:

    ESEUTIL /Y \\server1\d$\mailbox database.edb /D\\server2\d$\mailbox database.edb

    It then says:

    Usage error: Invalid Arguement 'database.edb'. Options must be preceded by '-' or '/'.

    So, it seems like I'm not getting the syntax right but I can't see where I'm going wrong and google isn't being much help.

    Friday, September 14, 2012 5:54 PM
  • Wrap the long file name in quotes i.e.

    ESEUTIL /Y \\server1\"d$\mailbox database.edb" /D\\server2\d$\mailbox database.edb


    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

    Friday, September 14, 2012 8:30 PM
  • Hi Troy,

    Thanks for your reply.

    Do I just wrap the source file path in quotes, or the destination (server2) path as well?


    EDIT: the actual file path to my .edb file is quite long, ie it isn't right under D as the syntax shows. So, I should probably be running:

    ESEUTIL /Y \\server1\"d:\program files\microsoft\exchange server\mailbox\mailbox database.edb" /D\\server2\d$\mailbox database.edb

    Also, on server2, can I just copy it to D: ? using the \\server2\d$\mailbox database.edb path? or should I recreate all the same folders from server 1 and drop it in the same place?

    Sorry for the simply / obvious questions.


    • Edited by Chris30-UK Friday, September 14, 2012 8:49 PM additions
    Friday, September 14, 2012 8:44 PM
  • Both

    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

    Friday, September 14, 2012 9:07 PM
  • On Fri, 14 Sep 2012 17:54:38 +0000, Chris30-UK wrote:
     
    >
    >
    >I've tried using ESEUTIL /Y as instructed here: http://technet.microsoft.com/en-us/library/aa996409(v=exchg.80).aspx but it doesn't work.
    >
    >From my exchange server (eg server1) I run:
    >
    >ESEUTIL /Y \\server1\d$\mailbox database.edb /D\\server2\d$\mailbox database.edb
     
    Do you really have a space in the mailbox database name??? Try
    surrounding the arguments with quotes ('"').
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, September 14, 2012 9:48 PM
  • Thanks for the replies.

    Yes, I have a space in the database name, I think that was the default when I installed it 3 years ago..

    Friday, September 14, 2012 10:05 PM
  • hello,

    Are you dismounting the IS and stopping the Exchange services before copying the database?

    There is a very good utility for copying files, it's called RICHCOPY.

    http://download.microsoft.com/download/f/d/0/fd05def7-68a1-4f71-8546-25c359cc0842//HoffmanUtilitySpotlight2009_04.exe

    Have you tried surrounding the DB file name with quotes as Rich stated?

    If the DB cannot copy, you may have to check the DB or the entire disk for consistency.

    Also, you can try the EXMERGE utility to backup the individual mailboxes into PST files as a precaution if the DB does not copy over.

    http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=49

    You can also set up another Exchange server and move individual mailboxes to it.


    Miguel Fra | Falcon IT Services, Miami, FL
    www.falconitservices.com | www.falconits.com | Blog



    • Edited by Miguel Fra Saturday, September 15, 2012 12:28 AM
    Saturday, September 15, 2012 12:22 AM
  • On Fri, 14 Sep 2012 22:05:40 +0000, Chris30-UK wrote:
     
    >Thanks for the replies.
    >
    >Yes, I have a space in the database name, I think that was the default when I installed it 3 years ago..
     
    The unprotected space is seen as the end of the value. What follows
    the unprotected space is taken to be the next switch identifier.
     
    This should do it:
     
    ESEUTIL /Y "\\server1\d$\mailbox database.edb" /D"\\server2\d$\mailbox
    database.edb"
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Saturday, September 15, 2012 2:19 AM
  • I think the punctured RAID is stopping me copying the .edb file so my new plan is to try and export all mailboxes into .pst files (we only have 15 mailboxes).

    I understand I should use the Exchange Management Shell, but all the guides seem to be doing things a lot of complex than just export all mailboxes. Can someone help with the syntax? I just want to export the .pst files to a separate file server?

    EDIT: On my exchange server logged in as administrator I've tried to run the following cmd in the EMS:

    export-mailbox -identity username -PSTFolderPath C:\PST -Confirm:$false

    Obviously, I swapped username for a real person. I have already created the "PST" folder under C:. The erro I get back is:

    The log file directory 'C:\program files\microsoft\exchange server\logging\migrationlogs' does not exist.

    I've checked manually, and I can see that the folder mentioned does not exist. Should this folder exist? Should this folder be created when I execute this cmd and it is failing? Or something else?

    I appreciate all comments.

    • Edited by Chris30-UK Saturday, September 15, 2012 10:58 AM
    Saturday, September 15, 2012 9:38 AM
  • Update:

    I found on another page where people were saying if they made this folder on the client PC which I'm running the command and create a registry key it should work. details here: 

    http://social.technet.microsoft.com/Forums/en-GB/exchangesvrmigration/thread/a143664a-71b1-4c64-9928-71ec3ea809c9

    This did get me passed my initial error but I came up against another one "MAPI exceptionnetworkerror"

    It turns out this was because my database was unmounted and the MX Information Store was stopped (from when I was trying to copy the .edb file!)

    Finally, I am able to export the .pst files. 

    EDIT: I've just noticed I'm getting a message at the bottom of the export output which says "Error occurred in the step: Moving messages. This mailbox exceeded the maximum number if corrupted items specified for this move mailbox operation."

    In the target destination folder I can see all the .pst files I've exported and they all seem like they are the correct file size etc. Should I be worried?

    • Edited by Chris30-UK Saturday, September 15, 2012 3:20 PM
    Saturday, September 15, 2012 2:52 PM
  • On Sat, 15 Sep 2012 14:52:24 +0000, Chris30-UK wrote:
     
    >
    >
    >Update:
    >
    >I found on another page where people were saying if they made this folder on the client PC which I'm running the command and create a registry key it should work. details here:
    >
    >http://social.technet.microsoft.com/Forums/en-GB/exchangesvrmigration/thread/a143664a-71b1-4c64-9928-71ec3ea809c9
    >
    >This did get me passed my initial error but I came up against another one "MAPI exceptionnetworkerror"
    >
    >It turns out this was because my database was unmounted and the MX Information Store was stopped (from when I was trying to copy the .edb file!)
    >
    >Finally, I am able to export the .pst files.
    >
    >
    >
    >EDIT: I've just noticed I'm getting a message at the bottom of the export output which says "Error occurred in the step: Moving messages. This mailbox exceeded the maximum number if corrupted items specified for this move mailbox operation."
    >
    >In the target destination folder I can see all the .pst files I've exported and they all seem like they are the correct file size etc. Should I be worried?
     
    You should be worried. Increase the "-BadItemLimit" value on the
    export-mailbox to some large value. The export stops after exceeding
    the limit.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by Chris30-UK Saturday, September 22, 2012 10:02 AM
    Saturday, September 15, 2012 4:28 PM
  • Hi , 

    you have only 15 mailbox to export , okay that a small number of mailboxes 

    but you seem to have trouble exporting to PST --

    http://blogs.technet.com/b/exchange/archive/2007/04/13/3401913.aspx

    Export/Import to PST Requirements

    In order to export or import mailboxes to PST files the following requirements must be met:

    • Export/Import to PST must be run from a 32 bit client machine with Exchange Management Tools installed (Version Exchange 2007 SP1 or later). The 32bit requirement comes from a dependency with the Outlook client.
    • Either Outlook 2003 or Outlook 2007 must be installed on the client machine.
    • The user running the task must be an Exchange Organization Admin or an Exchange Server Admin on the server where the mailbox to export/import lives."
    • Also give your self full permissions on those mailboxes 

    then you can preform dial tone recovery

    http://www.outlookexchange.com/Articles/AndersonPatricio/AndersonPatricio_c1p2.asp 

    http://blogs.technet.com/b/dhardin/archive/2009/08/25/simplifying-the-dial-tone-database-recovery-process-in-exchange-2007.aspx

    Rebuild your array

    create now DB -- swap the users back 

    import the PST files again 

    I guess the downtime will be minimum   


     


    • Edited by X-Changer Saturday, September 15, 2012 5:03 PM
    • Proposed as answer by X-Changer Sunday, September 16, 2012 12:48 AM
    Saturday, September 15, 2012 4:52 PM
  • Rich> Thanks for this, I will re-run the export with this key prior to deleting the RAID.

    Ayman> That article on dial-tone recovery looks excellent - I will definitely use it.

    I'll report back once I have the RAID reinitialised and mark all the replies as helpful / as the answer etc.

    thanks everyone

    Monday, September 17, 2012 8:10 AM