PVE Backup Job Chaining

[mcheshire]

Hi,

I've noted in PVE B&R, there is no way to chain 1 job after the other to ensure things happen in order and you dont overload your repositories etc.

Is this feature coming in a future release?

Thank you for releasing Proxmox capability, this will be a good option for some fleeing the Vmware world.

M.

[rovshan.pashayev]

Hello Michael,

Currently, the job chaining feature is not on the roadmap.
However, I recommend reviewing the following reply. It explains why you should avoid using job chaining and instead utilize load control at the repository level.

[NaughtyDog]

Hello,

we are currently migrating our virtual infrastructure from VMware to Proxmox. While testing Veeam on Proxmox, we noticed that in the job configuration under Schedule, there is no option to automatically start jobs depending on the previous job (After this job:). Is there a plan to add this missing option in a future update? What are the recommendations for job configuration if this option has been used previously under VMware and Hyper-V?

Thanks

[david.domask]

Hi NaughtyDog,

I've moved your post to an existing topic on the same subject (job chaining = "Start after this job" option)

Please see Rovshan's answer above for the current status.

[uatre_fnl]

Hi Veeam R&D Team,

I am currently working with Veeam Backup & Replication v13 (build 13.0.1.2067).

As I mentioned in a previous thread, we are currently finalizing our migration from ESXi to Proxmox VE. While the integration is a great step forward, we have encountered another significant orchestration hurdle regarding job scheduling which I will detail below:

We have noticed that Proxmox VE jobs are currently isolated from the global "Job Chaining" ecosystem. This presents a two-sided challenge for orchestration:

• Inbound Chaining: The option "Run the job automatically > After this job" is missing from the Proxmox VE backup job wizard.

• Outbound Chaining: Proxmox VE jobs do not appear in the selection list when configuring other job types (such as Windows/Linux Agents, Hyper-V, or Tape jobs) to run after a specific task.

This lack of homogeneity across job types prevents us from building a continuous backup pipeline. Currently, we are forced to "estimate" the duration of our Proxmox backups and schedule subsequent tasks based on time slots.

I kindly request the inclusion of Proxmox VE jobs in the global "After this job" scheduling logic to achieve full feature parity with the rest of the Veeam ecosystem.

Thank you for your time and for the constant evolution of this integration!

Best regards,
Facundo
Systems Administrator

[david.domask]

Hi Facundo,

I've moved your post to an existing topic on the same request.

I would ask if you could review Rovshan's post above and elaborate a bit on the use case for using job chaining instead of the built-in resource scheduling; we can consider the request, but job chaining tends to lead to scheduling challenges when there are unexpected delays or issues with jobs in the chain.