Maximum database size Exchange 2013 Standard

Hi,
Does anybody is aware of database size limitation for Exchange 2013 Standard. I remember in older version there was a registry tweak to increase database limits.
Thank you
alfa21

Hi,
This is the official answer :
Supported: Approximately 16 terabytes.
Best practice:
2 terabytes or less.
Provision for 120 percent of calculated maximum database size.
https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
Cordialement,
Mickaël LOPES
Blog : http://lopes.im

Similar Messages

Maximum Database size in exchange 2007

Hi Team,<o:p></o:p>
What is the maximum database size we can have in Exchange server 2007 SP3 RU8 standalone server.<o:p></o:p>
In our environment we have 1800 users hosted on the
exchange 2007 server with DB size(EDB file) of 1.61TB. What is the maximum size it can grow upto. Any response appreciated.
Thanks<o:p></o:p>
Srini<o:p></o:p>

Amit just beat me to posting Harold Wong's article! :-) Since you're currently on 1.61TB the artificial limit has already been adjust via the registry setting mentioned (the article mentioned 50GB though I've seen others mention 250GB). So the maximum limit
is 16TB, but whoever adjusted things to allow your current size may have set the artificial limit as something smaller, so you'd want to check the registry to see what it has been set to in your case.
I'd also echo the comments about database size. Depending on how you handle backups then they may also play a part. Since most backups work on the basis of backing up / restoring the entire database (obviously backing up changes rather than the whole thing
each time), then the event of you needing to restore it's much easier if you have smaller databases to deal with. Splitting your mailboxes across multiple stores will help minimise the time required before you can get some users online again in the case of
a total failure. Also, if you split your mailboxes across 5 databases and then have a problem (for instance corruption) on one of them, then only around 1/5 of your users are effected rather than all of them.

MAXIMUM DATABASE SIZE SUPPORTED BY DERBY

Hi,
What is the maximum database size that Derby supports?
Currently for our application, Oracle is used. We are planning to switch to Derby.
Any Suggestions??
Vijaya

HTTP://DB.APACHE.ORG/DERBY/MANUALS/INDEX.HTML

Large Mail.que database in Exchange 2013

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.
You cant move the queue database with move-databasepath. You have to follow this method:
http://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

What is the best backup plan for Archive Databases in Exchange 2013?

Hi,
We have Exchange 2013 with Hybrid setup with O365.
We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
That too, especially for Archiving DBs
Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
Keeping this in mind how to design the backup policy ?
Manju Gowda

Hi Manju,
you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db
Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
Example:
keep deleted items: 30 days
backup of archive db: every 14 days
restore procedure:
* restore archive DB content
* add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
So it depends more on your process than on a backup principle.
Regards,
Martin

MailboxInSiteFailoverException - OWA session error on database *over (Exchange 2013 SP1)

Hi all, I have noticed an issue with OWA when database(s) are failed over between DAG members. The environments in question (issue can be reproduced in separate implementations of 2013 SP1 all-role servers) are 2 or more DAG members within the same
AD site/subnet. These are also fresh implementations with SP1 and not upgraded. Exchange servers are load balanced via Netscaler.
So to the issue - OWA users experience the below "..MailboxInSiteFailoverException" message when the database copy is activated. Exchange does not immediately proxy the requests to the active database. You can wait several minutes and
the issue is resolved by refreshing the browser or if you recycle the MSExchangeOWAAppPool on both DAG members, the issue is resolved immediately (OWA session re-established on refresh).
Testing so far involved opening multiple OWA sessions and activating a database copy. At that point, upon refresh of the browser the below error is shown (in all test browsers/sessions below) where I would expect any DAG member to be able to proxy
the client request to the active database server immediately (and not after several minutes).
https://netscaler_LB/owa
https://ex2013server-1/owa
https://ex2013server-2/owa

Hi Simon, I have tested with no firewall on the exchange servers and on client machines within the same subnet as the servers. All with the same results.
I can see many ASP.NET 4.0.30319.0 Event ID 1309 logs similar to this and other threads (http://social.technet.microsoft.com/Forums/windowsserver/en-US/c938dda0-b3bc-4544-851e-f27b503cf4ed/exchange-2013-event-id-1309-source-aspnet-40303190).
IIS logs show similar monitoring mailbox issues but I am still currently looking through the logs. Thanks for your input.
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_3ce57cd622aa4655a ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
- 302 0 0 47
2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_2891f9d41af2422e8 ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
- 302 0 0 47

Exchange 2013 - EMC 2013 - View Mailbox Size With Column In EMC - How To View Mailbox Size Exchange 2013?

Is there a way to add a column to show each users mailbox size in the EMC for Exchange 2013 under recipients > mailboxes?
Such a simple tool would be so much easier for administrative purposes.

Hi,
There is no way to add the column of mailbox size back to EAC in Exchange 2013, I don't know why this option is removed and there is no official document explaining this issue.
To get the mailbox size, we can use commands to get it.
Thanks for your understanding.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Public Folder Mailbox causes database failover Exchange 2013

Hi , we are completing a migration from Exchange 2007 to Exchange 2013. All was going swimmingly until we migrated our legacy public folders. Now every now and again ( once a day generally ) the Exchange Database hosting the Public Folder Mailbox
crashes and fails over to another DAG member.
We are using CU5 and our old 2007 server is offline but not removed from the organization yet.
The error message is as follows :
Event ID 1013
The mailbox with mailboxguid "xxxxxxxxxxxx" caused crash or resource outage on database (GUID="xxxxxxxxxxx")
along with :
Event ID 1001
Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?) with a call stack of ( at Microsoft.Exchange.Server.Storage.Common.ErrorHelper.AssertRetail(Boolean
assertCondition, String message)
and :
Event ID 1002
Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?
The Mailbox Guild matches the Public Folder Mailbox GUID and the Database GUID matches the Database where the mailbox is mounted.
The error seems to be the same as this question :
https://social.technet.microsoft.com/Forums/office/en-US/7e823810-29f4-48f2-ad60-37e6ac147d3e/exchange-2013-database-dismounts-unexpectedly
However I'm after a bit more concrete information as to what actually causes this and if an upgrade to CU6 is required. This link appears to suggest moving the mailbox will help. Has anyone else come across this with CU5 and will a mailbox move
correct it ?
http://blogs.technet.com/b/exchange/archive/2014/10/03/those-pesky-lazy-indices.aspx

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Is their a maximum database size for DB2?

Hello,
we got a request from our business to install a new bw system on DB2 V8.2/V9 with an estimated end size of 100 Terabyte. I know, we have to ask our hardware partner, for sizing and this will include, partitioning,... But the first question from my side is "Is their a maximum size for a db2 database installed on aix?" Has anybody experience with such a huge database. At the moment our biggest database is about 1,4 Terabyte.
Regards,
Alexander

Hi Alexander,
A 100TB size sounds ambitious ... any thoughts to when the system will have that size ? It will also be interesting to understand if it's a OLTP or OLAP system.
There is a "theoritical" technical limit on the total size of a database, but that's really beyond reason. Here is how it goes:
A regular tablespace can be no larger than 512GB per DPF partition. A large tablespace can be no larger than 16TB per DPF partition. You can have 32767 tablespaces in a database. You can have up to 999 DPF partitions in a partitioned database server.
Coming from that the current technical limit is:
Non-partitioned database server: 16TB x 32767 tablespaces
Partitioned database server: 16TB x 32767 tablespaces x 999 partitions.
Regards,
Torsten

Unable to move mailbox to newly created database in exchange 2013

Hi, i created a new database in our existing exchange server 2013 sp1 and i was trying to move my mailbox to the newly created one using the EAC. But the mailbox is not getting moved and i am not receiving any errors. Is there anything else i need to do
after creating the database.
Please advise.

Hello
lets play again:
new-moverequest -identity useremailaddress -targetdatabase new database
after two minute get move req log
get-moverequest -identity useremailaddress |get-moverequeststatistics -includereport |fl
or if have got more DC specified one Dc with -domincontroller DCname
sorry my english

What is the best practice on mailbox database size in exchange 2013

Hi,
does anybody have any links to good sites that gives some pros/cons when it comes to the mailbox database sizes in exchange 2013? I've tried to google it - but hasn't found any good answers. I would like to know if I really need more than 5 mailbox databases
or not on my exchange environment.

Hi
As far as I know, 2TB is recommended maximum database size for Exchange 2013 databases.
If you have any feedback on our support, please click
here
Terence Yu
TechNet Community Support

Best practice on mailbox database size & we need how many server for deployment exchange server 2013

Dear all,
We have an server that runs Microsoft exchange server 2007 with the following specification:
4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2
Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
6 mailbox databases
1500 Mailboxes
We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
1500 mailboxes
10GB or 15GB mailbox quota for each user
How many
servers and databases are
required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
Number of the servers:
Number of the databases:
Size of each database:
Many thanks.

You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
2TB is recommended maximum database size for Exchange 2013 databases.
Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

Exchange 2013 - Removing a database and deleting folders but they still reappear!!

Hi
I created a new database and moved all the user mailbox's plus discovery mailbox;s over and all went well, i then unmounted and deleted the old database in ECP and stopped all the exchange services and deleted the old database files and folders from the
C:, i noticed i was still getting some errors with windows backup and after looking around i notice for some reason under program files/microsoft/exchange server/v15/mailbox the old db folder appears with the sub folders 'indexmeta', 'journal' and 'ms', it
seems that the last trace of the old databases is still being used because the date is always todays date! everytime i delete these foldersers they come back!!
I think this is the reason why the windows backup is failing with 'this application will not be available from this backup'
any help would be appreciated!

Hello,
If you want to remove the old database, you can follow this document to do that:
Manage Mailbox Databases in Exchange 2013
http://technet.microsoft.com/en-us/library/jj150580.aspx
Did you enable journal on the old database?
Thanks,
Evan Liu
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Lync Server Integration with Exchange 2013

Hello,
I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled.
So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
Thanks and Regards,
Nash Burns

Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Exchange 2013 Windows Updates Help Please!

Hello
My Setup:
Server01: Server 2012 Standard + Exchange 2013 Standard
Server02: Server 2012 Standard + Exchange 2013 Standard
DAG Enabled.
Well I'm wondering the best way to Install Windows Updates.
Which Server first? the Passive or Active node of Databases?
because after a Windows Update there are reboots required, what is the best practise when installing Windows Updates.
Thank You!

Hi,
There is no order in a DAG because there is no "active server" or "passive server", there is only servers that host either active or passive database copies. So when updating a DAG member you should make sure it is only hosting passive database copies at
the time.
Per my known, if the server need be restarted after installing certain Windows update, I suggest you run the maintenance scripts to avoid some unexpected situation.
Here is a related thread which can help you for your reference.
http://social.technet.microsoft.com/Forums/en-US/ff206f9c-6e39-4bae-ac1d-1b9d9b465854/best-practices-for-patching-exchange-2010-servers?forum=exchange2010
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Maximum database size Exchange 2013 Standard

Similar Messages

Maybe you are looking for