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

At the end of the year, the server also began to be in a bad mood. I don't know what happened recently, but the copy of the database may fail due to various reasons (such as a hardware failure on the underlying storage system). After addressing the root cause of the failure of the database replica, you need to regenerate the replica, which is the process of creating a new replica of the database by replicating the data of another DAG member that hosts the healthy replica.

To demonstrate how to reset a failed copy of the database, I first caused the failure of one of the databases, as you can see in the output of Get-MailboxDatabaseCopyStatus cmdlet.

Prepare to readjust the database copy

There are many considerations when resewing a copy of the database.

First, the time required to repopulate will depend on the size of the database and the network performance between the source and target servers.

By default, the seed uses the DAG member that hosts the copy of the active database as the source.

If the size of the database is 500Gb, you need to copy 500Gb's database over the network, plus the transaction log file and content index of the database. This may increase the amount of data that needs to be transmitted over the network.

This is unlikely to be a problem if DAG members exist only within a single site connected through a high-speed LAN.

However, this can be a bigger problem if DAG members exist at multiple sites in multiple WAN.

Fortunately, you can reassign a source server for the database, allowing you to select a server with better connectivity, such as another DAG member in the same site as the server with a failed copy of the database.

Use Exchange Administration Center to resend a copy of the database to open Exchange Administration Center and navigate to the server-> database. Select the database with the failed copy.

On the copy of the database that appears to have failed, click the update link.

You can click Browse and specify the source server as needed, otherwise click Save to reset the category from the server that hosts the active copy of the database.

Wait for the operation to complete again.

To use the Exchange Management Shell to resend a copy of the database

We can also use Update-MailboxDatabaseCopy cmdlet to perform reseeding.

The database to be re-entered is entered in the database name server name format, for example:

[PS] C:\ > Update-MailboxDatabaseCopy "MailboxDatabase 2E15MB1"

To specify the source server of the source type, use the-SourceServer parameter.

[PS] C:\ > Update-MailboxDatabaseCopy "MailboxDatabase 2E15MB1"-SourceServer EXMB3

If you receive an error message that log files already exist in the transaction log path of the database, you can use the-DeleteExistingFiles parameter to tell the Exchange server to delete the files before starting to reset the seed.

[PS] C:\ > Update-MailboxDatabaseCopy "MailboxDatabase 2E15MB1"-DeleteExistingFiles

Finally, you can use the-BeginSeed parameter for lengthy backups where you don't want to keep the Exchange management shell open, or if the script is rewritten and you don't want the script to have to wait for re-editing to complete.

[PS] C:\ > Update-MailboxDatabaseCopy "MailboxDatabase 2E15MB1"-BeginSeed

Of course, these parameters can be combined with each other, for example:

[PS] C:\ > Update-MailboxDatabaseCopy "MailboxDatabase 2E15MB1"-DeleteExistingFiles-BeginSeed-SourceServer E15MB3

Monitor the health of database copies

Speaking of monitoring, I found two domineering scripts in the TechNet library, which you can play with.

Script link:

Https://gallery.technet.microsoft.com/office/Database-Availability-9a25e9a1

Script link:

Https://gallery.technet.microsoft.com/scriptcenter/Generate-Health-Report-for-19f5fe5f

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.