Requirements and Connectivity¶
Before configuring Veeam Cloud Connect, make sure that your environment meets the software version and network communication requirements.
Supported software versions¶
Cloud4You currently supports the following Veeam product versions:
| Product | Minimum supported version |
|---|---|
| Veeam Backup & Replication 12.3.2 | 12.3.2.4854 or a newer build in the 12.3.2 branch |
| Veeam Backup & Replication 13 | 13.0.1 or newer |
| Veeam Agent for Microsoft Windows | 6.3.2 or newer |
| Veeam Agent for Linux | 6.3.2 or newer |
| Veeam Agent for Mac | 2.3.1 or newer |
Veeam Backup & Replication 13.0.0 is not supported
To connect to the Cloud4You service, you need:
Version:
is not supported.
How to check the Veeam Backup & Replication version¶
In the Veeam Backup & Replication console, go to:
Check the full version and build number.
Example:
It is not enough to verify only that version:
or:
is installed.
For the 12.3.2 branch, the minimum required build is:
Update before connecting¶
If your current version is older than the version supported by Cloud4You, update the environment before configuring or reconnecting to the service.
Before updating
Before updating a production environment:
- check the currently installed version and build,
- review the system requirements of the new version,
- create a Veeam configuration backup,
- schedule a maintenance window,
- if in doubt, contact Cloud4You Support.
Network access¶
The Veeam server or environment on the customer side must be able to access the following Cloud4You endpoints:
on:
Required rules:
| Direction | Protocol | Port | Destination |
|---|---|---|---|
| customer → Cloud4You | TCP | 6180 |
connect.cloud4you.pl |
| customer → Cloud4You | TCP | 6180 |
connect2.cloud4you.pl |
| customer → Cloud4You | TCP | 6180 |
connect4.cloud4you.pl |
The detailed access activation procedure is described in the Service Access section.
Public IP address¶
Connections to Veeam Cloud Connect are allowed on the Cloud4You side for public IP addresses that have been submitted in advance.
If the Veeam server is behind NAT, the relevant address is the public IP used by the firewall or router.
Example:
Submit this address to Cloud4You:
not:
DNS test¶
On the Veeam server, test name resolution:
Resolve-DnsName connect.cloud4you.pl
Resolve-DnsName connect2.cloud4you.pl
Resolve-DnsName connect4.cloud4you.pl
Each command should return a valid IP address.
Port 6180 test¶
Test each endpoint separately:
A correct result is:
If you receive:
check:
- the local firewall,
- the perimeter firewall,
- NAT rules,
- UTM / IDS / IPS,
- DNS resolution,
- whether the public IP address has been submitted to Cloud4You.
Does Veeam require a minimum Internet bandwidth?¶
Veeam does not define one minimum WAN bandwidth requirement for a Veeam Cloud Connect customer.
The service can also work over slower links, but bandwidth directly affects the time required to transfer backups.
The key requirement is that the amount of data changed between consecutive backups can be transferred within the available time window.
The 1 Gb/s requirement in Veeam documentation does not mean the customer needs 1 Gb/s Internet
Veeam lists 1 Gbps LAN or faster as a network requirement for the Cloud Gateway component on the service provider side.
This is not a minimum requirement for the Internet connection of a customer using Cloud Connect.
How to estimate required bandwidth¶
The most important parameters are:
- amount of data transferred each day,
- Daily Change Rate,
- time available for the Backup Copy Job,
- actual data reduction,
- other systems using the same connection.
Example:
If data reduction leaves approximately:
to transfer, and the data must be sent within:
the required average bandwidth is approximately:
Add a safety margin for:
- protocol overhead,
- variable Internet performance,
- parallel transfers,
- retransmissions,
- temporary bandwidth drops.
In practice, we recommend leaving an appropriate margin rather than sizing the connection exactly to the value produced by the formula.
Simple formula¶
An approximate bandwidth requirement can be calculated as:
The result is in:
Example for 250 GB and 8 hours:
First full copy¶
The initial data transfer is usually much larger than subsequent incremental sessions.
Example:
Therefore, the first synchronization may take significantly longer.
The first Full may use the connection for many hours or days
For large environments, take into account the time required to transfer the first full copy.
After it completes, subsequent jobs usually transfer a significantly smaller amount of data.
Example transfer times¶
The following values are approximate and assume that the entire listed bandwidth can be used.
| Data to transfer | 100 Mb/s | 500 Mb/s | 1 Gb/s |
|---|---|---|---|
| 100 GB | approx. 2 h 15 min | approx. 27 min | approx. 14 min |
| 500 GB | approx. 11 h | approx. 2 h 15 min | approx. 1 h 10 min |
| 1 TB | approx. 23 h | approx. 4 h 40 min | approx. 2 h 20 min |
| 5 TB | approx. 4.7 days | approx. 23 h | approx. 11.5 h |
These are theoretical values
Actual transfer may be slower because of:
- protocol overhead,
- storage performance,
- CPU,
- compression,
- WAN latency,
- packet loss,
- shared bandwidth,
- limitations in the customer environment.
Latency and connection quality¶
Bandwidth is not the only factor that affects transfer performance.
The following also matter:
- latency,
- packet loss,
- TCP retransmissions,
- connection stability,
- link congestion.
A:
connection with significant packet loss may perform worse than a stable:
connection.
WAN Accelerator¶
Veeam supports WAN Accelerator for Backup Copy and replication scenarios.
This mechanism can reduce the amount of data transferred over slower WAN links.
Veeam also distinguishes a High Bandwidth mode intended for links faster than:
WAN Accelerator is not required for Cloud Connect
It is an optional transfer optimization mechanism.
A standard Cloud Connect connection can work without WAN Accelerator.
The availability of WAN Acceleration for a specific Cloud4You service should be confirmed with Support.
Firewall and inspection¶
If the firewall performs advanced traffic inspection, make sure it does not interfere with Veeam communication.
If you experience problems, pay particular attention to:
- SSL/TLS inspection,
- IPS,
- Application Control,
- proxy,
- session timeout limits,
- connection limits,
- traffic shaping.
What should you check before adding the Service Provider?¶
Before starting the configuration, verify:
1. Veeam version¶
Supported:
Not supported:
2. DNS access¶
3. TCP/6180 access¶
4. Public IP address¶
Make sure all addresses used by the environment have been submitted to Cloud4You.
5. Bandwidth¶
Check whether the available bandwidth can transfer the daily changes within the required backup window.
Support¶
If you are not sure whether your environment meets the requirements, contact Cloud4You:
or:
It is useful to include: