The set of File Filters is reset to C:\Protected\**. What should I do next?

Follow

Summary

This Knowledgebase article describes the behavior of Neverfail IT Continuity Engine when one or more entries in the set of File Filters are pointing to a non-existent drive letter or to a non-NTFS partition.


More Information

The set of File Filters configured for each Neverfail IT Continuity Engine cluster can be found in the Advanced Management Client, under the Data -> Configuration tab or the Engine Management Service. The File Filters determine which files and directories are protected by Neverfail IT Continuity Engine.

When Neverfail IT Continuity Engine starts, the complete set of File Filters is checked for consistency. If any of the entries points to a non-existent drive letter or to a non-NTFS partition, the list of File Filters will be reset to the default value of C:\Protected\**. This is a safety measure; Neverfail IT Continuity Engine requires the same drive letter configuration on the Primary and the Secondary servers, and only supports protection of NTFS partitions.

Recovery Steps

The terms below refer to the Neverfail installation directory and the Windows installation directory, respectively.

Before beginning the restoration of the File Filters set, make sure you have the same drive letter configuration on the Primary and Secondary servers. If Neverfail Engine is currently running, stop Neverfail Engine but opt to leave the protected application running.

Neverfail recommends the following corrective measures, which vary depending on which application is being protected:

Neverfail for File Server

  1. On the Active server, delete the file \R2\Bin\FileServer.nfd. This will ensure all filters for network shares are recreated when Neverfail Engine is restarted.
  2. Start Neverfail Engine on both servers and allow the filter discovery tool to recreate the filters, and also the file \R2\Bin\FileServer.nfd. The filter discovery operation will not start immediately - the filter discovery tool runs at a preconfigured interval (by default, every 2 minutes).
  3. In the Log -> View Event Log section of the Advanced Management Client, wait for a ‘File System Filter Change Check Task Completed’ message, and then check that each share has its corresponding File Filter entry under Advanced Management Client.
  4. Using the Data - > Configuration panel of the Advanced Management Client, manually add the following 2 entries to the File Filter set:

    \R2\BIN\FILESERVER.XML

    \R2\BIN\FILESERVER.NFD.
  5. Click the Apply button when finished. Allow the system to perform another File System Filter Change Check Task.

Neverfail for SQL Server:

  1. On the Active server, delete the file \R2\Bin\SQLServer.nfd. This will ensure all filters for SQL Server database files and transaction logs are recreated when Neverfail Engine is restarted. Knowledgebase article #398 - ' Automated filter discovery in Neverfail for SQL Server' describes in detail the Automatic filter discovery tool in Neverfail for SQL Server.
  2. Start Neverfail Engine on both servers and allow the filter discovery tool to recreate the filters, and also the file \R2\Bin\SQLServer.nfd. The filter discovery operation will not start immediately - the filter discovery tool runs at a preconfigured interval (by default, every 2 minutes).
  3. In the Log -> View Event Log section of the Advanced Management Client, wait for a ‘File System Filter Change Check Task Completed’ message.
  4. Using the Data > Configuration panel of the Advanced Management Client, manually add the following 4 entries to the File Filter set:

    \R2\BIN\SQLSERVER.XML

    \R2\BIN\SQLSERVER.NFD

    \R2\BIN\*.DSN

    \System32\DTCLOG\**
  5. Click the Apply button when finished. Allow the system to perform another File System Filter Change Check Task.

Neverfail for Exchange:

  1. Recreate the filters for Exchange following the steps provided by Knowledgebase article #242 - ' How to Automatically Discover or Move Exchange Log and/or Mailstore Locations' .
  2. If any 3rd party applications are protected using AMX's, or the protected application is none of the above, please contact Neverfail Support for assistance.


Applies To

All Versions


Related Information

None

KBID-500

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.