Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Failover Engine (FoE) > Apply operating system (OS) patches or hotfixes on FOE with minimal interruptions

Apply operating system (OS) patches or hotfixes on FOE with minimal interruptions

Created by Mindy.Kerber, last modified by MindTouch on Jun 23, 2016

Views: 22 Votes: 0 Revisions: 4

Overview

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

Environment

All versions of FOE

Steps

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. 

 

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 hot fixes, 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 hot fixes 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 hot fixes, 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. 

  1. Once switchover has completed, shutdown Orion Failover Engine selecting the option Do not stop protected applications.

  2. Reboot the secondary server, if prompted at step 11, to complete the install of the OS patches or hot fixes.

  3. Verify all patches are installed properly.

  4. 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

  5. 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.

  6. 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 hot fixes using management (backdoor) IP addresses 

 

  1. On the secondary (passive) server, launch Windows Update.

  2. Download and install the patches or hot fixes, 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 hot fixes.

  6. Verify all patches or hot fixes 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 hot fixes, 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 hot fixes 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. 

 

Last modified
19:26, 22 Jun 2016

Tags

Classifications

Public