SolarWinds - How to Apply Operating System (OS) patches or Hotfixes with Minimal Interruptions

Follow

Summary

This article can be used to apply operating system (OS) patches or hotfixes on a SolarWinds Orion Failover Engine server pair with minimal interruption.


More Information

Orion Failover Engine's unique architecture allows you to install updates to the operating system or apply hotfixes without interrupting end-users. The active/passive server pair allows you to install the update or hotfix on one server and ensure functionality before installing on the other. See the instructions below on how to install an update or hotfix.

Procedure

Before implementing this procedure, ensure that the Automatic Update feature supplied by Microsoft is configured so that Updates are NOT applied automatically.  It is acceptable to allow the updates to be downloaded automatically.

Note: The procedure assumes that Orion Failover Engine is configured with the Primary server as active and both the File System Status and Registry Status are synchronized.

By following the procedure below, it is possible to install the OS updates or hotfixes with minimal interruption.

Patching a Orion Failover Engine server pair without management (backdoor) IP addresses

  1. On the Primary (active) server, launch Windows Update.
  2. Download and install the patches or hotfixes, but DO NOT reboot the server if instructed to do so.
  3. Launch the SolarWinds Orion Failover Manager.
  4. Perform a switchover using the SolarWinds Orion Failover Manager to make the Secondary server active. Note: At this point users may notice a slight interruption to the protected application.
  5. Once switchover has completed, shutdown Orion Failover Engine and select the option 'Do not stop protected applications'.
  6. Reboot the Primary server, if prompted at step 2, to complete the installation of the OS patches or  hotfixes.
  7. Verify all patches and hotfixes are installed properly.
  8. Start Orion Failover Engine on the Secondary server and also on the Primary server if no reboot was required at step 6 allowing the servers to synchronize.
  9. Allow servers to connect and synchronize with the Secondary as active and the Primary as passive.
  10. Once synchronization has completed, launch the Windows Update on the Secondary (active) server.
  11. Download and install the patches or hotfixes, but DO NOT reboot the server if instructed to do so.
  12. Launch the SolarWinds Orion Failover Manager.
  13. Perform a switchover using the SolarWinds Orion Failover Manager to make the Primary server active again. Note: At this point users may notice a slight interruption to the protected application.
  14. Once switchover has completed, shutdown Orion Failover Engine selecting the option 'Do not stop protected applications'.
  15. Reboot the Secondary server, if prompted at step 11, to complete the install of the OS patches or hotfixes.
  16. Verify all patches are installed properly.
  17. Start Orion Failover Engine on the Secondary server and also on the Primary server if no reboot was required at step 15 allowing the servers to synchronize
  18. Allow servers to connect and synchronize with the Primary as active and the Secondary as passive. Note: At this point users may notice a slight interruption to the protected application.
  19. On the Primary (active) server, launch Windows Update again and check for any further updates that may be required.  If additional updates are required, repeat steps 2 to 18

Installing operating system (OS) patches or hotfixes using management (backdoor) IP addresses

  1. On the Secondary (passive) server, launch Windows Update.
  2. Download and install the patches or hotfixes, but DO NOT reboot the server if instructed to do so.
  3. Launch the SolarWinds Orion Failover Manager .
  4. Shutdown Orion Failover Engine selecting the option 'Do not stop protected applications'.
  5. Reboot the Secondary server, if prompted at step 2, to complete the installation of the OS patches or hotfixes.
  6. Verify all patches or hotfixes are installed properly.
  7. On the Secondary (passive) server, launch Windows Update again and check for any further updates that may be required.  If additional updates are required, repeat steps 2 to 6.
  8. Start Orion Failover Engine on the Primary server and also on the Secondary server if no reboot was required at step 5 allowing the servers to synchronize.
  9. Launch the SolarWinds Orion Failover Manager .
  10. Perform a switchover using the SolarWinds Orion Failover Manager  to make the Secondary server active. Note: At this point users may notice a slight interruption to the protected application.
  11. When the switchover is complete, launch Windows Update on the Primary (passive) server.
  12. Download and install the patches or hotfixes, but DO NOT reboot the server if instructed to do so.
  13. Shutdown Orion Failover Engine selecting the option 'Do not stop protected applications'.
  14. Reboot the Primary server, if prompted at step 13, to complete the installation of the OS patches or hotfixes.
  15. Verify all patches or hotfixes are installed properly.
  16. On the Primary (passive) server, launch Windows Update again and check for any further updates that may be required.  If additional updates are required, repeat steps 11 to 15.
  17. Start Orion Failover Engine on the Secondary server and also on the Primary server if no reboot was required at step 14 allowing the servers to synchronize.
  18. Launch the SolarWinds Orion Failover Manager .
  19. Perform a switchover using the SolarWinds Orion Failover Manager  to make the Primary server active again. Note: At this point users may notice a slight interruption to the protected application.


Applies To

All Versions


Related Information

SWREFID - 1933

KBID-1933

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.