Feedback on Veeam Backup for Proxmox: encryption, job chaining and scripting limitations

[Aliko47]

Hi everyone,

I have been testing Veeam Backup with Proxmox and overall I think the integration is a good and important step. The Veeam Backup Worker concept also looks promising and works reasonably well so far.

However, compared to VMware-based jobs, the current Proxmox implementation feels less flexible in a few areas. I would like to share some feedback and also check whether I may have missed something in the configuration.

The main points are:

1. No backup encryption option visible
In the Proxmox backup job settings, I currently do not see an option to enable backup encryption.
This is something I consider important, especially when backups are stored on shared repositories, offloaded, or handled as part of a broader security concept.
Is encryption currently not supported for Proxmox backup jobs, or is it configured somewhere else?

2. No job chaining / “start after another job” option
For Proxmox backup jobs, it looks like I have to configure a fixed schedule, for example a specific daily start time.
I do not see an option to start one Proxmox backup job automatically after another Proxmox backup job has completed.
This makes scheduling less clean, especially when multiple jobs depend on each other or when the runtime can vary.

3. Backup Worker concept is good, but feels less flexible than VMware
I like the idea of the Veeam Backup Worker, but compared to VMware environments the Proxmox workflow currently feels more limited.
With VMware jobs, there are more mature options around scheduling, processing behavior, and general job control.
I understand that Proxmox support is newer, but these differences are noticeable in real-world planning.

4. No visible pre- and post-job scripting option
Another thing I noticed is that I cannot find an option for pre- and post-job scripting in Proxmox backup jobs.
In other Veeam job types, scripting hooks are useful for preparing applications, triggering external processes, notifying monitoring systems, or performing custom cleanup tasks after the job has completed.
For Proxmox jobs, I currently do not see such an option in the job settings.
Is pre-/post-job scripting currently unsupported for Proxmox backup jobs, or is this handled differently?

Overall, I think Veeam Backup for Proxmox is a strong start, but these limitations make it harder to use in the same structured way as existing VMware backup jobs.

Are these known limitations at the moment?
And are backup encryption, job chaining, and pre-/post-job scripting planned for future versions?

Best regards
Aliko47

[karsten123]

1. you have to set it on repository level