From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pvesr: remove note about offline migration
Date: Wed, 19 Oct 2022 12:35:28 +0200 [thread overview]
Message-ID: <20221019103528.589124-1-a.lauterer@proxmox.com> (raw)
It has been possible since quite a while to live migrate replicated
guests.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvesr.adoc | 1 -
1 file changed, 1 deletion(-)
diff --git a/pvesr.adoc b/pvesr.adoc
index e508eee..1981b9c 100644
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -46,7 +46,6 @@ but not twice to the same target node.
Each replications bandwidth can be limited, to avoid overloading a storage
or server.
-Guests with replication enabled can currently only be migrated offline.
Only changes since the last replication (so-called `deltas`) need to be
transferred if the guest is migrated to a node to which it already is
replicated. This reduces the time needed significantly. The replication
--
2.30.2
next reply other threads:[~2022-10-19 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 10:35 Aaron Lauterer [this message]
2022-10-20 12:50 ` [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=20221019103528.589124-1-a.lauterer@proxmox.com \
--to=a.lauterer@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