Exchange 2010
I recently attend some jump start training for Exchange Server 2010, the latest Microsoft Exchange server software. Exchange 2010 is available for download from the Microsoft MSDN website.
Exchange 2010 has some very interesting changes. The first major change is all clients connect to the client access role or CAS role for access to the mailbox server. In prior versions of Exchange 2010 the connections went to the Exchange mailbox server. This is because of some HA features Microsoft built into Exchange 2010. This means the CAS role has become very critical. Microsoft recommends load balancing the CAS role with a hardware load balance such as A10 Networks. You can also used the build in Windows load balancing (WLB), but it is not recommended.
The next major shift is single instance storage is gone. In prior versions of Exchange 2010, if you sent an attachment to 20 users, it would be only stored in the Exchange database once. Not any more. They have encrypted headers and the message body to help reduce the storage needs. This means you have to plan for storage growth. Microsoft has moved to sequential writing of the Exchange 2010 database, this makes writing the database more efficient. It also means less chance for corruption and fragmentation.
Along with the single instance store change, Microsoft is also suggesting you can run Exchange 2010 on a single SATA disk if you desire and do away with backups. Why do you ask? With Exchange 2010 comes the introduction of database availability groups or DAG. With DAG, you can replicate your store to another server easily. Failover can be in 30 seconds. The Store information is stored at the Exchange org level and not at individual servers. Combined with the move of all clients connecting to the CAS role, Exchange HA has become much easier. Microsoft has also achieved a 70% speed increase with Exchange 2010. Most of this improvement is achieved from moving away from single instance store and also with sequential writes.
The final feature we are going to discuss is email archiving. Email Archiving is build into Exchange 2010. A user with have a regular email account and an archive email account. The only issue is they are both located in the same information store. You can import PST files into the archive store with easy. You can also comply with email retention requirements your business might be under.
We are hosting an Exchange 2010 Power Breakfast to discuss all of the changes with Exchange 2010. We are holding this event December 8th 2009 from 8:30 am to 10:30 am. You can register here. You can also call the office at 414-455-0719
Exchange 2010 has some very interesting changes. The first major change is all clients connect to the client access role or CAS role for access to the mailbox server. In prior versions of Exchange 2010 the connections went to the Exchange mailbox server. This is because of some HA features Microsoft built into Exchange 2010. This means the CAS role has become very critical. Microsoft recommends load balancing the CAS role with a hardware load balance such as A10 Networks. You can also used the build in Windows load balancing (WLB), but it is not recommended.
The next major shift is single instance storage is gone. In prior versions of Exchange 2010, if you sent an attachment to 20 users, it would be only stored in the Exchange database once. Not any more. They have encrypted headers and the message body to help reduce the storage needs. This means you have to plan for storage growth. Microsoft has moved to sequential writing of the Exchange 2010 database, this makes writing the database more efficient. It also means less chance for corruption and fragmentation.
Along with the single instance store change, Microsoft is also suggesting you can run Exchange 2010 on a single SATA disk if you desire and do away with backups. Why do you ask? With Exchange 2010 comes the introduction of database availability groups or DAG. With DAG, you can replicate your store to another server easily. Failover can be in 30 seconds. The Store information is stored at the Exchange org level and not at individual servers. Combined with the move of all clients connecting to the CAS role, Exchange HA has become much easier. Microsoft has also achieved a 70% speed increase with Exchange 2010. Most of this improvement is achieved from moving away from single instance store and also with sequential writes.
The final feature we are going to discuss is email archiving. Email Archiving is build into Exchange 2010. A user with have a regular email account and an archive email account. The only issue is they are both located in the same information store. You can import PST files into the archive store with easy. You can also comply with email retention requirements your business might be under.
We are hosting an Exchange 2010 Power Breakfast to discuss all of the changes with Exchange 2010. We are holding this event December 8th 2009 from 8:30 am to 10:30 am. You can register here. You can also call the office at 414-455-0719
Labels: Exchange 2010
posted by JSO Technology LLC at
10:58 PM
|
0 Comments
Links to this post
