Neverfail Replicator V5.3.0 - Release Notes

Follow

Summary

This Knowledgebase article provides information about Neverfail Replicator V5.3.0.

New Features

  • A single unified Application Management Framework (AMF) replaces the separate Application Manager available in previous versions of Neverfail Heartbeat providing:
    • Passive Server service monitoring prevents protected applications from starting on the passive server – this prevents most file synchronization problems.
    • The System plug-in can be upgraded without stopping Neverfail Heartbeat.
    • Introduction of system monitoring via the System Plug-in. This extends to file filters, services, tasks, and monitoring rules, which are also integrated into the Management Client.
  • Users can now define 'Exclusion' file filters to exclude content from the protected set.
  • Neverfail Heartbeat can now be stopped from the System Tray icon.
  • Performance improvements.
  • Added the ability to choose windows or java look-and-feel with Windows PLAF as the default.
  • Added the Versionless Neverfail Heartbeat Management Client that allows the user to manage multiple versions of Neverfail from a single Management Client after installing the Client Support kit.

Changed Features

  • The Reference Guide and Installation Checklist have been removed from the installation kit. Information about technical documentation can be found in the Readme.txt file contained in the kit. All documentation is now available from the Neverfail Extranet.
  • Temp files created during Full System Check are now compressed.
  • Incorporated SCOPE Data Collector service V4.3.1.
  • Removed the case sensitivity of the \Windows folder on the Primary and Secondary server, which previously resulted in "The root folder is different" error message during Setup.
  • Removed "while active/passive" from the default red alert, yellow alert email and tool tray messages.
  • Removed the 'Mark as In-Sync' and 'Mark full file system as In-Sync' buttons.
  • Changed Red/Yellow Alerts so that they are logged to event log. Added a new EventLogResponse. Removed the default
  • Red/Yellow exec command. Added ability to set alert event log message and enable/disable logging.
  • Changed "Error sending email alert (KB 517)" Alert. Modified the EmailResponse class to fire EmailFailedEvents only when the previous attempt to send was successful.
  • The Server Configuration application now uses the same look and feel as the Management Client.
  • System Status and Control Panel changed to provide more detailed information about the health of the system.
  • Applications Screen
    • Summary panel
      • Redesigned to indicate whether the Primary or Secondary server is providing service.
    • Services
      • Services depending on protected services will be managed (i.e. started and stopped) by Heartbeat but not monitored (i.e. not restarted if stopped by some external agency).
      • Services upon which protected services depend will be monitored (i.e. restarted if stopped) but not managed (i.e. not stopped if protected applications are stopped).
    • Tasks -these are an extension of the start, stop, and monitor scripts in earlier versions of Heartbeat. Types of task are classified by when the tasks run, and include the following tasks:
      • Network Configuration – These types of task are run first to ensure the environment is updated to support the application. Typically used in a WAN, they are used to launch dnscmd and dnsupdate. Where multiple dnscmds are required, these can be contained in a batch script, which is launched by the task.
      • Pre/Post Start - Run before and after services are started on the active server.
      • Pre/Post Stop - Run before and after services are stopped on the active server.
      • Pre/Post Shadow -Run before and after a shadow copy is created on the active server by the Data Rollback Module.
      • Rule Action - Run only when a rule has been triggered, or a service fails its check.
    • Rules - these are an extension of the current application and system monitoring rules. All rules can only implemented by plug-ins (i.e., there are no user-defined rules).
      • Rules can be either “timed” (they must evaluate as true continuously for the specified duration in order to trigger) or “latched” (they trigger as soon as they evaluate to true).
      • Rules can be configured with rule actions, which are the tasks to perform when the rule triggers.
    • Plug-ins - Plug-ins are .NET Assembly .dlls that implement all of the functionality required to provide monitor system performance.
      • Plug-ins are installed by browsing to the *NFPlugin.dll file from Heartbeat.
      • Plug-ins can provide configuration options.
  • Data Screen
    • Configuration panel
      • Filters now have one or more 'Sponsors'. A protected application provides sponsorship of a filter, to indicate it requires this filter to be present. Filters can also be sponsored by the user.
      • Exclusion filters - These must be subsets of (i.e., be more restrictive than) inclusion filters.
      • Filters are compared with each other, and if one filter is more general than another is, only the more general is used. This allows efficient filter sets to be used, e.g., fileservers with 1000s of individual shares can be replaced by a single more general filter configured by the user.
      • All filters are validated before being passed to the replication components, and the Management Client reports why filters have been rejected (e.g., because the drive does not exist).

Fixed Issues

  • Corrected a potential NullPointerException if the exit was called before initialization.
  • Corrected the FullSystemCheckTask so that the processor does not sit at 100% for a 15-minute period when verifying a 60GB file with LBM enabled.
  • Removal of hard coded foreground color settings.
  • Corrected to only report errors on editingStopped() if the editor contains a non-empty string. Also, editingStopped() now ensures that editor's text is cleared before returning.
  • Corrected a handle leak when FSM attempts to detect reparse points.
  • Corrected issues installing the nfpktfltr during Setup on Windows 2000 installations when the Digital Signature Not Found dialog fails to appear.
  • Corrected NFServerR2: InvokeJVM - Failed to convert Java Arg list. Problem installing on paths with chars from multiple code pages.
  • Corrected the display, age of certain entries were appearing in the wrong queue. Safe queue entries displayed in the Unsafe queue and vice versa.
  • Corrected the application status (blank) on the Secondary server when the Management Client is restarted and the channel is not connected.

Known Issues

The following are known issues in Neverfail Heartbeat V5.3.0.

  1. Installation Issues
    1. Upgrades from earlier versions of Neverfail Heartbeat should not be attempted, as the upgrade functionality is not fully implemented yet.
  2. Operational Issues
    1. None
  3. Uninstallation/Reinstallation
    1. Setup is unable to uninstall NFServerR2.exe, the executable for the Neverfail Server R2 service.
    2. On uninstallation, you may be asked to delete the root folder of the Neverfail Heartbeat installation (by default, C:\Neverfail).  This folder is in use by Neverfail SCOPE, which is not removed when Heartbeat uninstalls; so you should ignore the warning and leave the folder in place.

Supporting Documentation

Technical Documents supporting this version of Neverfail Heartbeat are contained in Knowledgebase article #1280 - 'V5.3[.n] Neverfail Heartbeat Technical Documentation'.

Installation Information

Installation instructions are found in Neverfail Heartbeat and Neverfail Replicator - Technical Documentation - Reference Guide V5.3-Rev2 .


Applies To

Neverfail Replicator V5.3.0


Related Information

None

KBID-1412

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.