From: Alexandre DERUMIER <aderumier@odiso.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox Backup Server (beta)
Date: Tue, 14 Jul 2020 23:17:16 +0200 (CEST) [thread overview]
Message-ID: <1788232040.275836.1594761436288.JavaMail.zimbra@odiso.com> (raw)
In-Reply-To: <0852a3fa-ab39-d551-5a01-0264687d4b56@proxmox.com>
>>Proxmox Backup Server effectively does that too, but independent from the
>>source storage. We always get the last backup index and only upload the chunks
>>which changed. For running VMs dirty-bitmap is on to improve this (avoids
>>reading of unchanged blocks) but it's only an optimization - the backup is
>>incremental either way.
What happen if a vm or host crash ? (I think on clean shutdown, the dirty-bitmap is saved, but on failure ?)
does it need to re-read all blocks to find diff ? or make a new full backup ?
Is it possible to read files inside a vm backup, without restoring it first ?
(Don't have check vma format recently, but I think it was not possible because of out of orders blocks)
I really think it could be great to add some storage snapshot feature in the future.
For ceph, the backup speed is really faster because it's done a bigger block than 64K. (I think it's 4MB object).
and also, I really need a lot of space for my backups, and I can't fill them in a single local storage. (don't want to play with multiple datastores)
Bonus, it could also be used for disaster recovery management :)
But that seem really great for now, I known a lot of people that will be happy with PBS :)
Congrats to all proxmox team !
----- Mail original -----
De: "Thomas Lamprecht" <t.lamprecht@proxmox.com>
À: "aderumier" <aderumier@odiso.com>, "Proxmox VE user list" <pve-user@lists.proxmox.com>
Envoyé: Mardi 14 Juillet 2020 17:52:41
Objet: Re: [PVE-User] Proxmox Backup Server (beta)
Hi,
On 14.07.20 16:30, Alexandre DERUMIER wrote:
> I don't have tested it yet and read the full docs,
The following gives a quick overview:
https://pbs.proxmox.com/docs/introduction.html#main-features
>
> but it is possible to do ceph to ceph backup with ceph snapshots (instead qemu bitmap tracking)?
No. ceph, or other storage snapshots, are not used for backup in PBS.
>
> Currently in production, we are backuping like that, with incremental snapshot,
>
> we keep X snapshots on ceph backup storage by vm, and production ceph cluster only keep the last snasphot.
>
> The main advantage, is that we are only doing a full backup once, then incremental backups forever.
> (and we have checkum verifications,encryption,...) on ceph backup
Proxmox Backup Server effectively does that too, but independent from the
source storage. We always get the last backup index and only upload the chunks
which changed. For running VMs dirty-bitmap is on to improve this (avoids
reading of unchanged blocks) but it's only an optimization - the backup is
incremental either way.
> We can restore full block volume, but also selected files with mounting the volume with nbd.
There's a block driver for Proxmox Backup Server, so that should work just
the same way.
next prev parent reply other threads:[~2020-07-14 21:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 10:56 Martin Maurer
2020-07-10 11:42 ` Roland
2020-07-10 12:09 ` Dietmar Maurer
2020-07-10 12:24 ` Roland
2020-07-10 13:43 ` Thomas Lamprecht
2020-07-10 14:06 ` Roland
2020-07-10 14:15 ` Thomas Lamprecht
2020-07-10 14:46 ` Roland
2020-07-10 17:31 ` Roland
2020-07-10 13:44 ` Dietmar Maurer
[not found] ` <mailman.77.1594381090.12071.pve-user@lists.proxmox.com>
2020-07-10 11:45 ` Dietmar Maurer
[not found] ` <a92c7f1d-f492-2d43-00b9-15bdb0e805ec@binovo.es>
2020-07-10 13:50 ` Thomas Lamprecht
2020-07-10 12:03 ` Lindsay Mathieson
2020-07-10 12:13 ` Dietmar Maurer
2020-07-10 15:41 ` Dietmar Maurer
2020-07-11 11:03 ` mj
2020-07-11 11:38 ` Thomas Lamprecht
2020-07-11 13:34 ` mj
2020-07-11 13:47 ` Thomas Lamprecht
2020-07-11 14:40 ` Dietmar Maurer
2020-07-14 14:30 ` Alexandre DERUMIER
2020-07-14 15:52 ` Thomas Lamprecht
2020-07-14 21:17 ` Alexandre DERUMIER [this message]
2020-07-15 4:52 ` Thomas Lamprecht
[not found] ` <176392164.4390.1594849016963.JavaMail.zimbra@numberall.com>
2020-07-16 7:33 ` Thomas Lamprecht
[not found] ` <mailman.204.1594849027.12071.pve-user@lists.proxmox.com>
2020-07-16 10:17 ` Wolfgang Bumiller
2020-07-16 14:36 ` Mark Schouten
2020-07-16 17:04 ` Thomas Lamprecht
2020-07-16 13:03 ` Tom Weber
2020-07-17 7:31 ` Fabian Grünbichler
2020-07-17 13:23 ` Tom Weber
2020-07-17 17:43 ` Thomas Lamprecht
2020-07-18 14:59 ` Tom Weber
2020-07-18 18:07 ` Thomas Lamprecht
2020-07-10 12:45 ` Iztok Gregori
2020-07-10 13:41 ` Dietmar Maurer
2020-07-10 15:20 ` Iztok Gregori
2020-07-10 15:31 ` Dietmar Maurer
2020-07-10 16:29 ` Iztok Gregori
2020-07-10 16:46 ` Dietmar Maurer
[not found] ` <a1e5f8dd-efd5-f8e2-50c1-683d42b0f61b@truelite.it>
2020-07-10 14:23 ` Thomas Lamprecht
2020-07-10 15:59 ` Lindsay Mathieson
[not found] ` <mailman.86.1594396120.12071.pve-user@lists.proxmox.com>
2020-07-10 16:32 ` Dietmar Maurer
2020-10-06 13:12 ` Lee Lists
2020-10-08 8:21 ` Thomas Lamprecht
2020-10-09 9:27 ` Lee Lists
2020-10-09 12:10 Lee Lists
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=1788232040.275836.1594761436288.JavaMail.zimbra@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-user@lists.proxmox.com \
--cc=t.lamprecht@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