Exchange 2010

Can’t failover DAG DB

  In my Exchange 2010 DAG environment with 2 nodes I received the error that I couldn’t failover a DB to the other node in my DAG cluster. This was caused by the content index was in failed state, to resolve this error I had to run a script like below: “C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\ResetSearchIndex.ps1 MDBNAME” Done!

Exchange 2010

Creating a D.A.G (Database Availability Group)

  A little introduction The HA functions in Exchange have been changed a little bit; LCR, CCR, SCC and SCR are now away and replaced by D.A.G. I think it’s a very cool and great feature with Exchange 2010, maybe the best J it makes it able to create a copy of the database to a different server(s). You are able to have more than one copy of it, so your server1 holds an active copy of DB1, server2 and server3 can hold this database as passive if server1 is…

Continue Reading

Exchange 2003, Exchange 2007

OWA/ActiveSync with Exchange 2007 coexist with Exchange 2003

  In this scenario when have a single Exchange 2003 standard server installed and installed a new server with Exchange 2007 standard with CAS/HUB/MBX role (multi-role server). Our problem was that we had too many users that used OWA and ActiveSync so we couldn’t be without this function. I this case we had 3 different solutions to choose between. 1. Use two different IP addresses; one for the Exchange 2003 OWA/AS and one for the Exchange 2007 OWA/AS 2. Use a front-end firewall like ISA server or something else to…

Continue Reading