Description field in Backup
- Thread starter jldalla
- Start date
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
+1 for thisI'm not sure if this can cover Snapshots as well, but definitely +1 for the backups.
This other post has some other +1 members, I just don't know how to request the feature properly.
http://forum.proxmox.com/threads/15953-Keep-Up-with-Backups
This other post has some other +1 members, I just don't know how to request the feature properly.
http://forum.proxmox.com/threads/15953-Keep-Up-with-Backups
I think, at this point any type of custom naming convention is better. A lot of times I find myself deleting vm120 for example, but have a backup of it that I can use for future Linux templates. Then upon creation of new vm, the original Linux template backup will get lost in the name scheme, or deleted because of number of backups are exceeded
I am sorry to bring down your expectations, but I feel pve team does not like changing their backup naming standard, or any other descriptive details about it, even if many could find it useful, even as an option: file naming obvioulsy has implications with the overall flow, like max_backups setting, but a workaround could be found.
This topic has surfaced this forum a few times, search the forums, but simply they end up to ignore requests like these. They don't want this to happen, apparently. Maybe for good reasons, but I don't know which.
In the past - years ago - I even submitted code (it's just some perl code, anyway, as a newbie the most difficult part was understand how vzdump worked) that worked on my pve - it also had an option to append vm conf to backup log IIRC, since extracting it from the big backup file is slow, but that code broke at first update (it was about 1.x versions IIRC), and I was discouraged.
Even if probably a post-backup script could rename backup files according to vm details, this will clash with the above max_backups setting and the like, so it's not a good way. Vzdump should handle this.
my 2c
Marco
This topic has surfaced this forum a few times, search the forums, but simply they end up to ignore requests like these. They don't want this to happen, apparently. Maybe for good reasons, but I don't know which.
In the past - years ago - I even submitted code (it's just some perl code, anyway, as a newbie the most difficult part was understand how vzdump worked) that worked on my pve - it also had an option to append vm conf to backup log IIRC, since extracting it from the big backup file is slow, but that code broke at first update (it was about 1.x versions IIRC), and I was discouraged.
Even if probably a post-backup script could rename backup files according to vm details, this will clash with the above max_backups setting and the like, so it's not a good way. Vzdump should handle this.
my 2c
Marco