Tuesday, September 10, 2013

Perform patching/Updates for Exchange 2010 in DAG Environment- Part-6

Perform patching/Updates for Exchange 2010 in DAG Environment- Part-5

Returning an Exchange Server 2010 DAG Member to Production

After verification, if the update was successful and the server healthy then we can be placed back into production.
Re-enable services such as Tend micro, Symantec and data protector for Exchange. Re-enable monitoring agents and alarms for the server.

Set the server’s activation policy back to its original setting.

Now you can view the activation preferences for each database, and manually move active mailbox databases to their preferred server.

Open the Exchange Management Shell and navigate to the scripts folder on the Exchange server

Next run the StopDagServerMaintenance.ps1 PowerShell script.
The script will automatically reverse each of the actions made by StartDagServerMaintenance.ps1 except that it will not move active mailbox databases back to the server.
To move the active mailbox databases you can continue to go to each mailbox server in the DAG and run StartDagServerMaintenance.ps1 and perform your updates.

Rebalance Mailbox Databases in a DAG

When all of the servers have been updated, now we can rebalance the DAG automatically.

 You can see that most of the mailbox databases are active on a single DAG member.
Microsoft gave in build script in Exchange Server 2010 Service Pack 1 that allows you to automatically redistribute mailbox databases to their first activation preference. The script can be found on default path C:\Program Files\Microsoft\Exchange\V14\Scripts.
Now we can use the script for current database distribution among the DAG members.

Run the script parameters to rebalance the mailbox databases based on activation preference  

Finally you can see the each mailbox database in the DAG is now active on its preferred server



The information provided here is done so for information only as per my test LAB experience. So the information given here may not apply to any other environment. Before deploy any changes or updates on production environment first roll out on test environment and monitor for some time and test LAB and Production environment hardware & Software should be same, if changes/update directly deploying on production entirely at your own risk.

No comments:

Post a Comment