GithubHelp home page GithubHelp logo

Comments (4)

franklupo avatar franklupo commented on June 15, 2024

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

from cv4pve-barc.

gardar avatar gardar commented on June 15, 2024

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

from cv4pve-barc.

flames avatar flames commented on June 15, 2024

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

from cv4pve-barc.

franklupo avatar franklupo commented on June 15, 2024

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

from cv4pve-barc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.