Recover Failed/Dead Exchange Server 2013

 

Recover an Exchange Server

You can recover a lost server by using the Setup /m:RecoverServer switch in Microsoft Exchange Server 2013. Most of the settings for a computer running Exchange 2013 are stored in Active Directory. The /m:RecoverServer switch rebuilds an Exchange server with the same name by using the settings and other information stored in Active Directory.

Recovering a lost Exchange server is often accomplished by using new hardware. However, you can also use an existing server.

 

  1. Install Windows OS and give same IP as previous (failed Exchange).

1

 

2. Reset Domain account as shown in below image.

2

 

3. Join Domain with same computer name as previous.

4.Drives letters must be same a previous installation.

You can view previous installation path from adsiedit.msc

 

3

 

 

 

 

  1. Create Drive Letter and Folder path for Datebase(.edb) and logs accordingly. You can get that from Adsiedit.msc

 

And restore .EDB file from backup on that folder.

4

 

5

 

 

 

 

 

  1. Install Exchange 2013 Prerequisites.

 

  1. Install Exchange 2013 with /m:RecoverServer

 

Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

 

 

 

 

6

Now check Exchange Server Services.

Move Database and Log Folder Path in Exchange 2013

Move Database and Log Folder Path in Exchange 2013

To view current list of databases type Get-MailboxDatabase cmdlet in EMS.

1

By default Exchange Database location is under C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\ which is definitely not recommended place to store the Mailbox database.

It is always recommended to store Exchange Database and Logs on a different drive other than C:\ Drive.

 

Here, I will move both database and logs to F drive.

Before you proceed please be aware that:

  • the command must be run while logged on to the mailbox server hosting the database
  • this process requires that the database be dismounted while the move takes place, making it unavailable for mailbox users
  • this process should not be followed for databases that are replicated within a Database Availability Group
  • this process cannot be run at the same time as a backup is in progress

 

Move-Databasepath “Mailbox Database 0587117746″ -EdbFilepath “F:\ExchangeDB\Mailbox Database 0587117746.edb” -LogFolderpath “F:\ExchangeLog”

2

Now let’s verify if the database has changed its location. Run the following cmdlet again.

Get-MailboxDatabase | FL Name,*Path*

3

Great new features in Exchange 2013

Exchange Administration Center: The EAC brings to mind the quote, “You’re riding it, dude!” Yes, I cannot help but think of the line from “Finding Nemo” whenever I think of the new admin console for Exchange. But seriously, the GUI-based EMC (Exchange Management Console) and the Web-based ECP (Exchange Control Panel) are being replaced by a single Web-based UI that is, frankly, my least favorite of all the new Exchange 2013 features. I don’t like Web-based consoles for administration; they always feel clunky and unfriendly. Plus, it has that Metro look, which leaves me cold. We’ll see if I can get used to it.

Exchange architecture revisions: Exchange 2007 and 2010 are broken into five server roles, mainly to address performance issues like CPU performance, which would suffer if Exchange were running as one monolothic application. But Microsoft has made progress on the performance side, so Exchange 2013 has just two roles: Client Access server role and Mailbox server role. The Mailbox server role includes all the typical server components (including unified messaging), and the Client Access server role handles all the authentication, redirection, and proxy services. You can deploy Exchange 2013 with an Exchange 2010 Edge Transport server role but a 2013 Edge role is planned post-RTM.

A new managed store: The store service has been completely rewritten in managed code (C#). Although this change bodes well in terms of higher availability and resiliency, it doesn’t mean the ESE (Extensible Storage Engine) database engine has been replaced with SQL, as many admins would like. Exchange 2013 continues to use ESE as the database engine. But now each database runs in its own dedicated worker process, so a hung process in one database will not cause problems in other databases. Fast Search (an add-on to SharePoint 2010) is also integrated into the managed store for improved search and indexing.

Modern public folders: Rather than just getting rid of public folders (something promised for future releases), Microsoft has embraced them once again. They are no longer managed through the separate Public Folder Management Console; instead, they are managed via the EAC. That makes them public folder mailboxes, which means they use regular mailbox databases. In turn, this means they can be made part of a database availability group for disaster recovery.

Lots o’ PowerShell cmdlets: Although 13 cmdlets have been removed (many having to do with the old public folder management), Exchange 2013 brims with 187 new PowerShell cmdlets. That may not be the final tally when the final version ships next year, but it shows that command-line management tools are still growing. I wasn’t kidding years back when I told everyone to learn PowerShell. It’s not going away.

DLP (data loss prevention): DLP is new in Exchange 2013’s transport rules, but it’s also a continuation of Mail Tips in that it warns users when they may be violating policies meant to prevent disclosure of sensitive data. Such disclosures are usually inadvertent, so the use of DLP-fired reminders lets users be aware when they are putting something like a credit card number or Social Security number in an email. The built-in DLP policies are based on regulatory standards like PCI.

Outlook Web App enhancements: The whole of OWA is redesigned — yay! One awesome feature is support for offline access, which lets users write messages in their browser when offline, then have the messages delivered when they connect to the Internet. OWA supports this feature in Microsoft’s Internet Explorer 10, Apple’s Safari 5, and Google’s Chrome 16 (or later), all of which support the HTML5 local data storage feature. There’s also a new set of UI layouts that users can choose from for desktop, tablet, and smartphone use — a smart approach.

Built-in antimalware: Exchange has had antispam capabilities for quite some time; as of Exchange 2007 you could even choose whether to turn on antispam in the Edge role or in the Hub Transport role. Exchange 2013 extends antispam to a broader set of antimalware capabilities, such as to block phishing attempts.

 

New Features in Exchange Server 2013

Exchange Server 2013 comes with a number of new features as well as improvements on existing features that are already familiar to those who have worked with Exchange Server 2010.

Here are a few of the highlights:

  • Reduction in server roles to just two; Client Access server and Mailbox server
  • New streamlined Outlook 2013 and Outlook Web App user interfaces, and offline access for OWA
  • No more Exchange Management Console, all administration is now performed using the new web-basedExchange Administration Center and the Exchange Management Shell (using PowerShell 3.0)
  • Improvements to high availability features and manageability
  • Public folders are now stored in mailbox databases and can take advantage of Database Availability Groups for replication and high availability
  • Data loss prevention capabilities that can be integrated into Transport Rules