This Knowledge base article provides information about this specific release of Ipswitch Failover v9.0.1
This release of Ipswitch Failover is a patch release that applies to Ipswitch Failover v9.0 and addresses the loss of Ipswitch Failover registry configuration information caused by upgrading to JAVA 8 Update 60.
A listing of technical documents supporting this version of Ipswitch Failover are contained in IKB #2797 - v9.0 .[n] Ipswitch Failover - Technical Documentation .
Ipswitch Failover 9.0.1 delivers the following key features and benefits:
Dramatically Simplified Deployment
- Centralized Failover Management Service (FMS) facilitates end-to-end deployment of Failover protection pairs and trios via highly automated remote installation and configuration.
Fast deployment of Failover Management Service (<2 mins) and Failover protection pairs (<20 mins across most V2V installs)
Note : The above numbers are based on a typical VM with a 20 GB disk. Effective deployment time will vary depending on size of disks being cloned to the Secondary node. P2V cloning and deployment times might take longer.
- Automated creation of Secondary nodes associated with V2V and P2V cloning facilitated via integration with VMware vCenter Server and VMware Converter, respectively.
- Automatic deployment of application plug-ins (MoveIT Central, SQL Server, Fileserver, and IIS)
- Single NIC and Dual NIC configuration for public and channel networks
- Multiple concurrent remote Ipswitch Failover deployments can be executed in parallel.
- Fast deployment of Failover Management Service (<2 mins) and Failover protection pairs (<20 mins across most V2V installs)
Complementary add-on value to VMware solutions
Deep integration of Ipswitch Failover with VMware vSphere enables the following incremental recovery actions for end-users in the event of application degradation or failures (in addition to traditional recovery actions):
- Trigger HA restarts – lends true application awareness to VMware HA
- Migrate VM to alternative vSphere ESX host or datastore (for example, trigger vMotion, enhanced vMotion or Storage vMotion)
- Integration with VMware SRM (Site Recovery Manager) enables P2V DR facilitating recovery of virtual copies of physical servers at the DR site as part of the SRM recovery plans.
- Deep integration of Ipswitch Failover with VMware vSphere enables the following incremental recovery actions for end-users in the event of application degradation or failures (in addition to traditional recovery actions):
- Ipswitch Failover Manager provides a native Web Client and the legacy vSphere (thick C#) Client
- Advanced Failover management controls are available via the Ipswitch Failover Manager
- The Ipswitch Failover Manager provides automated deployment with basic switchover and failover capability
- Ipswitch Failover installs with a default 30-day evaluation license
- Activate License wizard allows for validation of Ipswitch license files to authorize Ipswitch Failover deployments
Plus core capabilities of Heartbeat, including:
- Continuous application availability with near-zero RPO and <2 mins RTO
- Built-in application level and data replication - eliminating the need for shared storage or expensive storage replication software
- Proactive application health monitoring to detect application failure patterns before they occur and thereby prevent failures
- Built-in WAN Acceleration via WANSmart features
- Built-in data protection via integration with VSS snapshots to rollback application data on recovery to an earlier point in time
Additional Detailed Information
- Ipswitch Failover v9.0.1 Quick Start Guide
- Ipswitch Failover v9.0.1 Installation Guide
- Ipswitch Failover v9.0.1 Administrator’s Guide
Supported Deployment Infrastructure
Server roles/applications for which protection will be installed automatically are:
- MOVEit Central v8.0 for x86, 8.1 for x64
- MOVEit DMZ v8.1
- SQL Server 2008 R2 SP2, SQL Server 2012 SP1
- File Server
- Internet Information Server
Additional supported plug-ins
- Ipswitch Failover for Business Application
For information about pre-requisites for deploying Ipswitch Failover v9.0.1, refer to the following:
- Ipswitch Failover v9.0.1 Installation Guide
- Provide a 30 day evaluation capability for a pair/trio without any licenses for any product (EN-834).
- Create auditable licenses issued to Ipswitch (EN-838).
- Create auditable licenses issued to customers (EN-839).
- Implement plug-in changes to support Ipswitch MOVEit Central 8.1 x64 (EN-852).
- Attempting to download the Advanced Management Client via the Failover Management Service User Interface results in Error #2308 (EN-1300) .
Ipswitch Failover Web Manager
After successfully deploying the Primary server and attempting to deploy the Secondary virtual machine, the deployment fails with the message: Creating VM. 100% Timed-out waiting for SECONDARY VM to complete auto-configuration.
Workaround: Reboot the Secondary server and then wait for the reconfiguration to complete (EN-1573).
Performing a single node upgrade and then cancelling the upgrade will continue to display the single node upgrade status in the server list.
Workaround: Navigate to Manage -> Remove the selected server to remove the single node upgrade status from the server list. Removing the upgrade status may result in the main entry for the cluster being removed as well. To re-add the cluster, navigate to Manage -> Add (EN-1491).
When performing an upgrade and selecting the
Upgrade only a specific server in the cluster
option, the progress status for the Secondary/Tertiary sever being upgraded is displayed in the Primary server
Workaround: This can be safely ignored as it is only a cosmetic status message (EN-1491).
- After adding a valid license to a Failover pair, a Warning sign is still present in the Protected Servers pane of the Failover Web Manager (EN-881).
- After deploying Ipswitch Failover, the navigation through Status/Events/Tasks/Rules/Settings is blocked (EN-965).
- The Ipswitch Failover Web Manager "Acknowledge" button doesn't clear the failure status in some scenarios (EN-970).
- When the Primary server install fails at the add server to protected servers list, the wrong failed message status is displayed (EN-971).
When upgrading Ipswitch Failover with the Ipswitch System Tray tool running, the
information may not be updated.
Workaround: Restart the Ipswitch System Tray tool (EN-867).
- The Failover Management Service User Interface fails to display a correct status when it is closed and reopened during an upgrade process (EN-1083)
On uninstallation of Ipswitch Failover Management Service, you may receive a popup about another process holding a lock on a log-file.
Workaround: Start Task Manager and terminate any instances of nfremoteexec.exe (Ref-15310)
- After uninstalling Ipswitch Failover, when reinstalling, the status of the operation may briefly display inaccurately. (Ref-16640)
- Attempting to upgrade multiple pairs of Ipswitch Failover v9.0 to v9.0.1 results in the sequential upgrade of the pairs rather than a simultaneously upgrade and requires the user to click Next to continue the upgrade on the additional pair (EN-919)
- Some licensing error messages are not useful (EN-967).
- The Ipswitch Failover .msi installer package is sometimes detected as having untrusted publishers (EN-969).
- In the event the registry preferences are lost, they will be restored during the Ipswitch Failover Service restart (EN-1447).
- Logging out of the Ipswitch Failover Management Service User Interface with a server pair selected in the Protected Servers pane and logging back in may result in the server cluster's information failing to display.
- Workaround: Refresh the Ipswitch Failover Management Service User Interface page (F5) and re-login (EN-1018).
- The Plan Execution pane steps displayed may not correspond to the server cluster selected in the Protected Servers pane except when an update arrives (EN-905).
- When a trio is installed and the Secondary server becomes dead or deleted, you must reinstall the entire trio (EN-508).
- Synchronization status between servers in a trio is relative, for example, "A" is in-sync with "C" if "A" is in-sync with "B" and "B" is in-sync with "C" (EN-1037).
- When extending a pair to a trio, the status message displayed during tertiary deployment may not be accurate (EN-1094).
- If a protected server is removed and re-added via Discover Protected Servers in the Ipswitch Failover Management Service, old tasks may display in the tasks pane for the newly added protected server (Ref-15470)
- Multiple concurrent tasks of the same type may not be shown correctly in the Ipswitch Failover Management Service (Ref-16522)
When attempting to collect logs via the Ipswitch SCOPE Configuration Tool, the dialog prompting you to put Ipswitch Failover into the Maintenance Mode is hidden behind the Ipswitch SCOPE Configuration Tool dialog and prevents you from collecting the logs (Ref-14294).
Workaround: Either maximize the dialog icon from the Windows Toolbar or use Alt + Tab to bring the dialog forward so that a response can be given to the prompt.
- After performing a switchover with VMware Platform Services Controller installed, the user must restart their browser and re-login to the vSphere Web Client v6.0 (EN-1310).
Installation instructions are found in the following document(s)
- Ipswitch Failover v9.0 Installation Guide
Uninstalling Ipswitch Failover Management Service from vCenter Server
- On vCenter Server, stop the Ipswitch Failover Management Service.
From the Control Panel, uninstall Ipswitch Failover Management Service.
Note: If you receive a popup warning about another process accessing a log, start Task Manager and terminate any instances of nfremoteexec.exe
Ipswitch Failover v9.0.1