Exchange Server 2013 Operations Series--Failure recovery

If the company's mailbox server hangs, we do not do high availability, this time we need to recover the mailbox database as soon as possible, and to ensure that the mailbox normal mail. Now we need to use a backup of the mailbox database, in general, we will back up the database in shared storage, or at least back up on another server. Our approach is to copy the database files inside the store, deploy Exchange on the new server, create a new database, overwrite the source database file into the new database file, and finally port all the users in the source database to the new database.

Enter the following steps:

One, view the situation of the source server:

1, the source server name, the following image:

2, the source server database as follows, we use "DATABASE01" database to do the experiment, the following diagram:

3, in "DataBase01", there are two users: "Zhang San", "John Doe", as shown below:

Use the command to view:

Use the ECP management interface to view:

4, the following view of the source database "Zhang San" and "John Doe" Mailbox situation, as shown below:

"Zhang San" e-mail:

"John Doe" e-mail:

5, we need to take the source server database files out, as shown below:

Second, install the new Exchange Server:

1, when the source server crashes, we need to install a new Exchange server in the same domain network environment, before the installation steps need to be aware of: Rename the new server, the name cannot be the same as the source server name, or you can not install, and need to join the domain, as shown below:

2. Install the roles on the new server, open PowerShell, and execute the following commands, respectively:

Install-windowsfeature rsat-addsinstall-windowsfeature as-http-activation, Desktop-experience, Net-framework-45-features, Rpc-over-http-proxy, rsat-clustering, Web-mgmt-console, WAS-Process-Model, Web-Asp-Net45 , Web-basic-auth, Web-client-auth, Web-digest-auth, web-dir-browsing, Web-dyn-compression, Web-Http-Errors, Web-http-logging, Web-http-redirect, web-http-tracing, Web-isapi-ext, Web-isapi-filter, Web-Lgcy-Mgmt-Console, Web-metabase, Web-mgmt-console, Web-mgmt-service, Web-net-ext45, Web-request-monitor, Web-Server, Web-stat-compression, Web-static-content, Web-windows-auth, WEB-WMI, Windows-identity-foundation–restart

3. Install the following three components sequentially:

Ucmaruntimesetup
Filterpack64bit
Filterpack2010sp1-kb2460041-x64-fullfile-zh-cn

4, install Exchange, here Omit the installation wizard step, if necessary, please review the following blog tutorial:

http://blog.csdn.net/xiezuoyong/article/details/22727189

Once installed, restart the server.

third, restore the database:

1. Copy the source database folder to the new server, as shown below:

2. Verify that the source database is in a clean Shutdown state:

Open EMS and enter the following command:

eseutil/mh "C:\DataBase01\DataBase01.edb"

Review the command execution results to verify that the value of "state" is "clean Shutdown", as shown in the following figure:

If not, execute the following command to repair the database:

eseutil/p "C:\DataBase01\DataBase01.edb"

3. Create a new database "DATABASE02" on the new server:

Open the ECP management interface--"server"--"Database", click "+" Add button, as shown below:

Enter the new database name and select the server, as shown below:

Create a good new database "DataBase02", as shown below:

4, remove the new database, as shown below:

5. Set the new database to "can be overwritten when restoring":

Select "DataBase02" and click "Edit" button, as shown below:

Open the Edit dialog box, select the Maintenance tab, and then tick "can overwrite this database when restoring", as shown in the following figure:

6. Change the source database filename "Database01.edb" to "Database02.edb", as shown below:

7, copy the name of the source database file, overwriting to the new database file "Database02.edb", as shown below:

8. Then reload "DataBase02" as shown below:

9, the last step, the source database "DATABASE01" All users in the migration to the new database "DataBase02" under:

Open EMS to execute the following command:

Get-mailbox-database DataBase01 |where {$_. Objectclass-notmatch ' (systemattendantmailbox|xoledbstemmailbox) '}| Set-mailbox-database DATABASE02

The results of the implementation are as follows:

Verify that the user migration is migrated to "DataBase02" and execute the following command, as shown in the following figure:

iv. verifying new mailbox server data and operating conditions:

1, verify that the user mailbox data is restored, landing "Zhang San" and "John Doe" Mailbox, check the mailbox situation, found that the mailbox data have been restored, as shown below:

2, verify that the mailbox is normal send and receive mail, with "John Doe" mailbox to "Zhang San" send mail, and then log in "Zhang San" Mailbox View, has received new mail, as shown below:

The mailbox recovery has been completed, and the Exchange certificate needs to be re-applied before the user can use it properly.

Original works, reproduced please specify the source: http://blog.csdn.net/xiezuoyong/article/details/40373813