Remember exchange 2007 had brought 70 percent I/O reduction , now you need to listed this, exchange 2010 has brought another 70 percent or even some more I/O reduction on table which to me the historical change for the product line.
I wanted to congratulate the people behind this hand up great job and ***incredible*** value to the product.
so how the messaging will be redundant with two servers? the key point or the value to see is “automatic, database-level failover capabilities” build into exchange 2010.
new engineering around exchange 2010 brought on a table continuous availability, remember fail over cluster , they in a way build into the product and it is seamless to the administrator.
The new architecture the fail over designed around the mailbox database level instead of Server level.This is known as **Database mobility** think about your mailbox is residing in the database and this database is located in a way amount two servers, if one server goes down, outlook clients will only see a blip and they get redirected to the available exchange server and therefore no mail interruption to the end user.
In a way remember AD and the story multi master replication model and how .DIT database is redundant and therefore if you loose one DC what you can do, get another server up and running run DC promo, hurray, you got .DIT database, your DNS information without suffering.
Think exchange 2010 in a same way. For those of you looking for business justification as I listed in the previous article
In a way if you don't upgrade beside so many build in futures you will be loosing $$$$
Oz Casey Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +