Configurations and ports

The flexibility of private and public accessibility allows for many different Carbonite Migrate configurations, including whether a proxy server is needed. If your source or target does not have a public IP address, you will have to use a proxy server for communication between the source or target and the Carbonite Migrate service. The proxy server is not used for communication between the source and target. Even though migration data is encrypted, you may need to consider private and public accessibility between your source and target for the migration of the data. There are different port requirements depending on the configuration you are using.

Your source environment will have the source server and optionally cloud services or a hypervisor, depending on your configuration.

Your target environment will have the target server and cloud services or a hypervisor, depending on your configuration.

Even though migration data is encrypted, you may need to consider private and public accessibility between your source and target for the migration of the data.

Any combination of the configurations above is possible. For example, if you are migrating from cloud to cloud and your source and target both have private IP addresses, your configuration would look similar to this.

The colored arrows correspond to the configuration diagrams above.

Component to Component Windows Communication Linux Communication Arrow Color

Web Browser to Carbonite Migrate

Carbonite Migrate to Cloud or Hypervisor Service

Proxy Server to Cloud or Hypervisor Service

 HTTPS port 443
Proxy to Carbonite Migrate

Service Bus (outbound only) port 9354

SignalR port 31867

Proxy to Source

Proxy to Target

Carbonite Migrate to Source

Carbonite Migrate to Target

SMB port 445

WinRM ports 5985 and 5986

Carbonite Migrate port 6325

SSH port 22

Carbonite Migrate port 6326
Source to Target Carbonite Migrate ports 6320 and 6325 Carbonite Migrate ports 1500, 6325, and 6326