Exchange 2013 Background Database Maintenance

Exchange 2013 uses now 1 MB per sec for the backgroud database maitenance where as in Exchange 2010 it used 5 MB per second per copy this brought down reduction in IOPS. The other factor increase size in checkpoint file to 100 MB where it result to have 50 percent reduction in IOPS on passive copy compared to it’s active copy iops. (In Exchange 2010 the checkpoint file size is 7.5 MB). Hence in one hours it can perform 3.5 GB of data (1 MB *60 Sec * 60 Min)

Background database maintenance I/O is sequential database file I/O associated with checksumming both active and passive database copies. If you using DAS then no need to consider about BDM and if you are using SAN or iSCSI then you need to consider the BDM.

You can also derive the throughput requirment of your Exchange 2013 environment on viewing from Exchange 2013 Calculator on the Role Requirement tab – Background Database Maintenance Throughput Requirements.

Exchange 2013 Calculator

The content maintenance which occurs default between 1 A.M to 5 A.M and Checksum scan which is used to detect possible corruption on every pages in the mailbox databases run 24/7. The other process like defragementation, page zeroing and compacting also runs 24/7. It uses two cycle to perform this operation – StoreMaintenance and StoreDirectoryServiceMaintenance. You can verify them using below powershell command

Get-MailboxDatabase <DatabaseName> | ft Name, BackgroundDatabaseMaintenance, MaintenanceSchedule -AutoSize

If you disable “Enable Background Database Maintenance” then your checksum wills scan the active database during the maintenance period of the database (1 A.M. to 5 A.M.). You can also verify them on checking in the event view application log for the event id 737  Database Maintenance has completed a full pass on database and ESE log event id 732 Online Maintenance Database Checksumming background task completes

Posted in Exchange 2013 BDM, Exchange 2013 SP1 | Tagged , | Leave a comment

Exchange Server 2013 Cumulative Update 6 Released

Microsoft has released Exchange Server 2013 Cumulative Update 6 and it fixed multiple issue compared with CU5.

Download Link:

Please find the list of issues that got resolved on CU6

2991934 Duplicate mailbox folders after migration to Exchange Server 2013
2988229 Hybrid Configuration wizard error “Subtask CheckPrereqs execution failed” for Exchange Server 2013
2986779 EMS takes a long time to execute the first command in an Exchange Server 2013 Cumulative Update 5 environment
2983512 RPC Client Access service crashes on an on-premises Mailbox server in an Exchange Server 2013 hybrid environment
2983426 AutodiscoverSelfTestProbe fails when external URL is not set for EWS virtual directory in Exchange Server 2013
2983423 AutodiscoverSelfTestProbe fails when external URL is not set for ECP virtual directory in Exchange Server 2013
2983422 The ServerWideOffline component is set to Inactive after Exchange Server 2013 prerequisite check fails
2983207 “532 5.3.2” NDR when you send an email message to a hidden mailbox in an Exchange Server 2013 environment
2983066 Removed Default or Anonymous permission for Outlook folders cannot be restored in an Exchange Server 2013 environment
2982769 “Topology service cannot find the OWA service” when you perform an eDiscovery search in Exchange Server 2013
2982763 Mail-enabled public folder accepts email messages from unauthorized users in an Exchange Server 2013 environment
2982762 OAB generation arbitration mailbox can be removed or disabled in an Exchange Server 2013 environment
2982760 The Enter key submits duplicate sign-in forms to Outlook Web App in an Exchange Server 2013 environment
2982759 You cannot access the archive mailbox of a delegated user after enabling MAPI over HTTP
2982017 Incorrect voice mail message duration in an Exchange Server 2013 environment
2981835 You cannot add attachments, delete or move many email messages in bulk in Outlook Web App
2981466 MAPI/CDO client cannot connect to Exchange Server 2013
2977279 You cannot disable journaling for protected voice mail in an Exchange Server 2013 environment
2975599 Exchange Server 2010 public folder replication fails in an Exchange Server 2013 environment
2975003 Calendar item body disappears in Outlook online mode in an Exchange Server 2013 environment
2974339 OAB generation fails if FIPS is used in an Exchange Server 2013 environment
2971270 Blank page after you sign in to Exchange Server 2013 EAC (formerly ECP)
2970040 Folder Assistant rule does not work correctly in an Exchange Server 2013 environment
2965689 EAS device cannot sync free/busy status if an item is created by EWS in an Exchange Server 2013 environment
2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013
2961715 “Something went wrong” error in Outlook Web App may show an incorrect date
2958434 Users cannot access mailboxes in OWA or EAS when mailbox database is removed

For more detail and reference:

Posted in Exchange Server 2013 Cumulative Update 6 Released | Tagged | Leave a comment

Exchange Server 2013 Content Index Replication

Exchange 2013 Content indexThought to share the experience that I had on Exchange server 2013 content index replication. Before going on deep drive let me provide few fundamental detail that need to know for more understanding.

Copy Queue length and Replay queue length:

Copy queue length are the logs files that needs to be copied from active to passive node. When they pass over it utilize the network bandwidth based upon the network that is specified either MAPI or Replication Network

Replay queue length are the number of log files that are moved to Passive and it was hold to get inspected and replayed in the passive mailbox database. They never utilize the network channel as they are processed internally on the server.

JSL Logs: These logs are know as Jet Shadow logs which are in the inspector directory get generated when the replication occurring. These Jet Shadow logs will get renamed to normal logs like EXXXXX.log when the replication for that logs file got completed

Block Mode and File Mode Replication:

File mode replication occurs for the completed log file to get replicated from active to passive database whereas the Block mode replication replicate the logs file that inprogress before it takes 1 MB in size. By default it will be file mode and when they are sync it move to block mode.

