No announcement yet.

Microsoft Exchange 2007 SP1 Disaster Recovery

  • Filter
  • Time
  • Show
Clear All
new posts

  • Microsoft Exchange 2007 SP1 Disaster Recovery

    All the following is right if there is no condition when crashed Exchange server is still on the network. If second DC is not on the network as it used to be, it will be necessary to remove a non existing DC as a replication partner from Active Directory. It could be done using Active Directory Sites and Services management console. Otherwise it may be impossible to create any new object in Active Directory due to RID master role replication issue.
    1. Install Server 2003 x64 bit editions on a new machine.
    2. Provide the new server with the same name and IP address as the old Exchange server used to have.
    3. Using Active Directory Users and Computers management console reset an existing Exchange server computer object by right clicking on it and choosing Reset.
    4. Join the domain with the new server.
    Install all the prerequisites on the new server (i.e. .Net Framework 2 or later, MMC3, PowerShell, IIS, KB 931836 , KB 92836. If Unified messaging was part of the old Exchange configuration you may need to install WMEncoder64.exe, KB 917312 and msxml6.msi
    Make sure that all fixed hard drive letters are the same as it used to be on the old server. The size of Data hard drive should be the same or bigger than the original.
    On a new server insert the installation DVD, open Command prompt, type X: press Enter (X it’s a DVD drive letter). Run /m:recoverserver /donotstarttransport. Setup will run precheck first and if everything is fine will automatically continue. If precheck will discover any of the issues then an error message will come up and setup won’t continue.
    Possible errors:
    “The fully qualified domain name (FQDN) of the local computer matches the SMTP address of recipient policy “Default policy”. Setup cannot continue.” For the solution go to Appendix 1.
    “Exchange Server 2007 build or later must be used to perform a recovery for this server”. For the solution go to Appendix 2.
    Since setup is complete successfully, install SP1 (only if it was not already part of the setup build) and all the Rollups, otherwise you may experience an error message -514 later on mounting the database saying that version of Log files is not compatible with Jet version (i.e. Exchange version). When installing SP1 you may also get described above “Default Policy” error message. Check Appendix1 on how to get around that issue.
    Restoring the Database:
    When the system part of restore of the Exchange server is complete we’re ready to start data restore. I used NTBackup for backing up our Exchange server. On the Exchange server run NTBackup.exe then go to advanced mode, choose Restore Wizard, browse to bkf file (exchange backup file) open it and check Exchange\Microsoft Information Store\First Storage Group, verify that Original location is chosen. Click Next, in the Restore To field type the exchange server netbios name (it should be already there). In the Temporary location for log and patch files field type C:\tempfolder, check the Last Restore Set box, click Next. Check Preserve existing volume mount points then Next and Finish. It will restore selected database and replay log files into Exchange server original database location.

    Mounting database:
    On the Exchange server open Exchange Management Console go to Server Configuration – Mailbox. Under Data Management tab expand First Storage Group, locate Mailbox Database right click on it and choose Mount Database. If database successfully mounted repeat the restore operation for the Second Storage Group (this group is used for Public folders which many companies don’t use at all).
    In case when database will not mount follow Appendix3.

    Install Certificate:
    • When you start Microsoft Office Outlook 2007 and then connect to a mailbox that is hosted on a mailbox server that is running Microsoft Exchange Server 2007, you may receive the following security warning message: The name of the security certificate is invalid or does not match the name of the site.”
      By default when you install an Exchange 2007 Client Access Server a self signed certificate is generated so that the Autodiscover and your web services service will work right out of the box. A Self-signed certificate will use exchange server Netbios name or FQDN – and not the Alias – which usually is a part of Commercial Certificate. That’s why the self-signed should be replaced with a commercially available internet trusted certificate. To fix Autodiscover.xml run following commands in the Exchange Power Shell:
    1. Setup you commercial Certificate on the Exchange Client Access Server
    2. In Power Shell run
    Set-ClientAccessServer -Identity CAS_
    exchangeservername -AutodiscoverServiceInternalUri
    3. Set-WebServicesVirtualDirectory -Identity "CAS_exchangeservername\EWS (Default Web Site)" -InternalUrl
    4. Set-OABVirtualDirectory -Identity "CAS_exchangeservername\oab (Default Web Site)" –InternalUrl
    5. Set-UMVirtualDirectory -Identity "CAS_exchangeservername\unifiedmessaging (Default Web Site)" -InternalUrl
    6. On the CAS exchange server open IIS Manager.
    7. Expand the local computer, and then expand Application Pools.
    8. Right-click MSExchangeAutodiscoverAppPool, and then click Recycle

  • #2

    “The fully qualified domain name (FQDN) of the local computer matches the SMTP address of recipient policy “Default policy”. Setup cannot continue.” error when trying to install Exchange server using /m:recoverserver from DVD or install Exchange SP1.
    To change Default Recipient Policyyou can using ADSIedit from the domain controller (ADSIedit is part of Support tols). Open ADSIedit go to CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Recipient Policies double click Default Policy, find the attribute gatewayProxy, click Edit and change [email protected] to [email protected] . Then run setup again.
    “Exchange Server 2007 build or later must be used to perform a recovery for this server” error when running /m:recoverserver. It indicates that you’re using downgraded Exchange install DVD (for example SP1 and a few Rollups have been installed in the production environment which will update the Exchange version and Active Directory. There is a way to get around: On the DC open ADSIedit.msc and browse to CN=Configuration,CN=Services,CN=Microsoft Exchange, CN=Administrative Group,CN=Servers, CN=”your exchange servername” right click on the server –Properties, find serialNumber attribute, click on Edit, add the DVD version of Exchange build(do not remove existing one)
    example: existing Version 8.1 (Build 30240.6), you add Version 8.0 (Build 685.25).
    Run again
    On Exchange Management Console open ToolBox and from the Wellcome screen run Database Recovery Management. From the menu choose Verify Database and Transaction log files. Let it analyze Mailbox Database. Database should be in a Clean Shutdown mode. If it’s in Dirty Shutdown mode follow the Solution instructions.
    One of the possible solutions :Perform soft recovery: Eseutil.exe /R E00/I /LF: logfilespath /S”F:\systempath”


    • #3
      Re: Microsoft Exchange 2007 SP1 Disaster Recovery

      Sorry andrey_ts, what is the reason for these posts?

      If you are posting can you link the source as well? I can't see a question here either?

      Please read this before you post:

      Quis custodiet ipsos custodes?