This Knowledgebase article provides information about Neverfail Heartbeat internal tasks.
Registry Check
The Registry Check is a task, which starts along with the File System Check. It ensures that the protected registry keys and values are the same on both active and passive Servers.
Full File System Check
A Full System Check is done whenever Heartbeat needs to verify that the protected data on the passive server is “in-sync” with the protected data on the active server. Any time that replication is stopped, and there is an opportunity for the protected data to change, Heartbeat will perform a Full System Check upon restart. Subsequently, a Full System Check happens when Heartbeat is shutdown and restarted and when replication is restarted for other reasons. This happens after a failover when the systems become reconnected, but it does not happen during a switchover operation because the protected application cannot update the protected data during the switchover operation
The File System Synchronization and the File System Verify & Synch Tasks
When a file or folder has been detected as 'Out of Sync', a new pane is introduced to the Neverfail Heartbeat Management Client displaying the detected files. The folder structure to the left side of the Management Client changes, replacing standard folder icons with red folder icons from the 'Out of Sync' file up the tree to the parent drive.
The 'Out of Sync' files can be manually synchronized by clicking the Synchronize All button, which rather than re-synchronizing the entire protected file structure, will just resynchronize the files listed in the right pane. Any files may be resynchronized at any time by selecting their entry in the file list and clicking the Synchronize button in the controls frame.
Where folders are selected, the 'Include Subdirectories' checkbox can be selected to ensure all files within the selected folder have been synchronized.
File System Synchronization task started – By pressing the Synchronize button from the 'Data' section and 'Files Synch and Verify' tab, Heartbeat started to synchronize a selected file or folder from the protected set.
File System Synchronization task completed –Heartbeat finished synchronizing a selected file or folder from the protected set.
The process to verify and synchronize is identical except that you select the Verify and Synchronize button. Select the 'Include Sub-directories' checkbox to ensure all underlying files and subfolders are included in the verification and synchronization operation. When a verification or synchronization operation is underway, the progress bar graphic will display the status.
Each manual or automatically scheduled synchronization and verification request is defined as a 'Task'. Other tasks are queued for processing until the current task is completed. Each task is listed in the task list to the right of the current task frame.
File System Verify & Synch task has started - By pressing the Verify & Synchronize button from the 'Data' section and 'Files Synch and Verify' tab, Heartbeat started to verify and synchronize a selected file or folder from the protected set.
File System Verify & Synch task has completed –Heartbeat finished to verifying and synchronizing a selected file or folder from the protected set.
Internal System Tasks
The Internal System Tasks are created by Neverfal Heartbeat in response the the following:
Renames: Regardless if it's a rename of an already protected file or a rename of an unprotected file that becomes protected after the rename, Neverfail Heartbeat must create a task to synchronize the target of the rename. This may involve a recursive tasks since the rename could be for a directory or a file that has alternate data streams.
Transactions: For transactions that were in flight before starting replication.
Passive Out-of-Sync: When a file is being changed before being verified or synchronized (during a Full System Check).
Orphaned Files Detection
Note: This section applies to Neverfail Heartbeat v6.5 and later
Neverfail Heartbeat can detect files that are availabile in the protected set on the passive server but not available in the protected set on the active server. These files are termed "orphaned files". You can configure the Neverfail Heartbeat Management Client to to detect the orphaned files and either create an event in the log or automatically delete them upon detection.
If Orphaned File Detection is disabled either manually or as the result of a failover, an event is created in the event logs stating the following:
Orphaned Files Detection is not configured.
To configure Orphaned Files Detection:
With Neverfail Heartbeat running, launch the Neverfail Heartbeat Management Client.
Navigate to Data: Replication page and click the Configure button.
Select the Orphaned Files tab.
Select the Detect orphaned files check box.
- Select one of the following options in the On detection, take the following action drop-down:
Click OK to accept the changes and dismiss the dialog.
Applies To
All Versions
None
KBID-1188