Albert Widjaja
asked on
Patching Exchange Server 2007 from the active node and to the passive node
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).
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).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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).
ASKER
THanks !
ASKER