...
Each FileFly Agent server may fulfill one of two roles, selected at installation time.
In the 'FileFly Agent for migration' role, an agent assists the operating system to migrate and demigrate files. It is essential for the agent to be installed on all machines from which files will be migrated.
By contrast, in In the Gateway role, the agent provides access to CloudScaler and Swarm destinations.
...
Clustered volumes managed by Windows failover clusters are supported. However, the Cluster Shared Volume (CSVFS) feature is NOT supported. As a result, on On Windows Server 2012 and above, when configuring a 'File Server' role in the Failover Cluster Manager, 'File Server for general use' is the only supported File Server Type. The 'Scale-Out File Server for application data' File Server Type is NOT supported.
When using clustered volumes in FileFly URIs, ensure that the resource FQDN appropriate to the volume is specified rather than the FQDN of any individual node.
...
If a Windows source server is configured to use migration policies and Windows Data Deduplication, it should be noted that a given file can either be deduplicated or migrated, but not both at the same time. FileFly migration policies will automatically skip files that are already deduplicated. Similarly, Windows will skip skips FileFly stubs when deduplicating.
When using both technologies, it is recommended to configure Data Deduplication and Migration based on file type such that the most efficacious strategy is chosen for each type of file.
Note: Microsoft's legacy Single Instance Storage (SIS) feature is not supported. Do not use SIS on the same server as Caringo FileFly Agent.
...
To retire a single server or cluster node, simply click Retire Server in the drop-down details for the server or cluster node of interest. To retire an entire cluster, click on the name of the cluster, then click Retire Cluster on the 'Server Details' page.
...
From any tab, click the about icon in the top right corner to access the 'About' page. This page contains information about the FileFly Tools installation, including file locations and memory usage information. Licensed capacity consumption information will also be displayed.
The page also enables the generation of a support.zip file containing your encrypted system configuration and licensing state. Caringo DataCore Support may request this file to assist in troubleshooting any configuration or licensing issues.
...
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
...
FileFly Agents may be configured on a per-server basis via FileFly Admin Portal. Simply navigate Navigate to the 'Servers' tab and click on the name of the cluster or standalone server to be configured, then click 'Configure'.
When the configuration options are saved, a new ff_agent.cfg file is pushed to the target server to be loaded on the next service restart. In the case of a cluster, all nodes will receive the same updated configuration. The service may be restarted through the Admin Portal interface.
The ff_agent.cfg file resides in the following location:
...
Log location and rotation options may be adjusted if required. Debug mode may impact performance and should only be enabled following advice from Caringo DataCore Support.
| Anchor | ||||
|---|---|---|---|---|
|
...
Max Slots
The maximum number of operations that may be performed in parallel on behalf of a single policy for a given Source (default: 8)
Worker Thread Count
The total number of operations that may be performed in parallel across all policies on this agent (default: 32)
This does not limit the number of policies which may be run in parallel, operations will simply be are queued if necessary
Important: take care if adjusting these parameters – over-parallelization may result in lower throughput.
...
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.
...