How to move the Exchange Server 2016 mailbox Database path method

When Exchange server 2016 is installed, a default mailbox database is created on the server for the administrator, and is placed in the following path of the system disk:

C:Program Filesmicrosoftexchange Serverv15mailbox

Use the following command on our test server to see the default created database name, database file, and log file path:

Get-mailboxdatabase | FL Name,edbfilepath,logfolderpath

Using the system disk as the default storage path for the mailbox database is obviously inappropriate, so it is recommended that you move the Exchange database and log files to a dedicated volume for storage. Also, because the Exchange database and log files are generally growing, their storage volumes suggest using larger free space.

Although the Exchange mailbox database can move locations at any time, you need to take the database offline when you move, which interrupts the user's access. Therefore, the proposal is carefully evaluated in planning. And then start providing services to users after the Exchange mailbox database is properly seated.

Note: The following steps do not apply to mobile DAG member's mailbox database path.

Because the default database name created by Exchange Server 2016 is randomly generated and is very inconvenient for administrators to identify and manage, before moving, I first change the "Mailbox db 2002024058" database name to "DB1" by using the following command:

Set-mailboxdatabase "Mailbox Database 2002024058"-name "DB01"

Now we use the Move-databasepath cmdlet to move the Exchange mailbox database and transaction log files to a new location:

Move-databasepath Db01-edbfilepath D:db01db01.edb-logfolderpath E:DB01

As shown above, according to Microsoft's best practices, it is recommended that you keep the database separate from the transaction log.

When an appeal order is executed, the database is temporarily dismount and the file is automatically reinstalled after it is copied to the new location, and the time of database and log movement depends largely on the database and log file size, source, and destination disk speed.