From: Andreas Heinlein <aheinlein@gmx.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] pbs incremental backups
Date: Tue, 2 Mar 2021 11:37:36 +0100 [thread overview]
Message-ID: <523edd9a-658d-5b49-c16d-3c0f6f973c13@gmx.com> (raw)
In-Reply-To: <82a59e22-1a52-e104-1217-ac904d9223ca@merit.unu.edu>
Hello,
this is probably a bit difficult to understand at first, but I will try
to explain.
Each backup is a full backup, even though only the differences to the
last backup are actually backed up. The remaining unchanged block are
just being referenced from the last backup. When you delete a previous
backup, only those blocks which are not referenced by another backup
will actually be deleted.
So each backup is independent on its own, and you can delete all
previous backups without losing any data.
Hope this clears it up a bit.
Bye,
Andreas
Am 02.03.2021 um 11:22 schrieb mj:
> Hi,
>
> Testing PBS backups taken from PVE VMs on ceph rbd now. Very nice,
> very quick, very cool. :-)
>
> We have a question. Something we wonder about.
>
> In our current backup software, we make weekly full_system backups,
> and daily incremental_system backups, each incremental based on the
> same full_system backup. So: each daily incremental backup becomes
> bigger, until the weekend. Then we make a new full_system backup to
> base the next set of incrementals on.
>
> In PBS I cannot specify if a backup is full or incremental, we assume
> this means that automatically the first backup is a full_system
> backup, and subsequent backups are incremental. The PBS backup logs
> confirm this assumption, saying: "scsi0: dirty-bitmap status: created
> new" vs "scsi0: dirty-bitmap status: OK (7.3 GiB of 501.0 GiB dirty)"
>
> And now the question: At what point in time is a new full_system
> backup created, to rebase incremental backups on?
> Or is each incremental backup based on the previous incremental? And
> if that is the case, how will we ever be able to delete one of the
> in-between incrementals, because that would then break to whole chain
> of incremental_backup-based-on-incremental_backup...?
>
> We have read the page
> https://qemu.readthedocs.io/en/latest/interop/bitmaps.html but it does
> not seem to answer this.
>
> Anyone care to share some insight on this logic and how PBS works?
>
> MJ
next prev parent reply other threads:[~2021-03-02 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 10:22 mj
2021-03-02 10:37 ` Andreas Heinlein [this message]
2021-03-02 10:48 ` Fabian Grünbichler
2021-03-03 7:48 ` mj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=523edd9a-658d-5b49-c16d-3c0f6f973c13@gmx.com \
--to=aheinlein@gmx.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox