version 4.0 | document revision 1
...
A Task schedules one or more Policies for execution. Tasks can be scheduled to run at specific times, or can be run on-demand via the Quick Run control on the 'Dashboard'.
While a Task is running, its status is displayed in the 'Running Tasks' panel of the 'Dashboard'. When Tasks finish they are moved to the 'Recent Tasks' panel.
Operation statistics are updated in real time as the task runs. Operations will automatically be executed in parallel, see E for more details.
If multiple Tasks are scheduled to start simultaneously, Policies on each Source are grouped such that only a single traversal of each file system is required.
...
Installation of the FileFly LinkConnect Server software requires careful configuration of both the NAS / file server and the FileFly LinkConnect Server machines. Instructions are provided in 5.4 for OneFS and 5.2 for Windows file servers. Other devices are not supported.
...
Suspend the scheduler in FileFly Admin Portal
Restore the primary volume
Run a 'Post-Restore Revalidate' policy against the primary volume
To ensure all stubs are revalidated, run this policy against the entire primary volume, NOT simply against the migration source
This policy is not required when only WORM destinations are in use
Restart the scheduler in FileFly Admin Portal
...
URIs created on previous versions of FileFly using the cloudscaler scheme will continue to function as expected. Existing destinations should NOT be updated to use the scsp scheme. The cloudscaler scheme is simply an alias for the scsp scheme.
...
URIs created on previous versions of FileFly using the swarm scheme will continue to function as expected. Existing destinations should NOT be updated to use the scspdirect scheme. The swarm scheme is simply an alias for the scspdirect scheme.
...
Some errors result in further action being taken which may itself fail. Errors with multiple branches are used to convey this to the administrator. Consider an error with the following structure:
[0] ERR... [1] ERR... [2] ERR... [3] ERR... [4] ERR... [5] ERR... [6] ERR... [3] ERR... [4] ERR... [5] ERR...
Whatever ultimately went wrong in line 6 caused the operation in question to fail. However, the function at line 2 chose to take further action following the error – possibly to recover from the original error or simply to clean up after it. This action also failed, the details of which are given by the additional errors in lines 3, 4 and 5 at the end.
...