[pve-devel] [PATCH docs 1/2] pvesr: fix possible issues storage ID

[pve-devel] [PATCH docs 1/2] pvesr: fix possible issues storage ID

[Aaron Lauterer]

The same storage needs to be configured on the target node for the
replication to work.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 pvesr.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pvesr.adoc b/pvesr.adoc
index 9eda008..4fc2de1 100644
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -101,7 +101,7 @@ setup there may be another cause.
 
 * No free space left on the replication target storage.
 
-* Storage with same storage ID available on the target node
+* Storage with same storage ID is not available on the target node
 
 NOTE: You can always use the replication log to find out what is causing the problem.
 
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication

[Aaron Lauterer]

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