Shulou(Shulou.com)06/03 Report--

The case is about:

I currently have a set of Exchagne01 and Exchange02 servers in my environment, all full-role installed exchange2013CU8 systems.

These two servers belong to the same DAG group, and due to special reasons, there is a problem with the DAG failover cluster and cannot recover properly, resulting in inaccessible user mailboxes.

At present, it is found that the data replication of the passive copy of the database on Exchange01 is not normal, and the data content of the active copy of the database on Exchagne02 is normal.

During this process, the server DAG group cannot return to normal and the user cannot access the mailbox. You can't remove either Exchange01 or Exchange02 from DAG after many attempts.

In order to restore user access as soon as possible, we have newly deployed an Exchange04 server in the environment, which is running normally and can create new users and database replicas.

Then we copy the normal database copy on the Exchange02 server to the default database copy directory of Exchange04.

How to mount this normal copy of the database to Exchange04 so that users can access the mailbox normally

Solutions are as follows:

Use database portability to move mailbox databases

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

Database portability is the ability to move or mount Microsoft Exchange Server 2013 mailbox databases to any other mailbox server in the same organization that runs Exchange 2013 for databases with the same data database schema version. The mailbox database for previous versions of Exchange cannot be moved to a Mailbox server running Exchange 2013. By using database portability, you can improve reliability by eliminating multiple manual steps that can easily lead to errors in the recovery process. In addition, database portability reduces the total recovery time for various failure situations.

When restoring a mailbox database using database portability, the operating system version, the Exchange Server version on the source, and the target Exchange server must be the same. For example, if the Exchange 2013 mailbox database was previously mounted on a server running Windows Server 2012, database portability works only if you migrate the database to a server that is also running Windows Server 2012 and Exchange 2013.

Database portability

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

1. First of all, you can see that the messages in the original mailbox are all there:

The following action assumes that the user's original database suddenly crashes and cannot be mounted and accessed.

two。 The user mailbox is in the following DB:

3. Then create a new temporary database Temp:

4. Mount's newly created DB:

5. Mount the user to the temporary database: (if you are the user of the entire database, use Get-mailbox-database "original database name" | set-mailbox-database "temporary database name")

6. If you reconfigure the mailbox account, you can find that the mailbox is empty, but the mailbox is connected:

PS: if you try to open the original configured account, you will find the following error message:

7. It can be found that at this time, the user's mailbox can send and receive email normally, but all the previous emails are gone:

8. At this time, even if the first phase is completed, the user mailbox can basically be used normally. So the next step is to help users recover their previous emails.

9. Use the backup to recover the original Edb file

10. Create a new DB by running the following command line:

11. The database folder is empty at this point:

twelve。 At this point, Mount the DB:

13. At this point, you can see that the Recover.edb file is generated:

14. At this point, drop the database Dismount:

15. Copy the restored edb file from the backup to 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:

17. Mount database

18. Set the mailbox to this database:

19. At this point, you can see that the user's original email has come back:

20. Now all you have to do is restore the mail from 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 the state of queue, restart the replication service:

twenty-two。 At this point, you can see that those messages have been restored:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.