These release notes provide additional guidance for SolarWinds Failover Engine version 6.7.7.
SolarWinds Failover Engine is a versatile solution providing complete protection for your SolarWinds products. It can be deployed in a LAN for high availability or across a WAN to provide disaster recovery.This flexibility enables SolarWinds Failover Engine to protect your installation of SolarWinds standalone products and associated SolarWinds modules.
New Features -- This release of SolarWinds Failover Engine includes the following new features:
Note: The new features listed below apply only to the 64-bit version of this release and not the 32-bit version. The available 32-bit version retains the original features of SolarWinds Failover Engine v6.7.0.
SolarWinds Failover Engine provides the following protection levels:
Provides continuous availability to end users should a hardware failure or operating system crash occur. Additionally, SolarWinds Failover Engine protects the network identity of the production server, ensuring users are provided with a replica server with the same server name and IP address in the event of a production server failure.
Proactively monitors network availability by polling up to three nodes, ensuring the active server is visible on the principal network.
Ensures the applications and services associated with SolarWinds products and associated modules stay alive on the network.
Proactively monitors system performance and notifies administrators of problems. SolarWinds Failover Engine can also take pre-emptive action to prevent an outage.
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.
SolarWinds Failover Engine v6.7 supports all Orion modules, including:
SolarWinds Failover Engine supports the following operating systems:
Note: SolarWinds recommends installing all Microsoft security updates prior to installation.
Prior to installing the SolarWinds Failover Engine, SolarWinds recommends that you read the appropriate SolarWinds Failover Engine Installation Guide and the SolarWinds Failover Engine Administrator Guide for step-by-step guidance on installing and configuring your SolarWinds Failover Engine. Ensure that you verify that your server environment meets the minimum requirements for the network option (LAN or WAN) selected. These guides also address minimum hardware and software requirements for this release.
To install the SolarWinds Failover Engine:
To uninstall SolarWinds Failover Engine, use the Uninstall or Modify icon on the desktop to initiate the uninstallation process.
The following issues from previous versions of SolarWinds Failover Engine have been fixed.
The following issues may arise in your installation of SolarWinds 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 SolarWinds Failover Engine to allow communication between the primary and secondary servers. For additional information, see "Firewall Connection" in the Troubleshooting chapter of the SolarWinds Failover Engine Administrator Guide.
Restarting SolarWinds Failover Engine server without first shutting down the SolarWinds Failover Engine may cause the server to return in the passive role. You must allow the SolarWinds Failover Engine to shut down gracefully prior to restarting Windows. For more information, see the chapter "Status and Control" in the SolarWinds Failover Engine Administrator Guide.
Performing a Service Pack upgrade does not upgrade the System Plug-in. The System Plug-in must be upgraded separately using the procedure provided in SWREFID-1942.
Installation of Client Tools using a file path longer than 100 characters may cause the installation of Client Tools to fail.
When installing SolarWinds Failover Engine on a non-English OS, although the installation path is displayed in English (for example, C:\Program Files\SolarWinds), the application path may display in the non-English language (for example, C:\Programme\SolarWinds).
Restoring to a non-cloned secondary server results in the following pop-up being displayed: This copy of Windows is not Genuine.
During Installation, if a serialization mismatch is detected, a warning message appears. When OK is clicked to acknowledge the message, Setup fails.
When installing using a single NIC on the Primary server and a single NIC on the secondary server, validate displays a warning message that two NICs are required.
When performing an installation with differing updates/hotfixes on the servers, after restoring the backup file to the Secondary server, the server keeps rebooting.
The Packet filter does not work after a Physical to Virtual Install Clone if VMware Tools were installed; please uninstall VMware Tools before performing the restore to a virtual machine.
Installing SolarWinds Failover Engine when the secondary server is virtual using the Intall-Clone (backup/restore) technique may result in the creation of ghost NICs on the secondary server. Workaround: Refer to SWREFID-2561 for procedures on how to identify and remove ghost NICs.
When resizing the SolarWinds Failover Engine Manager window, some buttons may disappear as a result of the resizing.
Viewing SolarWinds Failover Engine Online Help with Internet Explorer requires Active Scripting to be Enabled in Internet Explorer.
If SolarWinds Failover Engine is installed on Windows Server 2003, and .Net 2.0 is not present, an error occurs when the Log Collector utility is run.
The System Plug-in fails to load on the passive server; the service starts but appears to be deadlocked.
The DNS Update task may fail when run under the System account on the Secondary / active server after switchover.
DNS Update is not querying for the correct zone name.
After a switchover in a WAN deployment, the DNS Update task status is not updated on the Applications: Tasks page until after the applications are started.
When navigating to the Data: Replication page and clicking the Show Summary Of All Out Of Sync Files And Directories button to expand the Out of Sync Summary panel, the panel appears and then minimizes.
When attempting to collect logs via the SolarWinds Failover Engine Diagnostics Configuration Tool, the dialog prompting you to put SolarWinds Failover Engine into the Maintenance Mode is hidden behind the SolarWinds Failover Engine Diagnostics Configuration Tool dialog and prevents you from collecting the logs.
After a switchover of SolarWinds Failover Engine, attempting to run a job task may result in the following error message:
After a switchover of SolarWinds Failover Engine, new Orion 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 Orion NCM, and then specify schedules and add appropriate account information again.
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 the SolarWinds Orion Module Engine service on the passive server.
After restarting the primary or secondary server and using the System Tray on that server to start SolarWinds Failover Engine, the System Tray application may fail.
Installation/loading of the SystemMonitorNFPlugin.dll fails due to an incorrect path.
When IPAM 2.0 Standalone is installed, using SolarWinds Configure wizard resets the Syslog and Trap services to Automatic startup.
|After upgrading from a previous version of SolarWinds Failover Engine, configured Failure Actions |
may not be preserved.
Workaround: Review and if necessary reconfigure Failure Actions.
|Data Rollback - The Create button remains enabled while the create shadow operation is in progress.|
|The 'Warning' pop-up is too wide when failing to open file for exporting.|
|The Event Properties Detail can go blank when a new balloon error is generated.|
|A Full System Check does not mark the system as Out-Of-Sync when extended attributes are present.|
|The user can attempt to add user accounts by connecting to passive servers which will fail because the |
server can’t see the domain.
|The Failover Manager may always show auto-switchover tasks completing in the event log.|
|Alerts and Warning icons don’t replace the green tick on the server, just the whole group.|
|'Failover Prevented' appears twice in the Configure Alerts pane of the Failover Manager.|
|The Failover Manager accepts a blank hostname to mean localhost.|
|File Server Plug-in prevents system tray icon’s Start Group feature from working.|
|Switchover will continue even if pre-start or pre-stop scripts return an error.|
|From the Applications: Summary pane you can uninstall a plug-in while not all servers are connected.|
|Canceling an uninstall of a v6.7.0 kit that was upgraded from 6.6.2 may crash Setup.|
|The Third Recovery Action for services occasionally does not trigger.|
|In some physical environments the packet filter install hangs.|
|Validate cannot proceed if the user enters the wrong credentials the first time.|
|Error messages may appear as question marks on Japanese systems.|
|There are no upper-bounds on accepted percentage conditions in the Application Rules.|
|During installation it is possible to select a network adapter so that it looks selected but is not, so the Next button remains greyed out.|
|If the Network Monitoring targets are not configured then the Network Status shows “-1 missed pings”.|
|The Server Monitoring ping configuration asks for an IP but accepts any input.|
|The drop-down list for "Server Monitoring: Ping Configuration" and "Network Monitoring: Ping |
Configuration" are always empty.
|The Plan Actions only appear on the local Failover Manager.|
|There is no error presented when an unlicensed plug-in fails to install.|
|Managing hundreds of servers can cause the Default Group to disappear in the Failover Manager.|
|The Failover Manager can use a lot of memory if there are 1000s of file filters.|
|The Start Menu/shortcut contains an improper name.|
|This version of SolarWinds Failover Engine does not support downgrading to a previous version. Attempting to downgrade SolarWinds Failover Engine may result in SolarWinds license files being deleted during the downgrade process.|
|The switchover plan may fail after unprotecting and then again protecting an application.|
© 2016 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.