When Exchange administrators install a new version of Exchange Server, it also creates a new database by default. The location of the Exchange database is at the default C drive partition and in a separate folder. When the size of the database grows, and it becomes tricky to manage it, then the user should move the database to new partition drive, which has more space.
But you cannot just copy and paste the database to a new drive. You will need first to dismount the database, move to a different location or drive, and mount it back to Exchange.
When you have decided to move the database, then comes the first challenge to get the location of the database file. An Exchange administrator does not need to interact with the database file directly because all the operations can be performed at the Exchange Admin Center itself. But to move the database, you need to get its location. Here is the location of the default Exchange database file.
If the Administrator has changed the location of the database, then you should run the following cmdlet at Exchange Management Shell to get an actual location.
After running the cmdlet, you will get the details of the name of the database, the entire location of the EDB file, and the transaction log file. The transaction log file records all the activities performed in the database.
Before starting the database move procedure, you should rename the database because the default name of the different database is quite similar to that of other databases and it will be easier to recognize the database if it has a different name.
The original name of the database will change from DB4321 to DatabaseHR. Now, you can go ahead and run the move command.
The above cmdlet will change the location of the database ‘DatabaseHR’ to a different drive and subsequent folders. Now, mount the database back to Exchange Server and start working on it.
As mentioned in the method, the database should remain in the dismounted (offline) state and the user cannot work on it and the time required to complete the task will depend on the size of the database. Till the time the database is not moved entirely to the new location, the user will have to sit idle, and the productive hour will go waste.
If you do not want to disrupt the performance of Exchange Server, then you should create a new database at a different location and copy the mailbox data from the older database to the new database. Here is the cmdlet –
After creating the new database, go to Exchange Admin Center and create a local move request between two databases.
The move request will start and move the chosen mailboxes to the specified target database. The benefit of this procedure is that the user does not face any downtime.
Both the methods to move the Exchange 2016 database to a different drive or location are simple, but they take time and are not suitable for for large migrations. There are chances of data loss. Additionally, the user has to manually restore the database to the Exchange Server 2016. That is why you should use a professional tool which can conduct a safe transfer of data and maintain the data integrity.
Kernel for Exchange Server recovery software can access the Exchange database file, retrieve its information, and migrate to another Exchange database. The process is quite smooth, and the tool provides a full migration report after the migration. So, you can easily migrate mailboxes to a different database using this tool.