Thursday, February 28, 2013

Exchange DAG replication using secondary NIC betwene servers on different subnets

Recently I ran into a problem with Exchange 2010 DAG configuration. I needed to replicate databases between servers that were geographically in different sites and were each on their own separate subnets. For this purpose I wanted to use our secondary data line in order to avoid overloading our main production line with replication traffic. DAG was all set and replicating fine over production line but when I disabled replication on main NIC's and enabled it on secondary NIC's routed via secondary data line, Exchange was still pushing replication via primary NIC. Issue resolved after I collapsed DAG network on secondary ISP into a single DAG network adding both near and far subnet into it. Great article that talks just about that particular setup you can find right here:

Tuesday, February 5, 2013

Exchange 2010 view database info powershell commands

Get some info on database in particular size of it:
Get-MailboxDatabase -status | select Servername,name,databasesize

Get whole bunch of info for particular database
Get-MailboxDatabase -identity | fl

Some usefull powershell commands for fixing content index state when failed

Set content index state of particular database in PS:
Set-MailboxDatabase -identity -indexenabled $true

List databases with content index in failed state:
Get-MailboxDatabaseCopyStatus -Server   | ? {$_.contentindexstate -eq "failed"}

Reset search index for particular database ( need to be in script directory - C:\Program Files\Microsoft\Exchange Server\Scripts):
.\ResetSearchIndex.ps1 -force

Update replication of catalog only on database:
Update-MailboxDatabaseCopy -identity \ -CatalogOnly

Update catalog index state only on all failed databases:
Get-MailboxDatabaseCopyStatus -Server em-bk-exmb01  | ? {$_.contentindexstate -eq "failed"} | update-mailboxdatabasecopy -catalogonly