Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Exchange 2013 database portability to restore user database (2)

2025-01-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

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

About the repair of the abnormal database, that is, to ensure that the database on Exchange02 can be ported to Exchange04 normally.

Be sure to make sure that the database is working properly and recover the mailbox after mount:

Confirm whether the database is in clean shut down mode (this data is called A)

Eseutil / mh "database file name"

Make sure the database file is in the state of clean shutdown

If the database file is in the dirty shutdown state, we can repair the database file by running the following command line:

Eseutil / r E01

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

If soft recovery fails, you need to run the following command line for hard repair, but there will be some data loss:

Eseutil / p "database file name"

At this point, create a new recovery database (B) to ensure that the database can be properly mount. Then set the following parameters:

At this point, uninstall the new database, copy the original data file to the path where the current database folder is located, and then change the name of B to C and the name of A to B. This refers to the name of the EDB file. For mailboxes that are still in the numerical control library dropped by the old down, run the following command line to restore to the new database:

Get-Mailbox "mailbox name" | Set-Mailbox-Database "B"

PS: in fact, if nothing else has been done before, normally, we only need to run the following command line for full DB recovery:

Get-Mailbox-Database "A" | Set-Mailbox-Database "B"

If the user mailbox has first run the following command line to collect information about the disconnected mailbox:

Get-MailboxStatistics-Database "B" | Where {$_ .DisconnectReason-ne $null} | fl DisplayName,MailboxGuid,Database,DisconnectReason,identity

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

Connect-Mailbox-Identity "Identity exported from the command line above"-Database B-User "AD user name"-Alias "Alias"

After all operation, you need to restart the IS and IIS services.

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report