From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v3 docs 2/2] Revert "qm: freeze-fs-on-backup: remove reference to GUI"
Date: Thu, 23 Mar 2023 12:02:48 +0100 [thread overview]
Message-ID: <20230323110248.344718-2-c.heiss@proxmox.com> (raw)
In-Reply-To: <20230323110248.344718-1-c.heiss@proxmox.com>
This reverts commit 0025e843194130ec5223d5789fa01f916d189783.
The option is now also exposed in the GUI.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v2 -> v3:
* New patch
qm.adoc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 0726b29..15ac2fc 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1089,8 +1089,9 @@ Writer VSS module in a mode that breaks the SQL Server backup chain for
differential backups.
For such setups you can configure {pve} to not issue a freeze-and-thaw cycle on
-backup by setting the `freeze-fs-on-backup` QGA option to `0`. This option can
-be set via the CLI or the API.
+backup by setting the `freeze-fs-on-backup` QGA option to `0`. This can also be
+done via the GUI with the 'Freeze/thaw guest filesystems on backup for
+consistency' option.
IMPORTANT: Disabling this option can potentially lead to backups with inconsistent
filesystems and should therefore only be disabled if you know what you are
--
2.39.2
next prev parent reply other threads:[~2023-03-23 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:02 [pve-devel] [PATCH v3 manager 1/2] ui: qga: Add option to turn off QGA fs-freeze/-thaw on backup Christoph Heiss
2023-03-23 11:02 ` Christoph Heiss [this message]
2023-06-07 16:28 ` [pve-devel] applied: [PATCH v3 docs 2/2] Revert "qm: freeze-fs-on-backup: remove reference to GUI" Thomas Lamprecht
2023-05-04 6:08 ` [pve-devel] [PATCH v3 manager 1/2] ui: qga: Add option to turn off QGA fs-freeze/-thaw on backup Christoph Heiss
2023-05-04 14:58 ` Lukas Wagner
2023-06-07 16:28 ` [pve-devel] applied: " Thomas Lamprecht
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=20230323110248.344718-2-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox