Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

  1. Suspend the scheduler in FileFly Admin Portal

  2. Restore the primary volume

  3. 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

  4. 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:

...

  • 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.

...