Filefly - How to enable stub delete detection in version 2.1.1

Owned by Tony Lokko (Unlicensed)
Oct 10, 2017
2 min read

Filefly 2.1.1 adds a new feature for Windows Agents to track deletions of Stub files themselves. 

When a FileFly agent is installed on a Windows server, a filter driver is applied to the OS. This filter driver sits above the base drives in the system so it will intercept all calls to the file system (read, write, delete, rename etc). 

In prior versions of FileFly, read / write / rename operations were tracked and acted on so that the base file could be restored onto the local file system per user / application action. Deletes, however, were not tracked. So, if a delete was performed on a stub, just the stub on the source system was deleted; the base file (i.e. the data stored in Swarm) remained in place on the storage cluster. This behavior would lead to the creation of orphaned content in the Swarm storage cluster as a result.

 

With FileFly 2.1.1, functions have been added to the filter driver to take note of a stub delete and keep track of the associated objects in Swarm. In this way, they are added to the scrub list for deletion on the next Scrub task run. As the driver sits on top of the file system, all deletes are tracked and scrub operations will continue to honor the grace period configured in FileFly.

Step-by-step guide

To enable this feature

  1. First update the Filefly Migration Agent for Windows and Filefly Gateway to version 2.1.1
  2. Go to C:\Program Files(x86)\Caringo Filefly\data\FileFly Agent\
  3. Create the file ff_agent.cfg
    1. When creating this file remove the .txt extention so that the file type is .cfg
  4. Edit the file
  5. Add the line

Windows.StubDeleteMonitoring.ProcessEvents=true

Make sure that you save the file with UTF-8 encoding and filetype all files and save the file in the same directory.

Next restart the Caringo Filefly service

 

When the Filefly Agent is restarted we can check if the change was registered in the messages log.


If you open the file and go to the end of the log you will see some thing like the following.


Once that is done, reboot the server to be sure that the migration agents driver is running with the changes.


Repeat the above for any Filefly windows agents that you have or just copy the ff_agent.cfg file to all agents.




© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.