Solved

Patching Exchange Server 2007 from the active node and to the passive node

Posted on 2013-05-19
5
436 Views
Last Modified: 2013-05-20
Hi People,

What is the catch or the caveats apart from the few minutes of downtime for the Outlook user if I do the patching for the following clustered Exchange Server box:

Unicast NLB cluster Hub Transport
Start with the Node 1 and then followed by Node 2

Cluster Continuous Replication Mailbox Server
Start with the ACTIVE Node 1 so that after the patching the MBX role is fail over to PASSIVE Node 2

and then the current ACTIVE Node 2 patched to bring the MBX role failed over to PASSIVE Node 1

I know that it is rather weird or unorthodox way to patch it but I try to avoid manually patching the Exchange Server and minimize the amount of downtime (twice  if I start the patching from the passive node to active node).
0
Comment
  • 3
  • 2
5 Comments
 
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 500 total points
ID: 39179316
You are going against best practises and I don't even think it will work.
As soon as you start patching you will cause the active node to failover.

To ensure that you don't have problems with your cluster, follow the guidance - patch the passive node, failover, patch the other one.

Simon.
0
 
LVL 7

Author Comment

by:Senior IT System Engineer
ID: 39179963
Yes I know but when you automate the patching using the patch deployment tool, from the passive node to the active node, then you'll have to do twice failover at least.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39180344
That is going to happen anyway. You cannot avoid doing a failover at least twice unless you don't move the databases back to the previously primary server. If the cluster is working fine then you can do that. I regularly do that with one of my clients with a large CCR deployment.

The platform runs on active on server 1 until the next patching window, goes over to server 2, runs on that server until the next window, then goes back.

Means the client is confident that both nodes are able to do the job.

Simon.
0
 
LVL 7

Author Comment

by:Senior IT System Engineer
ID: 39180382
Yes but the reason I must failover back to the node 1 or the primary node is that the secondary node 2 is off site and the backup take place on the passive node not on the active nod(I'm using EMC Avamar).
0
 
LVL 7

Author Closing Comment

by:Senior IT System Engineer
ID: 39183022
THanks !
0

Featured Post

Courses: Start Training Online With Pros, Today

Brush up on the basics or master the advanced techniques required to earn essential industry certifications, with Courses. Enroll in a course and start learning today. Training topics range from Android App Dev to the Xen Virtualization Platform.

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article runs through the process of deploying a single EXE application selectively to a group of user.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This video discusses moving either the default database or any database to a new volume.

813 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now