-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different schedules for the same vm? #28
Comments
Hi, Best regards |
How about using one initial complete image, and then keep daily/weekly/monthly diffs for that same inital image? |
though, this is a highly needed feature, but i see a problem there maintaining one initial image and do separate diffs for daily/weekly/monthly. please correct me, if i am wrong (new to this stuff)...:
differential backup is the imho the best of both worlds, it takes a little more space than incremental, but still less than full backups (this is why we are here and not using the default proxmox backup feature). But still safe enough to restore a "selected date" even if previous (those between initial image and the selected diff) deltas are not available or broken. the --label parameter allows to make different schedules, but with one full initial image per schedule. i don't see a better way with ceph export :( |
Hello, I am developing a new plug-in version with a client running outside of Proxmox VE, using the Web API. I'll release a beta version in a few weeks. Thank you all |
It would be neat if we could do different schedules on the same, for example to keep 5 daily backup, 3 weekly and 1 monthly, etc. backups.
Currently we can do this by setting up a seperate backup job, but that would mean the other backup jobs are taken at the same time, so for example when the monthly backup is taken we would take a daily, weekly and a monthly backup all at the same time.
A better way would be if the daily backup would be taken and copied as a weekly and a monthly backup rather than having to run three backup procedures.
The text was updated successfully, but these errors were encountered: