I installed new exchange 2013 server on 2012R2 server. I have 35 users on server. I imported from their PST files manually exported from mdaemon. It is about 40GB data. I had problem with database and transaction logs and then I created new DB, enabled circular logging and moved user there to remove white spaces from first db which was also growing very fast. Then I deleted old DB. 

At 9pm it DB was 47GB size. Today in 10am db size is 180GB. it is growth of more than 10GB per hour! I am literaly pulling what is left of my hair because I have no idea what is problem. 

When I tried to move users to third DB exc report back that user is moved but it is still on old DB.

Have anyone anything to say that will help me?

ExMon doesnt work on win2012, best practise tool deosn't exist and I really don't know what to do.

• Edited by Ivica Vujovic Friday, January 31, 2014 11:24 AM

Verify the processor utilization Store.exe in your taskmanager as each store.exe is mapped to single database in Exchange 2013. Map the process id with the Exchange 2013 database

Check out if the mailbox is configured with Auto-response Rule which may have resulted email loop

Check out the logon logonstatistics using the below powershell command

get-logonstatistics |select-object username,Windows2000account,identity,messagingoperationcount,otheroperationcount,progressoperationcount,streamoperationcount,tableoperationcount,totaloperationcount | sort-object totaloperationcount -descending| export-csv LogonStats.csv 

Check out if there is any corrupted mailbox using New-MailboxRepairRequest DetectOnly

Try to gather ActiveSync report and verify the handheld device creates issue on generating the log and DB growth  - http://blogs.technet.com/b/exchange/archive/2012/01/31/a-script-to-troubleshoot-issues-with-exchange-activesync.aspx

Finally check the antivirus and any third party software installed in the exchange server. Try to stop them and monitor it

Check out the email queue in your exchange server  and verify is ther any spam emails- Get-Tranportservice | Get-queue

You can still walk through the below article for reference detail

http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx

Unable to submit online integrity check request for database DBKOV. Failure:An unexpected error occurred while tryin
g to submit the request. Detailed error information follows
Microsoft.Mapi.MapiExceptionInvalidParameter: MapiExceptionInvalidParameter: Queue online isinteg request failed. (hr=0
x80070057, ec=-2147024809)
Diagnostic context:
    Lid: 65256
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 57960   StoreEc: 0x80070057
    Lid: 63101   StoreEc: 0x80070057
    Lid: 1750    ---- Remote Context End ----
    Lid: 61463
    Lid: 36887   StoreEc: 0x80070057
    Lid: 60439
    Lid: 35863   StoreEc: 0x80070057
   at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarn
ings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception i
nnerException)
   at Microsoft.Mapi.ExRpcAdmin.ISIntegCheck(Guid guidMdb, Guid guidMailbox, UInt32 flags, Int32 dbtasks, UInt32[] dbta
skids, String& requestId)
   at Microsoft.Exchange.Management.Tasks.OnlineIntegrityCheckTaskBase.StoreOnlineIntegrityCheck(Guid mdbGuid, Guid mai
lboxGuid, OnlineIntegrityCheckFlags flags, OnlineIntegrityCheckTaskId[] taskIds)
   at Microsoft.Exchange.Management.Tasks.OnlineIntegrityCheckTaskBase.InternalProcessRecord().
    + CategoryInfo          : InvalidOperation: (:) [New-MailboxRepairRequest], OnlineIsIntegException
    + FullyQualifiedErrorId : 702E87C3,Microsoft.Exchange.Management.Tasks.NewMailboxRepairRequest
    + PSComputerName        : exchange.kov.doo.local

I got this error when I tried do get online integrity check.

get-logonstatistics doesn't work on Exchange 2013, MS didn't include it as an Get-Tranportservice:

Get-Tranportservice : The term 'Get-Tranportservice' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
 again.

Hello,

At present, it is not supported that installing exchange 2013 on windows server 2012 R2. Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1.

http://blogs.technet.com/b/exchange/archive/2013/11/20/exchange-server-2013-service-pack-1-coming-in-early-2014.aspx

After you move a mailbox, the mailbox on the source database will be soft deleted. You can use the Remove-StoreMailbox cmdlet to purge the mailbox.

Please use eseutil /mh command line tool to check your database status.

If you have any feedback on our support, please click here

I don't know what you people in Microsoft think about us. I really don't understand why you are release such a mess of software. 

I know it is my mistake not paying attention to that detail but really? Why would you even think to release some half usable software? I got WS2012R2 OEM with server I didn't have choice there.

Also, this is last time I use Exchange solution for mail server. I know it is not that bad solution but I lost entire week trying to figure out problem because you didn't bother to include some usable tools for debugging. 

I solved problem with database growing but what should I do now with transaction logs? Upgraded Exchange to CU1 version but Windows Server Backup still didn't truncate logs after successful backup of entire partitions with logs and database.

Hello,

You enable circular logging after you back up your database successfully, these logs still can't be truncated?

I recommend you check event id to make sure whether the backup is successfully.

If you have any feedback on our support, please click here

 

I checked event for backup and there was no issues. Also in Windows Server Backup panel shows no error, all backups were successfully completed. I have 3 databases and for neither are cleared logs.

Hello,

Did you enable circular logging to purge yoru logs?

If you have any feedback on our support, please click here

Yes I did it, but as it is not recommended solution I would like to solve that permanently with transactional logs.

As I can see I should wait for SP1 for Exchange. Btw, is there any release date soon for SP1?

I checked event for backup and there was no issues. Also in Windows Server Backup panel shows no error, all backups were successfully completed. I have 3 databases and for neither are cleared logs.

Windows Backup by default makes a copy backup, which doesn't help in clearing logs, if you check advanced options (custom backup, advanced settings, vss settings) in windows backup, you can change to full backup and your logs will get cleared