Proxmox Issues

[sbach]

There are some issues in my environment with Veeam backing up Proxmox VMs.

You can't schedule Proxmox Backup Jobs to run after another, as well as no option for Pre/Post script. Ok, that's fine I can create a PowerShell script to run the jobs...

'Start-VBRJob' fails immediately with error 'Job has been stopped with failures. Error: Failed to create target for the job 'DCs', targetType: 'VmbApiPolicyTempJob' '. Proxmox Backup Jobs are not listed under 'Get-VBRJob' PowerShell cmdlet, which I'm assuming is related to the error.

Manually running jobs in the console work just fine as well as restoring. How am I supposed to be automating backup jobs?

[sbach]

It also appears that backups are not encrypted, there is no option under Storage > Advanced > Storage

[Gostev]

Hi, job chaining is not recommended. We had this option available in the early days of Veeam but due to continuos issues in support (like parent job issues preventing dependent jobs from starting) we do not make it available for new workloads these days.

Also, the original reason to have the job chaining no longer exists because our scheduler became way more advanced and in particular it will chain the jobs automatically based on their start time. So you can set the start time of the second job a few minutes after the first, and VMs from the second job should only receive backup infrastructure resources (worker and repository slots) only when no VMs in the first job need those any longer. This also allows for more efficient use of backup infrastructure resources and smaller backup window, as the second job does not have to wait until the very last disk of the very last VM of the first jobs has been processed (which can take a long while with a large data disk).

And if you worry about overloading your primary or backup storage, please be ware that you can control concurrency with the concurrent tasks settings on either worker and/or on the repository. Overall, as you can expect Veeam scheduler is quite mature as it's build for enterprise environments with tens of thousands of VMs, where we do not expect customers to micro-manage job chaining in the first place.

Thanks

[Gostev]

@PTide can you comment on encryption? I believe for Proxmox it is controlled in the repository access setting, like it is for other new workloads (namely AHV/RHV/OLVM), correct?

[PTide]

He,

That's right, encryption in v1 works the same way as for AHV and oVirt KVM - encryption is set per-repository, not per-job.

Thanks!

[sbach]

Great, thanks for the insight on scheduling and encryption.

That brings me to my last issue. I have a script that runs after the final item is backed up that syncs the repo offsite. I keep 7 days locally in the repository on Veeam and offsite is basically infinite. What would be the best method to handle this?

[Gostev]

@PTide do we have pre/post jobs scripts in V1?

[PTide]

Hi,

No, we don't have scripts in v1. Neither job scripts, nor snapshot scripts.

Depending on the offiste repo type, I would suggest looking at Backup Copy Job. If that's not an option for you, you might want to consider using task scheduler on VBR.

Thanks!