From: Tom Weber <pve@junkyard.4t2.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Proxmox Backup Server (beta)
Date: Thu, 16 Jul 2020 15:03:49 +0200 [thread overview]
Message-ID: <4b7e3a23d9b1f41ef51e6363373072d265797380.camel@junkyard.4t2.com> (raw)
In-Reply-To: <0852a3fa-ab39-d551-5a01-0264687d4b56@proxmox.com>
Am Dienstag, den 14.07.2020, 17:52 +0200 schrieb Thomas Lamprecht:
>
> 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.
So there is exactly one dirty-bitmap that get's nulled after a backup?
I'm asking because I have Backup setups with 2 Backup Servers at
different Locations, backing up (file-level, incremental) on odd days
to server1 on even days to server2.
Such a setup wouldn't work with the block level incremental backup and
the dirty-bitmap for pve vms + pbs, right?
Regards,
Tom
next prev parent reply other threads:[~2020-07-16 13:10 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 10:56 [pve-devel] " Martin Maurer
2020-07-10 10:56 ` [PVE-User] " Martin Maurer
2020-07-10 10:56 ` [pbs-devel] " Martin Maurer
2020-07-10 11:42 ` [PVE-User] " 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
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 [this message]
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 ` [pve-devel] " Lee Lists
2020-10-06 13:12 ` Lee Lists
2020-10-08 8:21 ` [pve-devel] " Thomas Lamprecht
2020-10-08 8:21 ` Thomas Lamprecht
2020-10-08 8:21 ` [pbs-devel] " Thomas Lamprecht
2020-10-09 9:27 ` [pve-devel] " Lee Lists
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=4b7e3a23d9b1f41ef51e6363373072d265797380.camel@junkyard.4t2.com \
--to=pve@junkyard.4t2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.