Backup Agent - Known Restrictions

Objective

This guide details the known restrictions and limitations of the Backup Agent product that you should be aware of before using the service.

Known Restrictions

Backup Policy

• The backup policy is restricted, you cannot modify it.
• You cannot configure a backup only on a list of files or folders.
• You cannot modify the date and time of backup triggers (this will be the subject of a future improvement).

VSPC Access

• The user you receive is read-only, you cannot make modifications directly on the VSPC.

Vault

• You cannot create additional vaults, they will be created automatically to ensure that your data is not hosted in the same datacenter where your Bare Metal server is located.
• You cannot change the vault on an agent.

OS Limitations

• You can find the list of compatible OS for the Veeam Agent here.
• The product is not compatible for backing up hypervisors (Proxmox, ESXi, etc.)

Compatibility with other OVHcloud products

• Currently, the Backup Agent product is only compatible with Dedicated Servers, you cannot use your agent on other products.

Network restrictions

• The product is only compatible with servers that communicate with the public IP assigned by OVHcloud to the servers. As of now, it is incompatible with Additional IP addresses or the vRack.

Virtual machines (Proxmox, ESXi, etc.)

• The product only authorises the server’s public IP to communicate with the Veeam infrastructure. So, for example, if you have a Proxmox virtual machine (VM) running on your server and it uses the server's public IP, the agent can work. However, this use case cannot be considered as supported. Too many specific cases related to this configuration can emerge and this is not covered by the product currently.

Go further

Join our community of users.