Page Comparison

...

1. Demigrate the files.

   • Create a Rule in the FileFly Admin Portal to demigrate based on a filename pattern or attributes, such as size, date, or owner.

   • Access the files or change the owner.

2. Delete the files (not stubs) no longer needed to be archived in Swarm. 
   Important: If a stub file is accidentally deleted, use DrTool to recreate it (search for Recreating Stubs in the FileFly Guide).

3. FileFly keeps track of which files have been are demigrated by way of metadata objects that are stored in Swarm. Once a file is demigrated, these These metadata references stay available in case a stub file needs to be recreated to restore access to the data before the grace period expires once a file is demigrated.

4. Wait the (configurable) 24-hour grace period, then run a Scrub (Aggressive) task.

5. The task deletes the objects related to those files from Swarm. Monitor what objects FileFly stores in Swarm by using a listing request:

   Code Block
   language bash
   curl -iL "http://SWARM/filefly-destination-bucket?format=json&fields=x-alt-meta-name,name,tmborn,x-alt-meta-path"

6. Allow several HP cycles for the space to become fully available in Swarm. Use the Swarm UI to monitor the trapped space being freed (seeViewing and Managing the Cluster).

...