Summary

This Knowledgebase article provides information about Unprotected Features and their corresponding registry keys.

More Information

The following listing provides the default configuration of actions to be performed when an Unsupported Feature is encountered. The default set of actions for each Unsupported Feature is configured to provide the best protection for the user’s data and the least inconvenience. Neverfail recommends that these values not be changed.

Actions:

LogAsError : Each time the named feature is encountered, Neverfail Heartbeat adds a message in NFLog.txt

MakeOutOfSync : Each time the named feature is encountered, Neverfail Heartbeat marks the affected file out of sync, preventing switchover.

RaiseUserEvent : Each time the named feature is encountered, Neverfail Heartbeat adds a message in NF Event Log and the Windows Logs as well.

RaiseStopEvent : When the named feature is encountered, Neverfail Heartbeat stops replication.

Upon startup, the UnsupportedFeatureMgr logs the any of the following as appropriate:

UnsupportedFeatureMgr.UnsupportedFeatures=

UnsupportedFeature[0]

FeatureType ExtendedAttributes
CheckMask 16
LogAsError true
MakeOutOfSync true
RaiseUserEvent true
RaiseStopEvent false
MaxOccurences 100

UnsupportedFeature[1]

FeatureType HardLink
CheckMask 8
LogAsError true
MakeOutOfSync false
RaiseUserEvent true
RaiseStopEvent true
MaxOccurences 100

UnsupportedFeature[2]

FeatureType ReparsePoint
CheckMask 1
LogAsError true
MakeOutOfSync false
RaiseUserEvent true
RaiseStopEvent true
MaxOccurences 100

UnsupportedFeature[3]

FeatureType Encryption
CheckMask 4
LogAsError true
MakeOutOfSync true
RaiseUserEvent true
RaiseStopEvent false
MaxOccurences 100

UnsupportedFeature[4]

FeatureType SparseFile
CheckMask 2
LogAsError true
MakeOutOfSync false
RaiseUserEvent true
RaiseStopEvent false
MaxOccurences 100

UnsupportedFeature[5]

FeatureType DiskQuota
CheckMask 64
LogAsError true
MakeOutOfSync false
RaiseUserEvent true
RaiseStopEvent false
MaxOccurences 100

Workaround:

By default, Neverfail Heartbeat will mark the files with Unsupported Features as out-of-sync and log an error / event. To prevent files with Extended Attributes from being marked as out-of-sync and logging errors / events when an Unprotected Feature is encountered, use one of the following procedures:

Option 1:

Note: Each of the Unsupported Features has its own registry key.

1. 1. Shut down Neverfail Heartbeat.
   2. On the Primary server, run regedit.exe
   3. Navigate to the registry key:
      
      HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs\neverfail\current\/Unsupported/Feature/Mgr\/Unsupported/Features\/Unsupported/Feature[0]
      
   4. Change the value of /Log/As/Error from ' true ’ to ‘ false ’.
   5. Change the value of /Make/Out/Of/Sync from ‘ true ’ to ‘ false ’.
   6. Change the value of /Raise/User/Event from ‘ true ’ to ‘ false '.
   7. On the secondary server, run regedit.exe
   8. Navigate to the registry key:
      
      HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs\neverfail\current\/Unsupported/Feature/Mgr\/Unsupported/Features\/Unsupported/Feature[0]
      
   9. Change the value of /Log/As/Error from ‘ true ’ to ‘ false ’.
   10. Change the value of /Make/Out/Of/Sync from ‘ true ’ to ‘ false ’.
   11. Change the value of /Raise/User/Event from ‘ true ’ to ‘ false ’.
   12. On the Primary server, start Neverfail Heartbeat.
   13. On the Secondary server, start Neverfail Heartbeat.

Results: The following configuration will prevent an Unsupported Feature from marking a file as out-of-sync and creating an error / event entry in the logs.

UnsupportedFeature[0]

FeatureType ExtendedAttributes
CheckMask 16
LogAsError false
MakeOutOfSync false
RaiseUserEvent false
RaiseStopEvent false
MaxOccurences 100

Option 2:

1. Open a command window and navigate to Neverfail\R2\Bin and start nfclient.exe
2. Type the following:
   
   doSetLogAsError ExtendedAttributes true
   doSetMakeOutOfSync ExtendedAttributes false
   doSetStopEvent ExtendedAttrinutes false
   doSetUserEvent ExtendedAttributes false
   
   Note: This combination of commands given above will have the net result of just
   logging the occurrence of extended attributes in nflog.txt

Option 3: To reset to the default (out of the box) configuration:

1. Open a command window and navigate to Neverfail\R2\Bin and start nfclient.exe
2. Type the following:
   
   doResetDefaultUnsupportedFeatureTypes

Applies To

Neverfail Heartbeat

Related Information

None

KBID-475