Server Requirements

Learn about requirements for connecting Movebot to file servers.

Virtual Server Requirements

This software is run as an executable and can be also run as a service. While every migration is different, we recommend the resources below.

Type
Min Requirement

Memory

16Gb

Hard Disk Space

32GB of free disk

Network

1000GB LAN connectivity

Internet Connectivity

Unfiltered connectivity

CPU

4+ vCPU Cores

Supported Windows Versions

Below are the current versions of Microsoft Windows that are tested and supported.

Operating System
Supported

Windows 10

Yes

Windows Server 2016

Yes

Windows Server 2019

Yes

Windows Server 2022

Yes

Windows 2008 R2

Yes - please contact support

Migrating Data from Unsupported Servers

If you’re working with an unsupported server OS, you can still migrate your data using this workaround:

  1. Install the Windows Server Agent on a supported Windows machine.

  2. Create a mapped network drive to the location of the unsupported server.

  3. Configure the agent to access data via the mapped drive path.

This approach allows you to migrate data across your network without needing to install the agent directly on the unsupported system.

Need help setting this up? Contact support@movebot.io.

Network and Firewall Requirements

Migrations are upload-intensive by nature and so the speed of your migration will be heavily dependant on your internal and external network capacity. We recommend 1Gbps uplink speed where possible.

If you are experiencing performance issues with the agent, we recommend running a speed test and checking your project settings to ensure you've selected migration region that is close to the agent.

Recommended Connectivity for Host

Params
Details

Ports and Connectivity

HTTP and HTTPS internet access. Ports 80, 443 and 53

Uplink Speed

100MBit Internet Uplink. Recommended 1GBit

Local Network

1000Gbit Physical LAN connectivity

Outbound Firewall

No outbound filtering

The Movebot agent communicates with the Movebot control plane and APIs exclusively via HTTPS. This means that no additional ports are needed to be opened.

If you have a restrictive firewall, we recommend deploying the Movebot agent on a virtual machine that can be whitelisted through the firewall. Movebot uses dynamic IP addresses and connectivity to Movebot's cloud infrastructure IP addresses cannot be whitelisted due to the dynamic nature of Movebot's cloud architecture.

If you are using a proxy server - we highly recommend allowing Movebot to use a direct path to the internet. If this is not possible, then follow the instruction here to configure the Movebot agent to connect via the proxy.

For more information, get in touch with support via support@movebot.io Tags: agent

Last updated

Was this helpful?