Skip to main content

Rebuild an Exchange 2007 server after a crash

 Rebuild an Exchange 2007 server after a crash


Note: 
If Windows wasn't damaged during the crash, it's best to leave the operating system alone. This will save you work, and will also help to preserve some of the things that are unique to that server.
For example, client access servers almost always have SSL certificates installed. These certificates are stored locally on the server and they are not a part of Exchange. Because of this, certificates will have to be reissued unless you're able to preserve the operating system.



If you're rebuilding a damaged Exchange 2007 server, the first thing you need to do is return Windows to a functional state. After reinstalling Windows you must make sure that your server's disk is configured identically to how it was on the failed server.
You also need to install all of Exchange Server's required components, just as you did when you initially installed Exchange 2007. I also recommend that you apply the same set of patches to the OS that were in place before the crash.

After you've installed and configured Windows, you need to attach it to the domain. And it's critical that you do this correctly. Your Exchange Server configuration is tied to the computer account, which is connected to your old server. Before connecting your server to Active Directory, you must reset the computer account.


To reset the computer account, open Active Directory Users and Computers and select the Computers container. Next, right-click on the name of the failed server and select the Reset Account command. Finally, assign your Exchange Server the same name as the failed server and then join the domain as you normally would. Do not delete the old server's computer account. If you do, it will be impossible to rebuild Exchange Server.
After you've properly configured Windows, it's time to rebuild Exchange Server 2007. To begin, insert your Exchange installation media and run the following command:



Code:
Setup.exe /M:RecoverServer
Be sure that your installation media includes the same service pack that was previously installed.
When you execute this command, Setup will:

  1. Check the prerequisite to ensure that all necessary components are installed
  2. Copy Exchange binaries to the server
  3. Use Active Directory to configure the server.

When I first attempted the recovery process, it would not complete because my edge synchronization had broken. A TechNet article advised me to use the Exchange Management Shell (EMS) to remove the edge subscription, then to manually reestablish it once the server was functioning.
At first I was discouraged because the crash had destroyed the Exchange Management Console and Exchange Management Shell. However, I was pleasantly surprised to find that the management tools had been reinstalled and returned to a functional state when I copied the Exchange binaries. This made it easy to use the
Code:
Remove-EdgeSubscription
command to remove my edge subscription. After that, I was able to rerun Setup and rebuild my server.

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...