November 2022 Security Updates for Exchange
This week Microsoft released new security updates for the following Exchange versions:
If you have ever been in a situation where you have lost a physical Exchange 2010 server from your DAG then this document is critical to your ability to recover this server. Examples of how this could occur are through OS corruption, accidental overwrite or a true datacenter disaster. Even if you haven’t been in this situation this article will provide the insight to what it takes to recover an Exchange server that had once been a beloved member of your Exchange 2010 DAG.
Just to set the stage, there are very specific steps to the recovery process beginning with a fresh server build. Before we can start building that new server there are some necessary steps to take and these are addressed next. Also, this document assumes that you are running Windows 2008 R2 and that you are recovering all Exchange server roles.
Before Getting Started:
Begin the Recovery:
Note: In my experience it is ok to also apply the latest Windows Updates.
Note: After step 1 and 2 we will set aside this freshly built server to remove the old DAG member from the Exchange organization.
Note: If there were multiple database copies then this command will need to be run for each database copy that existed.
Note: Repeat these steps for each database that used to reside on this server.
Remove the Server from the DAG
Note: The server will remove itself from the cluster even if the error above is received.
Install Exchange 2010 Prerequisites on the Rebuilt Server
Check the Version of Exchange Installed within your DAG
It is very important that you are doing the recovery from the same version of Exchange that is installed across your Exchange environment. If you are not sure, you can check your other DAG members to find this information
Install Exchange 2010 through the Recovery Command
The following steps assume that your Exchange Server software is moved to a network share
Configure the New Server
When reconfiguring the new server it will be important to check your environment against the other servers in your DAG. If possible it is always best to have these things well documented prior to any disaster. I do not recommend restoring any of the following settings from backup.
Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer servername
Set-MailboxDatabaseCopy -identity ‘XDB1\c1xchpws11' -ActivationPreference 2
Note: The Activation preference for each database will vary depending your DAG design.
Bring the Exchange Server Back into Production
By having a well-designed plan for server recovery if a member of your Exchange 2010 DAG is failed is very important to a timely recovery. For additional detail, see the this TechNet Article on how to recover a DAG member server.
Theresa is a Sr. Technical Systems Administrator and has been working as a technical expert in IT for over 18 years. Theresa has her MCSE, CCA and EPIC ECSM certifications. Her areas of expertise are in the areas of Exchange, Active Directory, Lync, SharePoint and Citrix XenApp. She has architected, designed, implemented and led complex projects in all of these areas. She also is a public speaker, speaking at events such as Briforum 2013 and upcoming will be at E2E Virtulization conference in May 2014.