• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 174
  • Last Modified:

Exchange 2013 Database limits

Migrating mailboxes to Exchange 2013 led to 40 % increase in mailbox sizes and therefore had to increase Database limits in Exchange 2013 . Now that mailboxes have been migrated I need to revert the quota limits to original limits. The issue is we will have a lot of unhappy users calling in how to archive and will lead to helpdesk being bombarded with calls.

What is the most efficient way to handle this situation?
0
jose87
Asked:
jose87
  • 3
  • 2
1 Solution
 
Tony GiangrecoCommented:
Here is your exact situation mentioned:

"Apparently there’s quite a lot of overhead within the database that has never been charged against user mailbox quotas. I assume that the until-now-forgotten overhead includes general debris, forgotten messages, bits of email addresses, and similar crud that accumulates over time. The Exchange developers maintain that they are simply being more accurate in mailbox accounting."

"But getting back to mailbox quotas, there’s no increase in the physical database file on disk. All that’s affected is the calculation of how much quota a user mailbox has consumed within the database and therefore how much of that quota remains. According to the Exchange 2013 Preview release notes, the actual difference is in the order of 30 to 40% extra, so a mailbox that is reported to hold 100MB of data in Exchange 2010 will be shown as anything between 130MB and 140MB in Exchange 2013. "

http://windowsitpro.com/blog/exchange-2013-counts-data-within-databases-better-may-affect-user-mailbox-quotas

http://community.spiceworks.com/topic/383232-increase-mailbox-storage-quota-for-a-single-user-exchange-2010

Here is a script to raise the mailbox sizes by OU.
Get-Mailbox -OrganizationalUnit "Marketing" | Set-Mailbox -IssueWarningQuota 209715200 -ProhibitSendQuota 262144000 -ProhibitSendReceiveQuota 293601280 -UseDatabaseQuotaDefaults $false

http://technet.microsoft.com/en-us/library/bb123981(v=exchg.150).aspx

Hope it helps!


Use a powershell script to change the max mailbox size and your users will not be calling as often.
0
 
jose87Author Commented:
Thanks for the articles ,

So the best way to forward is to set individual mailbox limits? I was thinking of a solution in terms of database setting .

Something like warning at 600 MB , prohibit send at 1GB , prohibit send & receive at 1.2GB. This way many of the users will atleast get the message that they have to archive if they are 600+ and will proceed with archival. Will this work ?
0
 
Tony GiangrecoCommented:
If you use the OU method, it updates it for all users.
0
 
Tony GiangrecoCommented:
Have I answered your question completely?
0
 
jose87Author Commented:
I wanted to change database limits , not individually on mailboxes . Gradually brought back to old limits
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now