From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 84BDE1FF0DE for ; Thu, 19 Nov 2026 11:40:18 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 8BFAB21A43; Thu, 19 Nov 2026 11:37:01 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH docs v4 36/41] vzdump: restore: describe what a failed restore can leave behind Date: Thu, 19 Nov 2026 11:34:22 +0100 Message-ID: <20261119103551.1666964-37-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261119103551.1666964-1-t.lamprecht@proxmox.com> References: <20261119103551.1666964-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795084557570 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.159 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: HFHAWY4HCIY3NRFZCDCQPRXMQUG556NQ X-Message-ID-Hash: HFHAWY4HCIY3NRFZCDCQPRXMQUG556NQ X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: A restore that fails or gets killed can leave a locked guest behind, or a placeholder and volumes at a VMID that was free before. The backup and restore chapter did not mention that, nor how to clean up. Describe when a guest stays and is locked, how to remove a placeholder and the volumes that no guest config references anymore, and when a retry needs another VMID. Signed-off-by: Thomas Lamprecht --- changes v3 -> v4: * new in v4: the part about locks and leftovers from the 'Failed Restores' section of the guest identity patch, as a section of the restore chapter, since it does not depend on the identity * added there: a guest stays, locked, if its cleanup cannot remove a volume or the firewall config, and '--destroy-unreferenced-disks' removes all other volumes of the VMID, also of an earlier guest, with how to check first vzdump.adoc | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/vzdump.adoc b/vzdump.adoc index 44db027..7587580 100644 --- a/vzdump.adoc +++ b/vzdump.adoc @@ -563,6 +563,34 @@ file in `/var/log/proxmox-backup/file-restore/`. The log file might contain additional information in case an attempt to restore individual files or accessing file systems contained in a backup archive fails. +[[vzdump_restore_failed]] +Failed Restores +~~~~~~~~~~~~~~~ + +A restore that fails or is stopped can leave the guest behind, for example a +restore over an existing guest, or a VM restore that fails after it restored the +data or in the live phase of a live restore. A container restore over an +existing container that fails after it destroyed the old container removes the +container, unless the cleanup cannot remove a volume, also one of the old +container, or the firewall config. The container then stays locked. If the +restore task was killed, the guest can also stay locked. Remove the lock with +`qm unlock ` or `pct unlock ` before you retry the restore or remove +the guest. + +A restore to a free VMID that fails before it restored the data normally +removes the guest again. If the restore task was killed, or if the cleanup could +not remove a volume or the firewall config, a locked placeholder can stay at +that VMID instead. Unlock it as described above and remove it, for example with +`qm destroy ` or `pct destroy `. With +`--destroy-unreferenced-disks 1`, the command also removes all other volumes +with that VMID on the enabled storages. These include volumes that a killed +restore created or that the cleanup could not remove, but can also be volumes +of an earlier guest, so check them first with +`pvesm list --vmid `. In both cases, restore again. +Use another VMID if the xref:pvecm_next_id_range[`next-id`] setting of the +datacenter has the `unique` and `enforce` options set, as the first VMID then +counts as used. + [[vzdump_configuration]] Configuration ------------- -- 2.47.3