Solved

Exchange 2010 DAG members with different levels of Service packs

Posted on 2014-03-27
3
722 Views
Last Modified: 2014-08-13
All,

I am planning to upgrade my Exchange environment, 1 CAS, 1 HUB and 2 Mailbox servers in a DAG to upgrade to service pack 3. Currently they running without any service pack levels.

Once i upgraded CAS and HUB with Service pack 3, i am thinking to install a new Exchange 2010 SP3 mailbox server and join the existing DAG, add the Databases and move mailboxes to this new mailbox server. Then update service packs on other mailbox servers. Does this work? can i have at least for temporarily run DAG mailbox servers with different levels for service packs?
0
Comment
Question by:stratoman
  • 2
3 Comments
 
LVL 9

Accepted Solution

by:
Mahesh Sharma earned 500 total points
ID: 39959143
Why don't you upgrade all server with SP3 & then introduce new mailbox server with SP3 & create a DAG.

There are some database schema change if you go from the release to manufacturing (RTM) version of Exchange 2010 to Exchange 2010 SP3


Check this article for explanation:
http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
0
 

Author Comment

by:stratoman
ID: 39959317
i was looking for the safest upgrade path.

I was even thinking to build a new server with Exchange 2010 SP3 and create a new DAG and new databases and move users to new database from the exchange 2010 RTM databases.
0
 
LVL 9

Expert Comment

by:Mahesh Sharma
ID: 39959324
Ref: http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx

Database Schema Upgrades
The database schema for Exchange 2010 has been updated in Exchange 2010 SP1. Because SP3 contains all the fixes included in SP2 and SP1, when Exchange 2010 RTM Mailbox servers are upgraded to SP3, the databases are upgraded to the Exchange 2010 SP1 version of the database schema. This database schema upgrade process adds time to the overall service pack upgrade process. During the upgrade, the database is dismounted, and all mailboxes in that database are taken offline. If you're upgrading the Mailbox server from the release to manufacturing (RTM) version of Exchange 2010 to Exchange 2010 SP3, the database upgrade process could take an additional 30 minutes or longer per database. You can track the progress of the database upgrade process by examining event 1185 in the Application event log on the server you're upgrading. After a database has been updated to the Exchange 2010 SP3 schema, it can't be mounted on a RTM Mailbox server.
If you're upgrading from Exchange 2010 SP2 or SP1 to Exchange 2010 SP3, the upgrade process takes less time, because there is no database schema upgrade. In addition, you can safely move a database between servers running Exchange 2010 SP1, SP2 or SP3. Even though you can move databases between mailbox servers running different service pack levels, you should complete the upgrade of all DAG members to the same service pack level without too much delay. We recommend that you minimize the amount of time you have your DAG members running different service pack levels.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A safe way to clean winsxs folder from your windows server 2008 R2 editions
Read this checklist to learn more about the 15 things you should never include in an email signature.
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

713 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question