Running Multiple Agents on a Single Host

Using multiple Agents on the same system is discouraged and may result in excessive license charges at renewal, because each Agent will consume a separate license, even if on the same machine.

It is not necessary to use multiple agents in order to have multiple separate folders synced or mounted on Files.com. When creating a Remote Server Sync or Remote Server Mount, you will have an opportunity at that time to specify the remote path for that specific sync or mount.

Ensure that the root path for the one Agent that you do install is set to a parent path of the folders you will be accessing on Files.com.

With that said, it is technically possible to run multiple Agents on a single host. On Windows based systems, only 1 Agent can run as a system service but multiple Agents can be run manually.

You should not do this without ensuring that your proposed use will fit within the limits of your Files.com subscription.

The primary use case for running multiple Agents on a single server would be if you have multiple Files.com sites, where each separate site needs access to the exact same local server.

Another use case for running multiple Agents on a single server is when a Production instance and a Test/Dev instance need to be implemented to the same server. Even so, in this case, we recommend keeping Production and Test/Dev instances completely separate from each other and so, ideally, separate servers should be used for Production and Test/Dev, each with its own Agent.

Create each Agent as described in the setup instructions. Each Agent should be created on the Files.com site that you want the Agent to connect with.

On Windows based systems, you can run multiple Agents manually from the command line. You can also run 1 Agent as a Service but the others must be run manually from the command line.

On Linux and Mac based systems, you can run multiple Agents manually from the command line. You can also run multiple Agents as system services by adding multiple entries in the Systemd or Launchd configuration, one for each Agent.