In this video, Robert McMillen demonstrates how database size affects performance and how to properly plan for it. Settings the correct database size is critical to not using too many or too little resources on an Exchange 2016 server application. Having the correct knowledge for this procedure and the reasons behind it will help considerably in your server’s performance.
- [Voiceover] Setting the correct database size is critical to not using too many or too little resources on an Exchange Server 2016. Having the correct knowledge for this procedure and the reasons behind it will help considerably in your server's performance. Setting a maximum mailbox size for the email users is really important, so a few individuals don't end up using all of the available space. So let's start by taking a look at how much space we have. So in this particular case, we have a lot of space.
We have 407 gigabytes free on our C drive, and we have terabytes free where we're actually keeping our databases. So plenty of space means we can let the maximum amount of space be available for our mailbox users. As we're logged into our Exchange admin center, we can set this by going down to where it says Servers, and then highlight the Databases link, and then double-click on the Exchange database that you want to set the limits.
We only have the one database, so we're just gonna go ahead and double-click on that database. Now if we go to the Limits section, we can now see that there are limits that are pre-set by Microsoft for Exchange Server 2016. The first one is issuing a warning at a certain amount of gigabytes, and it's set to 1.9. Then the Prohibit Send at two gigabytes is set. Prohibit Sending and Receiving is set at 2.3 gigabytes, and Keep Deleted Items is set for 14 days, and Keep Deleted Mailboxes for 30 days.
So let's focus just on the Issue the Warning and the Prohibit at the top three settings. If we click the dropdown under Issue a Warning, we can change this to Unlimited. We can do the same with Prohibit Send, and Prohibit Send and Receive. So the Issue a Warning basically just comes up and says if you hit this limit, you're going to be cut off from your email soon if you go much further, whereas the Prohibit Send At and the Prohibit Send and Receive is actually going to keep your email from working altogether.
So if you don't want to have the unlimited, then you can just go ahead and type in the amount that you would like to have in gigabytes. So, for instance, maybe we want more than 1.9. Maybe we wanna issue a warning at five gigabytes, and we're going to prohibit send at 5.1 and send and receive at 5.1 also. Now we know at 5.1 gigabytes we're no longer going to allow our users to send and receive email. If you want, you can set one or the other of the Prohibit Send and Prohibit Send and Receive to a different amount.
We could say that there is an unlimited amount for the Prohibit Send, and the Prohibit Send and Receive, but we could still issue our warning at five gigabytes. When we do this, the users will not be cut off from their email, but they will be constantly reminded that they have too big of a mailbox. We can also set this in a different place. We can set this at the individual user themselves. Let's go over to our recipients, and we see our individual user Administrator that we created when Exchange Server 2016 was installed.
If we double-click on Administrator, we can then look at the mailbox limits that are built in individually. Now, the mailbox limits that are individual are going to override whatever the database store is. So if we want everybody in the database store to have specific limits except for a few individuals, this would be the way to do that. Let's go to our mailbox usage link and you see here we can override what the database defaults are by clicking on Customize Quota.
From here we can change this to a much higher amount, lower amount, or unlimited. And we can do the same for the Prohibit Send or Prohibit Send and Receive. When we're done, we can just go ahead and click Save. By setting limits on email users, you will keep your server performance working at its maximum and avoid causing a crash or other problems with your exchange server.
Join Robert McMillen as he takes you through the process, from preparation, and configuration, to deployment. Along the way, he informs you of new features, so you'll know how the 2016 version compares to 2013 or 2010. This course is designed to provide new or experienced networking professionals the essential steps needed for a successful implementation of Microsoft Exchange Server 2016.
- Upgrading and migrating considerations
- Preparing Active Directory
- Planning for database size, performance, and virtualization requirements
- Creating roles and users
- Transporting with TLS
- Using command-line setup options
- Establishing DLP
- Creating Database Availability Groups
- Troubleshooting synchronization for High Availability databases