/
Where to install Migration Agents versus Gateway Agents

Where to install Migration Agents versus Gateway Agents

Choose whether to install an "Agent for Migration" or a "Gateway Agent" during the installation of a FileFly Agent. This is the essential difference:

  • Agent for Migration - Moves files from a data source (server) to a target destination (storage); an agent must be installed on every server planning to migrate data from.

  • Gateway Agent - Acts as a proxy between FileFly Migration agents and the destination storage location. This provides access to Swarm and CloudScaler destinations when direct access is not possible.

Note: the Gateway Agent does not migrate data. Use a Gateway Agent when it is not possible for a server running a Migration Agent to have direct access to the destination storage. Examples of this include:

  • A dedicated proxy is used to connect to a cloud-based endpoint.

  • The destination storage (e.g., Swarm Storage) is on another network segment, and it is not desirable to have the source server connected directly to the destination storage network.

Best practice

Review the requirements for network connectivity between FileFly sources and destinations before making the agent installation choices.



Related content

Walkthrough: How to install FileFly 3.x
Walkthrough: How to install FileFly 3.x
Read with this
How to move FileFly Agents
How to move FileFly Agents
More like this
FileFly 3.0 Release Notes
FileFly 3.0 Release Notes
More like this
How to move FileFly stubs to a new Migration Agent
How to move FileFly stubs to a new Migration Agent
More like this
5 FileFly Admin Portal Reference
5 FileFly Admin Portal Reference
More like this
How to set up a FileFly S3 endpoint for Gateway
How to set up a FileFly S3 endpoint for Gateway
More like this

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