Select all Open in new window > Finally, we need to run recoverserver command and install Exchange again on failed server. Sc config NetTcpPortSharing start= auto sc config spooler start= disabled netsh advfirewall set allprofiles state off Select all Open in new window > Once Server is up. Import-Module ServerManager Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server -Restart Launch Powershell in Admin mode and run below commands. > Next install the Exchange 2010 Pre-requisites. > Now download and install Office 2010 Filter Packs 64-bit. Uncheck Registration this connection address in DNS check box. Especially, on the Replication NIC, make sure:įile and Printer Sharing for Microsoft Networks-Disabled Never install the higher version of a service pack or Rollup. > Now download the Rollup that was present on failed server. If you have SP3 on the failed server, get SP3 and extract it. > What do you need? First, the same service pack. If you miss any step, your recovery will fail. Use the same Disk/NIC configuration, with the same computer name and join it to the domain. For DAG you need Enterprise Edition Windows OS. Make sure to use same operating system with same service pack and patches. Find the server>right click>select reset. Launch Failover Cluster Management from another DAG server, expand Nodes>Right Click the Failed Server>Select Evict the server. > Now remove or evict Server2 from the Cluster. Select all Open in new window or check using the EMC. Select all Open in new window If you don't know what the DAG name is, run Remove-DatabaseAvailabilityGroupServer -Identity NADAG1 -MailboxServer Server2 -ConfigurationOnly Select all Open in new window > After the databases are cleaned up, it is time to remove Server2 configuration from the DAG. Remove-MailboxDatabaseCopy "DB1\Server2" Remove-MailboxDatabaseCopy "DB2\Server2" Remove-MailboxDatabaseCopy "DB3\Server2" Best copy paste in a text file, save it as remove.ps1 and run it from EMS from another DAG server. If you have more databases you will need to run the command for each of them. Select all Open in new window Note: You will get a warning, but it will disappear. Clean up failed server/db from AD,Exchange and Cluster configuration. > Launch the Exchange Management Consolve (EMC) from another server and capture the database screenshot with your activation preference. Take screenshots, especially of the NIC configuration so you can compare later. > First document all OS/NIC/Drives related configurations. The Exchange server is crashed due to hardware failure. Here I am using the name Server2 that is part of a DAG named as NADAG1. You have decided to reinstall Exchange with a fresh operating system. This could happen due to operating system patching, a third party tool or even a virus. The Exchange server is up, but Exchange services are not working. So, I am writing this article to provide you real time steps. Several of you might have performed this in your lab, but when it comes to recovering server in actual production environment, we all know how much we struggle. One of them is recovering a failed server in a DAG. Admins might be handling Exchange 2010 database availability group (DAG) Environment every day and if Exchange is configured with proper hardware and software, there is nothing much left for admins to do. However there are few tasks where real expertise required.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |