Feature Request - Support for Proxmox VE with Veeam Powershell

[mhurcombe]

I'd like to ask for the Start-VBRZip Veeam Powershell command and equivalent "get-VBRIdentity" type commands to be considered for a future release.
We currently do our VMware VM backups using the Veeam Powershell commands and would very much like to be able to do the same for our new Proxmox VE VMs. We are planning to migrate all of our existing VMs to Proxmox VE for various reasons.
We can use the Veeam console to at least perform backups or crreate backup jobs for Proxmox VMs but this is not as flexible as we'd like, compared to what you can do with Start-VBRZip.
Thanks in advance for condiering this request.

[Mildur]

Hi Mark,

Welcome to the forum!
Currently, PowerShell is not available for Proxmox workloads, and we are aware of this request.

May I ask, what kind of "flexible options" are missing that you have to run VeeamZip backups?

Best,
Fabian

[mhurcombe]

Hi Fabian,
What I mean by flexible is that on the command line via Powershell we can specifiy the destination folder in particular where we want the backup files to go. You don't seem to have the same control via "jobs" but it isn't a show stopper. So long as we know where the backup files are written we can move to our NAS and then to offsite backup (removable USB in our case).
The job has a retention of 1 day but doesn't seem to be deleting the previous backup files. We manually delete the VBRZip generated files as part of the PowerShell scripts - we can do the same for the Proxmox backups if we need to.
I think that when we started using Veeam a few years ago the job scheduling might not have been as sophisticated as it is now, so we went down the Powershell script path and we also only have ESXi hosts and VMs.
I guess we were just assuming that our scripts would "just keep working" but perhaps we were a bit too optimistic.

[Mildur]

Hi Mark

Thanks for the details.

we can specifiy the destination folder in particular where we want the backup files to go.

Thats what Backup Repositories are for. You can specify the root folder for your repository. In that folder, a subfolder with the backup jobs name will be created.

So long as we know where the backup files are written we can move to our NAS and then to offsite backup (removable USB in our case).

Thats what Backup Copy jobs are for. Such job copies your restore points from your primary repository to a NAS or any other supported repository. We recommend to use backup copy jobs and let the backup server manage the copies.

The job has a retention of 1 day but doesn't seem to be deleting the previous backup files. We manually delete the VBRZip generated files as part of the PowerShell scripts - we can do the same for the Proxmox backups if we need to.

The lowest number of restore points you can keep with "forward forever incremental" jobs should be 1-2 backups. If you select retention type "days", it will be a minimum of 3 restore points.
We recommend to keep a few days of backups on your primar repository for fast restore scenarios. Imagine you need to restore from a few days ago. In your scenario you would have to import backups manually to the backup server to start a restore.

Best,
Fabian