To verify the whether they are block or file mode use the below powershell command:

Get-MailboxDatabaseCopystatus | fl Name, ReplicationIsInBlockMode

Replication Port and Protocols: It uses 64327 TCP port for replication. This can be changed using Set-DatabaseAvailability group

Few Important Notes on Exchange 2013 Content Indexing

  • Content indexing is used for indexing the mailbox that are located in the mailbox database.
  • They are used when user searches email while using Outlook online mode.
  • By default the content indexing size will be approx 10% of the mailbox database size.
  • They always use the MAPI network for replication as it can’t be moved to Replication network as per design.
  • To verify the content index error message and amount of content index got completed for the mailbox database use the below powershell commands

Get-MailboxDatabasecopystatus | ?{$_.ContentIndexState -eq “seeding”} | fl Name, ContentIndexSeedingPercent, ContentIndexState, ContentIndexErrorMessage 

  • When you observer the error message as corrupted for the content index follow the below procedure

Stop the MSExchangeFastSearch services – Stop-Service MSExchangeFastSearch
Stop the HostControllerService services – Stop-Service HostControllerService
Rename the content index file
Start the MSExchangeFastSearch services – Start-Service MSExchangeFastSearch
Start the HostControllerService services – Start-Service HostControllerService
Update the content index – Update-MailboxDatabaseCopy <Database Name> -CatalogOnly
Verify the CI status – Get-MailboxDatabaseCopyStatus | Ft Name,contentindexstate, Contentindexerrormessage -Autosize

  • To verify the port number that is utilized for Content indexing ( Most of the time i see the port 3875 is mapped for content indexing)

Get-ItemProperty HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\Search\IndexStatus

Get-MailboxDatabaseCopyStatus -ExtendedErrorInfo | fl name, *Seeding*, *replic*, *index* -AutoSize

  • Although seeding network show Replication network but for content indexing it uses MAPI network. To verify the connection status for the seeding mailbox database.

Get-MailboxDatabaseCopyStatus -ConnectionStatus -ExtendedErrorInfo | fl name, *Seeding*, *replic*, *incoming*, *out* -AutoSize


Posted in Exchange Server 2013 Content Index Replication | Tagged , , , | 7 Comments

Exchange Server 2013 legacyExchangeDN – IsGuidPrefixedLegacyDnDisabled

Today on creating user mailbox found the legacyExchangeDN is added with numbers in front of the alias name. This behaviour is not there in Exchange Server 2007 or 2010.

legacyExchangeDN: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=63e8dcabcae84802b1f03db4d02aa27c-Raji;

This will result on contact sync while using FIM products when it creats proxy address for the X.500 stamping. All the it’s know behaviour of Exchange Server 2013. I tried to disable them  using the below powershell command..but it didn’t work.. 😦

Set-OrganizationConfig -IsGuidPrefixedLegacyDnDisabled $true


On digging much found in the technet article stating “This parameter is reserved for internal Microsoft use” from the technet article –

Posted in Exchange 2010 SP3 | Tagged | Leave a comment

Exchange Server 2013 Performance Counters

The article helps to understand different counter on Mailbox and Client Access Server role in Exchange 2013 Server. I have exported in the spreadsheet divided into

1.  Common Counters in Mailbox and Client Access Server Role

2. Unique Counters present only in Client Access Server Role

3. Unique Counters present only in Mailbox Server Role

You can download them on clicking  Exchange_2013_Perfmon_Counters

The powershell command used to get this report –  Get-Counter -ListSet *msexchange* | Select-Object -ExpandProperty Counter and then played excel to make easier to understand.

Posted in Exchange Server 2013 Performance Counters | Tagged | 1 Comment

Exchange 2013 Microsoft Exchange Writer Status

If you have multiple Exchange servers in your envirnoment and to check the  Microsoft Exchange Writer Status you can try to use the below script. I have used the sysinternal tool PSExec.exe to gather the detail as vssadmin list writer will not able to perform remote execution natively.

Microsoft Exchange Writer Status

Input the server names in the serverlist.txt file

for /f %%a in (c:\Severlist.txt) do (
PsExec.exe \\%%a hostname >> C:\temp\raji\VSSWriter\Output.txt
PsExec.exe \\%%a vssadmin list writers |findstr /l “name: Last error” > C:\temp\raji\VSSWriter\Output.txt >> C:\temp\raji\VSSWriter\Output.txt

Posted in Exchange 2013 SP1, Exchange Server 2013 SP1 Interview Questions | Tagged | Leave a comment

Exchange Sever 2013 Disk Clean Up

When the disk run out of space in Exchange Server 2013. You can follow the below steps to regain the space

Disk   Cleanup


Operating System Files Clean-up

Go to Run – Type – Temp – Delete all the files
Go to Run – Type – %Temp% – Delete all the files
Clear the unwanted profile from the C: Drive
Removed the unwanted file or software packages from the drives

 Log Files Clean-up

Go to Run – Type – Logfiles – Delete all the old files
Go to C:\inetpub\logs – Clear the old log file or you can Zip them

Clean-up Shadow copies

Sometime when the backup fails to leads to create shadow copies and it will not get deleted. These are mostly located on system volume information folder which are read only access. You can delete them on opening the command prompt with administrator previlege

Type the below command and they are case senstive




ThirdParty tool Cleanup

Download the tool TreeSizeFree is just 4 MB exe file which can display the folder size in descending order. No need to install them in the server since it’s .exe file. It makes your job easier to find the folder which carry more disk space.

Posted in Exchange 2007 SP3, Exchange 2010 SP3, Exchange 2013 SP1 | Tagged | Leave a comment