Validating the destination file paths exchange 2016

Rated 4.87/5 based on 526 customer reviews

The key to keeping your Microsoft Exchange Servers running at their best is to establish a routine of regular maintenance.

Exchange Server performs eleven automated maintenance tasks nightly, but you can schedule the best time for this, and you should verify that the tasks are completing as well as verifying your databases' integrity and percentage of free space.

Here’s an example from my test server: Get-Mailbox Database | fl Name, Edb File Path, Log Folder Path Name : Mailbox Database 2116642217 Edb File Path : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 2116642217\Mailbox Database 2116642217Log Folder Path : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 2116642217 The default location is probably not suitable for your environment, so you would likely want to move this database to the volumes that you’ve provisioned for your Exchange database and log files.

Another common scenario is that the database is growing and the current volume is low on free disk space, so you want to move it to new, larger volume.

The interesting part is that if you managed to successfully run the hybrid wizard, you would expect to have the same success when creating the migration endpoint.

This is a wrong expectation, because in some cases, for example due to firewall configuration (URL filtering or IP restriction), your attempt to create a migration endpoint on Office365 side can fail.

Even so, every version of Exchange requires occasional, regular maintenance.

So here are some tips for keeping your Exchange servers running as smoothly as possible.

After a hybrid setup is deployed, most of the customers will create the migration endpoint in Office365 Exchange Admin Center, as a first step in the migration process.

A mailbox database can be moved, but before you proceed consider that the move requires the database to be dismounted and taken offline, so it will not be accessible by your mailbox users during the move.

This is fine if the server has just been set up and there are no mailboxes on it, but if you’re moving a database with active mailbox users a better option would be to create a new database on the new volume and perform mailbox moves (which are non-disruptive to end users).

Additional tips for ensuring best performance of your Exchange servers include periodically running the Microsoft Exchange Server Best Practices Analyzer (Ex BPA), verifying your backups, and testing your uninterruptible power supplies (UPSs).

Because it's been around for well over a decade, Exchange Server is a mature product, and Exchange Server 2007 seems to be more stable and reliable than its predecessors.

Leave a Reply