From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication
Date: Tue, 5 Nov 2024 12:08:01 +0100 [thread overview]
Message-ID: <20241105110801.151806-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20241105110801.151806-1-a.lauterer@proxmox.com>
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvesr.adoc | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/pvesr.adoc b/pvesr.adoc
index 4fc2de1..209f306 100644
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -181,6 +181,12 @@ A replication job is identified by a cluster-wide unique ID. This ID is
composed of the VMID in addition to a job number.
This ID must only be specified manually if the CLI tool is used.
+Network
+-------
+
+By default, the replication traffic will choose the management network. To
+place the replication traffic on a specific network, configure the `Migration
+Network` over the web interface, `Datacenter -> Options -> Migration Settings`.
Command-line Interface Examples
-------------------------------
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-05 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 11:08 [pve-devel] [PATCH docs 1/2] pvesr: fix possible issues storage ID Aaron Lauterer
2024-11-05 11:08 ` Aaron Lauterer [this message]
2024-11-29 15:17 ` [pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication Fiona Ebner
2024-12-04 16:08 ` Aaron Lauterer
2024-11-29 15:18 ` [pve-devel] applied: [PATCH docs 1/2] pvesr: fix possible issues storage ID Fiona Ebner
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=20241105110801.151806-2-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.