Client-level VM/CT Backup Management - Configurable via usage (vzdump)

[jbrouhard98]

Clients may want to have the ability to create/manage their backups, or even restore from a previous backup themselves.

[lsthompson]

We support the idea. This makes sense to do.

https://pve.proxmox.com/wiki/Backup_and_Restore
https://pve.proxmox.com/pve-docs/chapter-vzdump.html

Need to explore a bunch of things:

• option to have backups visible at all
• pruning configuration (keep-last etc)
• vzdump mode (snapshot/suspend/stop)
• restricted scheduling/firing of dump jobs
• whether self-service restores can happen

[jbrouhard98]

From experience granting a user access to PVE Realm:

The end user can absolutely trigger their own backups, and i have confirmed they can restore directly if they have the permissions of VM.Backup, VM.Snapshot. and VM.Snapshot.Rollback. To view the repo,they need Datastore.AllocateSpace, Datastore.AllocateTemplate and Datastore.Audit just to be able to view the datastores.

As for backups visible... I think it's possible if you query the datastore, and look for vzdump-qemu-{VMID}-[[[date]]].vma.zst. Querying for the VMID and matching it to the client's VM ID should be sufficient?

Default backup is "snapshot"

[lsthompson]

I like your thought process there. Modules Garden are pushing hard now that we're around:

https://www.modulesgarden.com/products/whmcs/proxmox-ve-vps#changelog

There are some key things it does which I'd like to see parity with.