sus42

A Blog on Wndows Server and Microsoft Exchange by Thomas Pätzold

Archive for January 2012

Update Exchange 2010 Infrastructure

leave a comment »


If you are running an Exchange environment, it is necessary to plan the upgrade process of both the operating system and the Exchange system carefully in order to prevent data loss.

In order to do this you have to follow the steps below:

  • Virus scan tool, monitoring and Backup
    • First of all you have to check the prerequisits of the other software components such as the virusscanner, monitoring client or backup client. After you have assured that the components you use are working properly with the installed update you should start the upgrade process.
  • CAS Server
    • After you checked the prerequitsits you are able to start the upgrade process of your Exchange Environment. First of all you should start with the internet-facing Client Access Server roles. After this you can start the upgrade process of the intranet Client Access Server. During the upgrade process it might be possible that not all clients are able to connect to the infrastructure. In order to improve this you should consider using an hardware load balancing system.
  • HUB Server
    • After upgrading the Client Access Server you should upgrade your HUB Servers next.
  • Mailboxserver
    • Now it is time to upgrade your Mailbox servers. Please consider, it might be a diffrence, if you use a single server environment or a Mailboxcluster (Database Availability Group). Basically you should start upgrading the Databaseserver which doesn´t hold any active databases.
  • Edge Transport Server
    • After you have upgraded all other Exchangeservers you should upgrade the Edge Transport Server now.

In order to support the upgrade process of the members of a database availability group (DAG) there are two scripts in the installation folder of Exchange 2010 (usually c:\Program Files\Microsoft\Exchange Server\v14\scripts).

Starting the maintenance mode
In order to start the maintenance mode you should use the script StartDagServerMaintenance.ps1
This script

  • pauses the node so that it couldn´t become the Primary Active Manager
  • suspends database activation on the specified node
  • moves the active database of the designated server to another Mailboxserver in the same DAG

After maintenance is finished you must stop the maintenance mode manually in order to reactivate the specified mailboxserver.

Stopping the maintenance mode
In order to stop the maintenance mode you should use the script StopDagServerMaintenance.ps1. Consider that stopping the maintenance mode dosn´t move the active copy to the prefered Mailboxserver.

Redistribute Active Mailboxdatabase
If you create a new mailboxdatabase in the DAG then you are able to configure the ActivationPreference attribuite of each mailboxdatabase. Based on this setting you are able to move the active mailboxdatabase to its prefered mailboxserver. In order to redistribute the mailboxdatabase use the following script RedistributeActiveDatabases.ps1.

Written by Thomas Pätzold

January 24, 2012 at 9:59 pm

%d bloggers like this: