It would be nice to add Tags based selection in Backup Job. Right now it does not have tags support and I have to add my VMs which I want to include in backup job to pool and select the pool in selection mode.
[Suggestion] Add Tags based selection mode in backup job
- Thread starter encryptedserver
- Start date
-
- Tags
- backup and restore
Yes, we discussed already internally that such a thing would be nice to have.
But I'd not cram it as yet another selection mode in, but see if we can rework the whole to something in the spirit of the new bulk-action (start, migrate, stop, suspend) filters, as that is quite flexible but still relatively easy to understand and work with.
The most work would be ensuring the matchers/filters are sound and can cover use-cases also in other areas.
As compared to the bulk-action filter this would not be done only in the frontend but implemented in the backend, and needs to be supported for a long time and should be ideally re-useable for all other sorts of endpoints where a list of VM can be passed.
Anyhow, feel free to open an enhancement request over at our Bugzilla so that we have this properly tracked:
https://bugzilla.proxmox.com/
But I'd not cram it as yet another selection mode in, but see if we can rework the whole to something in the spirit of the new bulk-action (start, migrate, stop, suspend) filters, as that is quite flexible but still relatively easy to understand and work with.
The most work would be ensuring the matchers/filters are sound and can cover use-cases also in other areas.
As compared to the bulk-action filter this would not be done only in the frontend but implemented in the backend, and needs to be supported for a long time and should be ideally re-useable for all other sorts of endpoints where a list of VM can be passed.
Anyhow, feel free to open an enhancement request over at our Bugzilla so that we have this properly tracked:
https://bugzilla.proxmox.com/
I have VMs tagged as [production] [lab] [template] and even though lab might be running I only want production to be backed up.
Similar here. I would also like to make use of tag-based backups. I am helping myself currently with some scripting around pvesh.
Depending how it gets implemented, bulk actions might work if they are able to get preconfigured and scheduled. Resource pool based backup jobs are of no value for my environment.
+1
The lack of this feature is problematic for us and unfortunately prevents us from switching to this backup solution. It would be really great if we could do so.
The lack of this feature is problematic for us and unfortunately prevents us from switching to this backup solution. It would be really great if we could do so.
As a stopgap, even just being able to filter the VM list on the backup configuration page, like is possible for the bulk actions page, would be incredibly helpful.
Hi everyone,
We would also like to see tag-based backup job selection implemented in Proxmox VE.
We are currently migrating a large VMware environment to Proxmox VE.
Our goal is to dynamically assign VMs to backup jobs based on freely configurable tags instead of relying on resource pools or manually maintaining VM selections.
Tags should be evaluated at backup execution time, ensuring that newly created VMs are automatically included in the appropriate backup jobs when matching tags are assigned.
This would simplify backup management, improve automation, and reduce the risk of VMs being unintentionally excluded from backups.
We have also added our use case to the existing feature request:
https://bugzilla.proxmox.com/show_bug.cgi?id=4186
Is there any update on the implementation status or potential roadmap for this feature?
We would also like to see tag-based backup job selection implemented in Proxmox VE.
We are currently migrating a large VMware environment to Proxmox VE.
Our goal is to dynamically assign VMs to backup jobs based on freely configurable tags instead of relying on resource pools or manually maintaining VM selections.
Tags should be evaluated at backup execution time, ensuring that newly created VMs are automatically included in the appropriate backup jobs when matching tags are assigned.
This would simplify backup management, improve automation, and reduce the risk of VMs being unintentionally excluded from backups.
We have also added our use case to the existing feature request:
https://bugzilla.proxmox.com/show_bug.cgi?id=4186
Is there any update on the implementation status or potential roadmap for this feature?