Exchange 2013 Database Portability Recovery user database (ii)

Case story:

I currently have a set of EXCHAGNE01 and EXCHANGE02 servers in the environment, all of which are all role-mounted exchange2013cu8 systems.

The two servers belong to one DAG group, and due to a special reason, the DAG's failover cluster fails to recover properly, causing the user's mailbox to be inaccessible.

It is found that the passive copy data of the database on EXCHANGE01 is not properly replicated, and the data contents of the database active copy on EXCHAGNE02 are normal.

During this process, the server Dag group does not return to normal and users cannot access the mailbox. You cannot delete either EXCHANGE01 or Exchange02 from a DAG multiple attempts.

In order to restore user access as soon as possible, we deployed a new EXCHANGE04 server in the environment, which is functioning properly and can create new users and database replicas.

We then copied the normal copy of the database on the EXCHANGE02 server to the EXCHANGE04 default database copy directory.

How can this normal database copy be mounted on EXCHANGE04, allowing the user to access the mailbox normally

The solution is as follows:

Move a mailbox database using database portability

https://technet.microsoft.com/zh-cn/library/dd876926 (v=exchg.150). aspx

Database portability is the ability to move a Microsoft Exchange Server 2013 mailbox Database to or mount any other mailbox server in the same organization, which runs Exchange 2013 for a database that has the same version of the data database schema. The previous version of Exchange's mailbox database could not be moved to a mailbox server that is running Exchange 2013. By using database portability, you can increase reliability by eliminating multiple manual steps that could easily lead to errors during recovery. In addition, database portability reduces the total recovery time for various failure scenarios.

When you use database portability to recover a mailbox database, the operating system version, the Exchange Server version on the source, and the target Exchange server must be the same. For example, if an Exchange 2013 mailbox database was previously mounted on a server that is running Windows Server 2012, the database can only be migrated to a server that is running Windows Server 2012 and Exchange 2013 Portability can be used normally.

Database portability

https://technet.microsoft.com/zh-cn/library/dd876873 (v=exchg.150). aspx

Regarding the repair of a database that is already unhealthy, it is guaranteed that the database on the EXCHANGE02 can be ported to Exchange04 normally.

Be sure to restore the mailbox after the database has been mount properly:

1. Verify that the database is in clean shut-down mode (this data is called a)

ESEUTIL/MH "Database file name"

· Ensure that the database file is in clean Shutdown state

2. If the database file is in the dirty shutdown state, we can repair the database file with the following command line:

ESEUTIL/R E01

Note: E01 this check point file matches the name of the check point file in your log folder

3. If the soft recovery fails, you need to run the following command line for hard repair, but there are some data loss scenarios:

eseutil/p "Database file name"

4. Create a new recovery database (B), and make sure that the database mount is normal. Then set the following parameters:

5. Now unload the new database, copy the original data file to the path of the current database folder, then change the B name to C and change the name of a to B. This refers to the name of the EDB file.
6. For the mailbox that is still in the old down NC library, run the following command line to restore to the new database:

Get-mailbox "Mailbox name" | Set-mailbox–database "B"

PS: In fact, if you have not done anything else before, under normal circumstances, we just need to run the following command line for full db recovery:

Get-mailbox–database "A" | Set-mailbox–database "B"

7. If the user mailbox has run the following command line, collect the information for the broken mailbox:

Get-mailboxstatistics–database "B" | Where {$_. Disconnectreason-ne $null} | FL displayname,mailboxguid,database,disconnectreason,identity

8. Run the following command line to connect to the corresponding AD account:

Connect-mailbox-identity "Identity" in the command line above-database b-user "AD username"-alias "Alias"

9. The IS and IIS services need to be restarted after all operation.

Exchange 2013 Database Portability Recovery user database (ii)