From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 502716DE36 for ; Thu, 19 Aug 2021 16:22:57 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 428422734A for ; Thu, 19 Aug 2021 16:22:57 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id D35042733C for ; Thu, 19 Aug 2021 16:22:52 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 9745743473; Thu, 19 Aug 2021 16:22:52 +0200 (CEST) To: Proxmox VE development discussion , =?UTF-8?Q?Rados=c5=82aw_Korzeniewski?= References: From: Stefan Reiter Message-ID: <6bd6cbed-5519-cb7e-628c-13e934639652@proxmox.com> Date: Thu, 19 Aug 2021 16:22:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 1.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.891 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] VM Incremental backup for 3-party solution (Qemu) X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2021 14:22:57 -0000 On 8/19/21 3:21 PM, Radosław Korzeniewski wrote: > Hello, > > I'm working on implementing VM incremental backup for a 3-party solution > based on Qemu dirty bitmap which is available in Proxmox. Unfortunately I'm > unable to make it working, so I decided to ask for some help. > First I'm adding a dirty bitmap using the `block-dirty-bitmap-add` command > and making a full backup with `drive-backup` command. > Both are executed in transactions. The bitmap is successfully added. > But the external backup file is populated with ~193K of data and hung. > The backup job is added and QMP returns 3 events: > `"status": "created"`, `"status": "running"`, `"status": "paused"`. > I'm not sure why. > As finally the job is "paused", I try to resume it with `block-job-resume` > command > the `query-block-jobs` returns `"status": "paused"` i `"paused": true`. > All I can do is to cancel the job with the `block-job-cancel` command. > No commands return any error. > > Do you have any idea why the job fell into a paused state and how I > should proceed? > Hi, as a shot in the dark I would say you specified the bitmap in your initial backup command, and it only backed up what had been written between the time you did 'bitmap-add' and 'drive-backup'.. But more importantly, 'drive-backup' and the bitmap support around that are not based on our code, they are from upstream QEMU. We implement the 'backup' and 'query-backup' QMP calls. There's nothing against using the native calls if they fit your use case, but for support it would make more sense to contact upstream and read through their documentation :) ~ Stefan