Exchange Server2013 Series 11: Basic database Management

Exchange Server2013 Series 11: Basic database Management

Duffy

A mailbox database is a unit of granularity for creating and storing mailboxes. The mailbox database is stored in the form of an Exchange database (. edb) file. In Microsoft Exchange Server 2013, the deployment succeeds with two databases, typically for ease of administration and maintenance, and our system is dismounted from the database, creating our own database according to the plan. As shown in the following:

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908zrwn.png "width=" 576 "height=" 207 "/>

So is there a place for users to be aware of when creating a database? Reference: http://technet.microsoft.com/zh-CN/library/ee832792 (v=exchg.150). aspx

Each database is simply composed of database files and log files, which can be up to 16TB for the size of its database file. edb, but the best practice is 200GB, so we try to control every. edb file within 200G. It is also recommended to use basic GPT volumes, which are recommended for the allocation unit size for. edb and log file volumes. It is also important to remember that best practices do not require and do not recommend the use of defragmentation, and it is also recommended to disable automatic disk optimization and defragmentation on Windows Server 2012.

To create a database:

This can be used in the EAC interface or using the New-mailboxdatabase command, where the EAC interface is used:

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908lmig.png "width=" 573 "height=" 368 "/>

In the above interface, specify the database name, server, database file path, and log folder path. After the creation succeeds, as shown in:

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908e21c.png "width=" 575 "height=" 368 "/>

But there is only one copy, and we want to have a copy on the DF-DAG02, you need to add the database copy as shown in:

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908k5kn.png "width=" 582 "height=" 411 "/>

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908zqoc.png "width=" 553 "height=" 429 "/>

After the creation is complete, as shown in:

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908etxe.png "width=" 665 "height=" 416 "/>

In this interface, we can see the active state of this database, which is the active node, what the replica server has, there are no errors, and so on.

Suspend, activate, delete operations:

Suspend operation: maintains a disk containing a copy of the database, or a single copy of the database suspended for disaster recovery, that is, the replication between the replicas. Of course, when the database replication is suspended, it can be re-copied through the recovery operation.

Activation action: The process of designating a specific passive copy as a new active copy of a mailbox database. This process is called "Database switchover." The database switchover process involves dismounting the currently active database and loading the database copy into a new active mailbox database copy on the specified server.

Delete operation: These procedures will show how to delete a copy of the mailbox database, not the database directly. You cannot use these procedures to delete the last copy of a mailbox database.

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872908i5nv.png "width=" 674 "height=" 407 "/>

Seeding a database copy

In simple terms, it is the process of synchronizing updates for each copy of a database in a DAG. Microsoft's explanation is that seeding a database copy is a database update operation that adds the database to the destination replica location on other mailbox servers in the DAG. This becomes the baseline database for the replicas maintained by the server.

Depending on the actual situation, seeding can be either an automated process or a manual startup process. When you add a database copy, the copy seed is automatically set, but only if the destination server and its storage are properly configured. Database replicas rarely need to reseed after the initial seeding has occurred.

But if you need to set the seed, it's very simple, in the EAC interface, for example,

However, if you need to reseed, or if you want to manually seed the database copy instead of automatically seeding the copy, you can use the Update Mailbox Database Copy Wizard in the EAC or the Update-mailboxdatabasecopy cmdlet in the Management Shell To perform these tasks. Before seeding a database copy, you must first suspend the mailbox database copy. For example, if you need to seed a database copy on a MBX02, you need to suspend the database copy, click "Hang" in and then save it directly.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872909mjtr.png "height=" 328 "/>

Then click "Update" to set the seed, the current server is df-mbx01, you can specify the source server for seeding, that is, which server is the benchmark, if not specified, is currently processing the active state of the server. Any database copy that is in good condition can be used as a seed source for other copies of the database. But generally avoid the WAN connection and choose a link with the lowest cost.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872909imrj.png "height=" 354 "/>650) this.width=650;" Title= " Image "Style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0px;padding-top:0px; padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http://img1.51cto.com/attachment /201407/20/382644_140587290965lc.png "height=" 321 "/>

After the update succeeds, you see the result as shown:

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872909gbyq.png "height=" 409 "/>

After the update succeeds, the active state of the database is normal, the activity is mounted, the replication queue length is 0, and the content index status is normal.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_14058729091quq.png "height=" 266 "/>

Note: If the database is reported as an error during synchronization, it is possible that there is a problem with the DAG's replication network settings if the network is unblocked, and you can try to debug the replication network by switching to the wrong one, as shown in:

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/20/382644_1405872909cryy.png "height=" 459 "/>

You can stop replication replication and enable replication for the DAG network to troubleshoot. In general, the problem may be that the replication network settings are incorrect.

In addition, synchronization can be achieved by manually copying the offline database files, and the administrator can dismount the active copy of the database and copy the database files to the same location on other mailbox servers in the same DAG. If you use this method, a service outage occurs because the process requires the database to be dismounted. Updating a database copy can take a long time, especially if the replicated database is large or the network latency is severe or the network bandwidth is low. After the seeding process starts, do not close the EAC or the shell until this process is complete. Otherwise, the seed set operation terminates.

This article is from the "Duffy" blog, make sure to keep this source http://dufei.blog.51cto.com/382644/1440667

Exchange Server2013 Series 11: Basic database Management