Exchange Server 2016 Management Series Courseware 44. To add a database copy of a DAG deployment

Official links

Add a Mailbox Database copy https://technet.microsoft.com/zh-cn/library/dd298080 (v=exchg.160). aspx
Configure mailbox Database Copy Properties https://technet.microsoft.com/zh-cn/library/dd351151 (v=exchg.160). aspx
Move Mailbox Database copy of mailbox database path https://technet.microsoft.com/zh-cn/library/dd979782 (v=exchg.160). aspx

In the ECP, select "Server"-"Database" and select a mailbox database Click "Add Database Copy"

Select one server EX1602 to hold another copy of the database.

The operation that is performing the add replica.

The newly added replica server is initially synchronized.

Add complete.

In the ECP, you can see the database that you just added the replica to.

Use PowerShell to see that one copy has been initially synchronized and the other is in sync.

The following two commands allow you to view more detailed information

The key knowledge of official website is excerpted as follows

Manage Mailbox Database Replicas https://technet.microsoft.com/zh-cn/library/dd335158 (v=exchg.160). aspx

Seeding, also known as update, is the process of adding a copy of a blank database or production database to the active database as the destination replica location on another mailbox server in the same DAG. This will be maintained by the server that is the baseline database copy.

Depending on the situation, you can use an automated process or start a manual process seeding database. When a copy of a database is added, the copy is seeded automatically, providing the correct configuration of the target server and storing it. If you want to manually set up a seed database copy and you do not want automatic propagation to occur when you create the replica, you can use the seedingpostponed parameter when you run the Add-mailboxdatabasecopy cmdlet.

If the source and destination servers are on the same subnet and you have configured a replication network that includes the subnet, the replication network will be used.
If the source and destination servers are on different subnets, the client (MAPI) network is used for seeding, even if the replication network containing those subnets is configured.
If the source and destination servers are in different datacenters, the client (MAPI) network will be used for seeding.

Seed setting process

When you start the seeding process by using the Add-mailboxdatabasecopy or Update-mailboxdatabasecopy cmdlet, the following tasks are performed:
Validates the specified database and server, and verifies that the source and destination servers are running Exchange 2016, that they are the same DAG, these two members, and that the specified database is not a recovery database that reads database properties from Active Directory. The database file path is also read.
Prepare to reseed the seed check from the Microsoft Exchange Replication Service on the destination server.
The Microsoft Exchange Replication Service on the target server checks for the existence of the database and transaction log files in the file directory that was read by Active directory in step 1.
The Microsoft Exchange Replication Service Returns state information from the destination server to the management interface from which the cmdlet is run.
If all the primary checks have been completed, you will be prompted to confirm the action before proceeding. If you confirm the action, continue with the procedure. If an error is encountered during the primary check, an error is reported and the operation fails.
Start the seeding operation from the Microsoft Exchange Replication Service on the destination server.
The Microsoft Exchange Replication Service suspends database replication for the active database copy.
The state information for the database is updated by the Microsoft Exchange Replication Service to reflect the state of the seeding.
If the destination server already has no directory for the target database and log files, create them.
The request to seed a database is passed from the Microsoft Exchange Replication Service on the destination server to the Microsoft Exchange Replication Service on the source server that uses TCP. This request for seeding the database and subsequent communication will be performed on a DAG network that has been configured as a replication network.
The Microsoft Exchange Replication Service on the source server initiates an Extensible Storage Engine (ESE) streaming backup through the Microsoft Exchange Information Store service interface.
The Microsoft Exchange Information Store service streams database data to the Microsoft Exchange Replication Service.
The database data is moved from the source server to the Microsoft Exchange Replication Service to the target server of the Microsoft Exchange Replication Service.
The Microsoft Exchange Replication Service on the destination server writes a copy of the database to a temporary directory in the primary database directory named temp-seeding.
The streaming backup operation on the source server ends as it reaches the last row of the database.
The write operation on the destination server is complete, and the database is moved from the Temp-seeding directory to the last location. The temp-seeding directory will be deleted.
On the destination server, the Microsoft Exchange Replication Service Proxy makes a request to the Microsoft Exchange Search service Proxy to mount the content index catalog (if any) of the database copy. If there are obsolete catalog files in the previous instance of the database copy, the mount operation fails, which fires the need to replicate the catalog from the source server. Similarly, a copy of the catalog is required if the catalog does not exist on the new instance of the database copy on the destination server. When you copy a new catalog from a source, the Microsoft Exchange Replication Service instructs the Microsoft Exchange Search service to suspend indexing of the database copy.
The Microsoft Exchange Replication Service on the destination server sends a seed-seeding request to the Microsoft Exchange Replication Service on the source server for the catalog.
On the source server, the Microsoft Exchange Replication Service requests directory information from the Microsoft Exchange Search service and requests a pending indexing operation.
The Microsoft Exchange Search service on the source server returns the search catalog directory information to the Microsoft Exchange Replication Service.
The Microsoft Exchange Replication Service on the source server reads catalog files from the catalog.
The Microsoft Exchange Replication Service on the source server uses a connection across the replication network to move the catalog data to the Microsoft Exchange Replication Service on the directory server. After the read is completed, the Microsoft Exchange Replication Service sends the request to the Microsoft Exchange Search service to restore the indexing operation of the source database.
If there are existing catalog files on any target server in the directory, the Microsoft Exchange Replication Service on the destination server deletes them.
The Microsoft Exchange Replication Service on the destination server writes the catalog data to a temporary directory named Ciseed.temp, until the data is fully transferred.
The Microsoft Exchange Replication Service moves the completed catalog data to the final location.
The Microsoft Exchange Replication Service on the destination server recovers the index search on the target database.
The Microsoft Exchange Replication Service on the destination server returns the completion status.
The final result of the operation is passed to the management interface from which the cmdlet was invoked.

For more It information, you can also follow the public number below:

Zeng Hung Xin's online classroom, has hung Xin da Lecture hall-51CTO College

Http://edu.51cto.com/lecturer/639838.html

Exchange Server 2016 Management Series Courseware 44. To add a database copy of a DAG deployment