Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9877
  • Last Modified:

Exchange Server 2013 Database DAG limitation and maximums

Hi People,

In Exchange Serve 2013, what is the maximum recommended DB size ?
and how many DB per Storage Group or per DAG ?

Because in Exchange Server 2007, one database maximum size recommended is 200 GB for CCR cluster mode.
0
Senior IT System Engineer
Asked:
Senior IT System Engineer
4 Solutions
 
Kash2nd Line EngineerCommented:
The sizing recommendations for Exchange 2010 and 2013 are the same, maximum of 2TB per database.

In 2013, the number of databases you can mount have changed, 5 in Std, but only 50 in Enterprise Exchange 2013. It is 100 in 2010 Enterprise.

some other read here >> http://howexchangeworks.com/2012/11/exchange-2013-enterprise-edition-can-only-mount-50-databases.html
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
2 TB :-o

Is that the recommended mailbox database size ?

so that sounds good, because with just 200 GB MB DB limit, I have to create 12+ Mailbox Database and Storage Groups in CCR 2007.
0
 
NetoMeter ScreencastsCommented:
Hi,

You might find helpful the Exchange 2013 Server Role Requirements Calculator v5.9 (not only when figuring out the DB size):

http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780


There are no storage groups in Exchange 2013 - since Exchange 2010 the DB is an organization object, not a server one.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Simon Butler (Sembee)ConsultantCommented:
As far as I am aware, there are no recommended sizes.
This is because there are many factors that have to be taken in to account.
If you are using a DAG for example, then if you have a large database of 500gb, and have to reseed it, then you are looking at moving a lot of data to do so.
If you were recovering a backup, a 500gb database is a lot of data to recover.

150-200gb is the usual target size even with the later versions of Exchange because it provides a good trade off between having databases of a decent size and quick reseeds and recoveries. I certainly wouldn't design a platform to use 2tb databases.

Simon.
1
 
NetoMeter ScreencastsCommented:
The supported and best practice Database sizes are specified here:

Exchange 2013 Storage Configuration Options

in the "Database and log file choices for the Exchange 2013 Mailbox server role" table, and you have Stand-alone and High Availability DB size best practices.

It really depends on your HA configuration and specific requirements.

Jeff Mealiffe (aka the Perf Guy) has a real life example here:

http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Thakns all !~
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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