From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve@junkyard.4t2.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id E0AA1639CD
 for <pve-user@lists.proxmox.com>; Thu, 16 Jul 2020 15:10:36 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id D329B14C0C
 for <pve-user@lists.proxmox.com>; Thu, 16 Jul 2020 15:10:36 +0200 (CEST)
Received: from mxf.4t2.com (mxf.4t2.com [78.47.65.59])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 6602E14C01
 for <pve-user@lists.proxmox.com>; Thu, 16 Jul 2020 15:10:36 +0200 (CEST)
X-Spam-Status: No
X-4t2Systems-MailScanner-Watermark: 1595509430.30104@aN82QMU9KRxcE0539iLPrA
X-4t2Systems-MailScanner-From: pve@junkyard.4t2.com
X-4t2Systems-MailScanner: Found to be clean
X-4t2Systems-MailScanner-ID: D7A9B4146A.A0320
X-4t2Systems-MailScanner-Information: processed at mxf.4t2.com
Received: from mailrelay.abyss.4t2.com (mailrelay.abyss.4t2.com [192.168.1.11])
 by mxf.4t2.com (Postfix) with ESMTP id D7A9B4146A
 for <pve-user@lists.proxmox.com>; Thu, 16 Jul 2020 15:03:49 +0200 (CEST)
Received: from mailserv.abyss.4t2.com (mailserv.abyss.4t2.com [192.168.1.12])
 by mailrelay.abyss.4t2.com (Postfix) with ESMTP id C061B382
 for <pve-user@lists.proxmox.com>; Thu, 16 Jul 2020 15:03:49 +0200 (CEST)
Received: from [10.8.1.101] (zerberus.abyss.4t2.com [192.168.1.254])
 (Authenticated sender: x)
 by mailserv.abyss.4t2.com (Postfix) with ESMTPSA id A21D72063E
 for <pve-user@lists.proxmox.com>; Thu, 16 Jul 2020 15:03:49 +0200 (CEST)
Message-ID: <4b7e3a23d9b1f41ef51e6363373072d265797380.camel@junkyard.4t2.com>
From: Tom Weber <pve@junkyard.4t2.com>
To: pve-user@lists.proxmox.com
Date: Thu, 16 Jul 2020 15:03:49 +0200
In-Reply-To: <0852a3fa-ab39-d551-5a01-0264687d4b56@proxmox.com>
References: <c84ac772-d577-27fd-710c-293d8a4baffe@proxmox.com>
 <7d1bd7a4-f47b-4a1a-9278-ff1889508c33@gmail.com>
 <1768587204.461.1594383204281@webmail.proxmox.com>
 <450971473.487.1594395714078@webmail.proxmox.com>
 <aa8534d4-174b-5069-e27b-160b8fb92d72@merit.unu.edu>
 <c51e8cf4-1c6d-051b-f91d-5d600a566c5a@proxmox.com>
 <c522fc9b-6b3f-7770-d32a-c1bb47961884@merit.unu.edu>
 <1514606299.525.1594478405167@webmail.proxmox.com>
 <16057806.272035.1594737045788.JavaMail.zimbra@odiso.com>
 <0852a3fa-ab39-d551-5a01-0264687d4b56@proxmox.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results:  0
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_PASS          -0.001 SPF: HELO matches SPF record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [PVE-User] Proxmox Backup Server (beta)
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2020 13:10:36 -0000

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