Skip to content
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

Open
gardar opened this issue Feb 7, 2018 · 4 comments
Open

Different schedules for the same vm? #28

gardar opened this issue Feb 7, 2018 · 4 comments

Comments

@gardar
Copy link

gardar commented Feb 7, 2018

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.

@franklupo
Copy link
Member

Hi,
nice idea. This is true if we maintain the same times of execution, very difficult.
I think the real problem is the first complete image, which is heavy.

Best regards

@gardar
Copy link
Author

gardar commented Feb 12, 2018

How about using one initial complete image, and then keep daily/weekly/monthly diffs for that same inital image?

@flames
Copy link
Contributor

flames commented Mar 29, 2019

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)...:
the diffs are not "differential" as the name suggests, but incremental.

  1. differential is, where every diff depends on the initial image
  2. incremental is, where diffs depend on previous diffs, and only the first diff depends on initial image
    if we want to maintain one initial image and different diffs for d/w/m, they need to be dependent on initial image.

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 :(

@franklupo
Copy link
Member

Hello,
except for the initial image, the diffs depend on the previous diff. So the first diff depends on the initial image, the second diff depends on the first diff and so on.
An option to make the first smaller image is to export it as 'diff' with 'rbd export-diff' instead of 'rbd export'.
One of the problems with this solution is that it can only be restored in CEPH.
The current backup exports a RAW image, which can be restored to any system not only CEPH.

I am developing a new plug-in version with a client running outside of Proxmox VE, using the Web API.
I'm developing in C # dotnet core.

I'll release a beta version in a few weeks.

Thank you all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants