Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Failover Engine (FoE) > Failover Engine 6.4 Release Notes

Failover Engine 6.4 Release Notes

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 12 Votes: 0 Revisions: 3

Updated: 07/23/2010

These release notes provide additional guidance for SolarWinds Orion Failover Engine version 6.4.

Features

The Orion Failover Engine is a versatile solution providing complete protection for your SolarWinds Orion installation. It can be deployed in a LAN for high availability or across a WAN to provide disaster recovery. This flexibility enables the Orion Failover Engine to protect your installation of SolarWinds Orion and associated SolarWinds Orion modules.

Protection

Orion Failover Engine provides the following protection levels:

Server Protection
Provides continuous availability to end users should a hardware failure or operating system crash occur. Additionally, Orion Failover Engine protects the network identity of the production server, ensuring users are provided with a replica server including server name and IP address in the event of a production server failure.
Network Protection
Proactively monitors network availability by polling up to three nodes, ensuring the active server is visible on the principal network.
Application Protection
Ensures the Orion family of products and the Web Console applications and services stay alive on the network.
Performance Protection
Proactively monitors system performance attributes and notifies administrators of problems, the Orion Failover Engine can also take pre-emptive action to prevent an outage.
Data Protection
Intercepts all data written by users and applications, and maintains a copy of this data on the passive server to be used in the event of a failover event.

Supported Modules

Orion Failover Engine supports the following modules:

  • SolarWinds Orion Core Services 2010.0
  • SolarWinds Orion NPM v10.0
  • SolarWinds Orion APM v3.0
  • SolarWinds Orion IPAM v1.6
  • SolarWinds Orion IPSLA Manager v3.5
  • SolarWinds Orion NTA v3.6
  • SolarWinds Orion NCM v6.0
  • SolarWinds Orion EOC v1.2

Supported Operating Systems

Orion Failover Engine supports the following operating systems:

  • Windows Server 2003 x86 Standard or Enterprise, SP1, SP2, and R2
  • Windows Server 2003 x64 Standard R2 and Enterprise SP2 and R2
  • Windows Server 2008 x86 or x64, SP1 and SP2, and R2

Note: SolarWinds recommends installing all Microsoft security updates prior to installation.

Supported Server Architectures

  • Physical to Physical
  • Physical to Virtual
  • Virtual to Virtual

Installing this Version

Prior to installing Orion Failover Engine, SolarWinds recommends that you read the Orion Failover Engine Quick Start Guide and Orion Failover Engine Administrator Guide for step-by-step guidance on installing and configuring your Orion Failover Engine. You must verify that your server environment meets the minimum requirements for the network option (LAN or WAN) selected. These guides also address minimum hardware/software requirements associated with this release.

To install Orion Failover Engine:

  1. Review the installation procedure listed in the Orion Failover Engine Administrator Guide.
  2. Ensure the environment meets the minimum requirements outlined in the Orion Failover Engine Administrator Guide. Verify that firewalls in use will not prevent communications between the primary and secondary servers via the SolarWinds Channel.
  3. Identify installation options.
  4. Download the software.
  5. Install Orion Failover Engine software on the primary server.
  6. Install Orion Failover Engine software on the secondary server.
    • If using the Install-Clone technique, restore the clone image to the secondary server.
    • If using the Pre-Clone technique, install Orion Failover Engine software on the Secondary server.
  7. Allow the secondary server to reboot and run Plug-n-Play.
  8. Perform the Acceptance Verification testing listed in the Orion Failover Engine Quick Start Guide.

Notes:

  • Orion Failover Engine does not support SQL Server installed on the same host with Orion Failover Engine. Orion Failover Engine does not protect SQL Server. If both Orion Failover Engine and SQL Server are installed on the same host and a failover occurs, SQL Server data will be lost.
  • Installation time for Orion Failover Engine can vary depending on the installation technique, architecture, and the volume of data to be protected. SolarWinds recommends that you install Orion Failover Engine after hours or during a scheduled maintenance period.
  • When using Windows 2008, UAC must be disabled for the duration of the installation.
  • The path of the SolarWinds installation folder, Orion Failover Engine, and any protected applications can only contain lower and upper case letters A to Z, digits from 0 to 9, and the following special characters: space \ _ - ( ) . :
  • When configuring management IP addressing, ensure that the management IP address is configured in a different subnet than the principal IP address. If configuring management IP addressing on a Windows Server 2003 installation, ensure that the management IP address is listed first in the binding order. For more information about management IP addressing, see the Management IP Address section of the Orion Failover Engine Administrator Guide.
  • If installing Orion Failover Engine on a web server, you must edit the Website Availability and Website Response Time rules to reflect the monitored web site. Ensure that you change the default settings http://localhost:80 to reflect the IP address and port of the monitored site.
  • In the event that you must repair of a SolarWinds Orion module with Orion Failover Engine installed, follow the procedures outlined in SWREFID-2060.

Uninstalling

To uninstall Orion Failover Engine, use the Uninstall or Modify icon on the desktop to initiate the uninstall.

Windows 2008 users with UAC Enabled may require an Administrator account login. Disabling UAC for the duration of the uninstall will bypass this.

Note: After uninstalling Orion Failover Engine, some files and folders will remain. These are logs and should not be removed as they may later be required for support or troubleshooting purposes.

Known Issues

The following issues may arise in your installation of Orion Failover Engine. These are known issues that are being addressed for a future release.

  • Firewalls protecting the SolarWinds Channel must be disabled prior to installing Orion Failover Engine to allow the primary and secondary servers to communicate. For additional information, see Firewalls in the Orion Failover Engine Administrator Guide.
  • Restarting an Orion Failover Engine server without first shutting down Orion Failover Engine may cause the server to return in the passive role. You must allow Orion Failover Engine to gracefully shutdown prior to restarting Windows. For more information, see Status and Control in the Orion Failover Engine Administrator Guide.
  • When Orion Failover Engine is deployed in an environment where the primary server has a different principal IP address than the secondary server (in a WAN or stretched LAN configuration), the Web Console is unavailable after a switchover or failover. This occurs because the active server's principal IP address changes as the result of a switchover or failover in a WAN or stretched LAN environment and the Web Console is not automatically updated to point to the new IP address. For each of the NPM, NCM, and EOC modules installed, you must run the corresponding Website Configuration Manager and set the IP Address to (All Unassigned).
  • Changes made to the Web Console port number or IP address are not replicated to the passive server. If you attempt to access the Web Console from the passive server, the Web Console is not available. You must manually edit the URL to include the correct new port number or IP address.
  • When SolarWinds Orion Configuration wizard is run, it routinely sets services to Automatic (including protected application services) thereby preventing Orion Failover Engine from managing the starting and stopping of protected application services. To correct the issue, stop and restart Orion Failover Engine on the server to reset the protected application services to Manual. Note: Stopping the protected application is not required. Users will not be interrupted.
  • When starting Orion Failover Engine, the following warning may be logged: Sponsor 'FoE' was not found in the list of ordered sponsors. This warning may be safely ignored.
  • After a switchover of Orion Failover Engine, attempting to run a job task may result in the following error message: No suitable job engine available for job execution. Verify that the principal NIC is listed first in the binding order and wait 5 minutes before running the job task again. The job task should complete successfully.
  • After a switchover of Orion Failover Engine, new NCM jobs created before the switchover are disabled on the new active server. To create NCM jobs on the new active server, navigate to the Scheduled jobs window in NCM and again specify the schedules and add the appropriate account information.
  • Immediately after installation using the Pre-clone install technique or after manually changing the roles of the servers regardless of the installation technique, the SolarWinds Orion Module Engine service fails to stop on the passive server. Reboot the passive server to stop SolarWinds Orion Module Engine service on the passive server.
  • When Orion Failover Engine is installed in an environment with a German version of Microsoft Windows Server 2003, the %ALLUSERSPROFILE%\Application Data\SolarWinds folder is not included in the replication file filters. Manually create an inclusion file filter for %ALLUSERSPROFILE%\Application Data\SolarWinds\** to ensure that the folder is replicated. For information about creating file filters, see the Orion Failover Engine Administrator Guide.
  • If a failover or switchover occurs immediately after upgrading a SolarWinds Orion license, the license data may not be fully replicated from the primary server to the secondary server and may become corrupt. SolarWinds recommends that you wait a number of minutes before performing a switchover after upgrading a SolarWinds Orion license.

Legal

Last modified
19:28, 22 Jun 2016

Tags

Classifications

Public