Exchange 2013 Database Portability Recovery user database (i)

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

1. First you can see that the mail in the original mailbox is in:

The following operation assumes that the user's original database suddenly crashes and cannot mount access.

2. The user mailbox is in the following DB:

3. Then create a new temporary database temp:

4. Mount New DB:

5. Mount the user to the temporary library: (if the user of the entire database is using Get-mailbox–database "original database name" |set-mailbox–database "temporary database name")

6. Reconfigure the mailbox account, you can find that the mailbox is empty, but the mailbox is in a connected state:

PS: At this point, if you try to open the original configuration account will find the following error message:

7. It can be found that the user's mailbox can send and receive mail normally, but the previous messages are gone:

8. At this point the first stage, even if completed, the user mailbox can basically be used normally. Then the next step is to help the user recover the previous mail.

9. Use the backup to recover the original EDB file

10. Run the following command line to create a new db:

11. The database folder is empty at this time:

12. Mount the DB at this time:

13. You can find that the Recover.edb file was generated at this time:

14. Then dismount the database out:

15. Copy the EDB file recovered from the backup into the new DB folder, copy the original db to a new location and change the copied DB name to recover:

16. Enable the following properties of the database:

. Mount Database

18. Set the mailbox to this database:

19. At this point you can see the user's original message is back:

20. The only thing to do now is to restore the messages in the temporary library to this library:

21. Run the following command line to check the status of the export request. If you find that you have been in a queue state, restart the Replication service:

22. At this point, you can see that the messages are restored:

Exchange 2013 Database Portability Recovery user database (i)