Exchange 2010 High Availability! Database Availability Groups RIP SCC, CCR and SCR

Rest in peace SCC, CCR and SCR!

Exchange 2010 now only supports one method for High Availability, and that's Database Availability Groups, or DAGs for short.

You can have upto 16 Servers in a DAG, and you aren't limited to just two copies of a database like you were with CCR - you can have 2+ or more copies if you so wish. Also all Mailbox Servers that are Members in a DAG don't necessarily have to have all databases log shipped over to each other.

Benefits of Database Availability Groups!

1. You now fail over at the MAILBOX LEVEL. This means you don't fail over an entire cluster anymore. Your Mailbox Server a little over utilized? Then move 1 or 2 Databases over to a lesser used Mailbox Server to stabilize resources.

2. You can have truly multiple copies of a Database! Technically with 3 or more copies you could use Circular Logging and enter into a Backupless state!

3. DAG Servers can stretch AD Sites! Making DR and HA one solution - without having the pain of having to have an SCR Target.

Play with DAG in the released Exchange 2010 BETA.

Powershell cmdlets:

1. New-DatabaseAvailabilityGroup

This creates the DAG

2. Add-DatabaseAvailabilityGroupMember

This adds a Mailbox Server to the DAG

3. New-DatabaseAvailabilityNetwork

This allows you to specify a Network for Log Shipping

and finally, 4. Get-DatabaseAvailabilityGroup

This shows you all available DAGs, it's members and Operational Servers.

It is noted this is all available to do through the Exchange Management Console too for all those still not quite accustomed to Powershell:

It is worth noting you still need a FileShare Witness if you have an even number of Mailbox Servers in the DAG. You specify this at the time of DAG creation.

DAGs also rely on the use of Failover Clustering, so Windows 2008 Enterprise is still needed.

A very very good feature for smaller companies is that you can have Mailbox Servers as members of a DAG and achieve HA with your Mailbox Data and still also have both the Hub Transport and Client Access Server roles on the Server - effectively total HA with the use of just TWO Servers! This does not take into account Active Directory tin, and also you would need Hardware Load Balancing - as Windows NLB is not supported on a Server with Failover Clustering installed.

That's it for now, I will take you through the steps of creating a DAG and multiple copies of a Database is a future post.

Oliver Moazzezi

MVP - Exchange Server

Exchange 2010 Technical information starts to appear on TechNet

Microsoft has kindly already started filling TechNet with Exchange 2010 information



http://technet.microsoft.com/en-us/library/bb124558(EXCHG.140).aspx


Oliver Moazzezi

MVP - Exchange Server

Exchange 2010 BETA released!!!

Grab it here:



http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1898ed2c-2f88-48ac-824e-d3d20fad77d7



I've been playing with it, expect some how to's in the next couple of days.


Oliver Moazzezi

MVP - Exchange Server

More BES 5...

If you are a BlackBerry Alliance Partner why not take a look in the Downloads section today, there may be a treat for you posted on 13/4/9.

http://www.blackberry.com/partnerzone

Daniel

BES 5 documentation

Documentation has appeared for BES 5 on the BlackBerry website, this is great news as there are some cool features that have been missing to date.

http://na.blackberry.com/eng/support/docs/subcategories/?userType=2&category=BlackBerry+Enterprise+Server+for+Microsoft+Exchange

My top 3 are HA, monitoring and administration.

High Availability
To date to achieve HA with BES you needed to buy an additional product, such as Neverfail, and configure hot swap servers. BES 5 includes Neverfail style clustering out of the box, so no more down time for BlackBerry users.

Monitoring
With BES 4.1.5 the BlackBerry Monitoring Service was released, it presented much need statistical information about servers and devices in a web based console. BES 5 builds on this.

Administration
BES 5 administration is all web based, so no more rolling out management tools. The BlackBerry Web Desktop Manager has also been updated and allows users to provision there own devices, so long as they are enabled on BES. There are also now over 400 built in policies to choose from.

Daniel

Exchange 2003 Support lifecycle

It goes into extended support on the 14/4/2009 - next week.

http://support.microsoft.com/lifecycle/Default.aspx?p1=1773


Oliver Moazzezi

MVP - Exchange Server

Migrating SANS for Exchange 2003 A/P clusters

This is usually a really fun late night affair :-)


Here are the basic steps outlined for an easy pain free move:


1. Pause passive node in Cluster Administrator then take passive cluster node offline

2. Add new HBA's

3. Fire up passive node, connect fibre from HBA's to fibre switches on new SAN and configure zoning etc.

4. Present disks to passive node, then re-scan via disk managenet and ensure you've picked up new disks

5. Add drive letters and format

6. Fail cluster over

7. Take cluster offline, add disks as Physical Disk resource in Exchange Resource Group and add disks as a dependancy of SA.

8. Bring cluster online

9. On new passive node repeat steps 1 through to 4.

10. Fail cluster over to ensure both nodes can successfully bring their resources online and see both disks

11. Now just move the databases via ESM to new SAN disks.

12. Quorum is moved in Cluster Administrator

13. EVS disk - I take the cluster offline then copy all EVS data to the new EVS disk.

14. Once that is done remove the EVS disk from Cluster Admin and add the new EVS disk with the original drive letter name. Then bring cluster online.
15. Removing the old SAN hardware - removing the disks from Cluster Admin and then at an appropritate time take each node down and remove legacy HBA's

16. Power down legacy SAN and remove from racking



Oliver Moazzezi

MVP - Exchange Server

Named Properties handling changing in a future RU for Exchange 2007 SP1?

Most excellently written and described in detail here:

http://msexchangeteam.com/archive/2009/04/06/451003.aspx

From the Conclusions statement it appears to be coming in a future Roll Up for SP1!


Oliver Moazzezi

MVP - Exchange Server

Applying an Exchange Service Pack to an Exchange 2007 UM Server

If you have extra language packs installed (very likely if you’re outside of the US!) then you need to first remove them before you can SP Exchange on your UM Server.

To find out the language packs installed you can use the Get-UMServer cmdlet:

Once you have ascertained what ones are installed you use setup to remove them

Command: setup.com /RemoveUMLanguagePack:en-GB

This will remove the en-GB language pack I had installed.

You can then Apply your Service Pack:

Once your SP has been installed correctly. You can re-install your language pack

Command: Setup.com /AddUmLanguagePack:<UmLanguagePackName> /s: d:\<languagepackfilelocation>

Don’t forget to re-select the language on your associated Dial Plans:

Here’s a link to the available Language Packs:

http://www.microsoft.com/downloads/details.aspx?FamilyID=2b3e23a5-57b6-4a11-8954-f8025ea54bad&displaylang=en

Oliver Moazzezi

MVP - Exchange Server

Exchange Remote Connectivity Analyzer (ExRCA) tool Released

Microsoft have just released there Remote connectivity Analyzer tool this allows you to perform testing of your Exchange 2007 services remotely from a web page ! awesome hey

Allows you test ActiveSync, Autodiscovery, Outlook Anywhere connectivity and inbound mail too. Very useful for testing your configuration is setup correctly but can also be used for testing after maintenance has been performed on Exchange to confirm it's all working correctly etc

https://www.testexchangeconnectivity.com/

More information can be found here : http://msexchangeteam.com/archive/2009/03/25/450908.aspx

Enjoy !

Wayne Hollomby