X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pvecm.adoc;h=2b7f5d21825379a34528b6c947612075c2cffc46;hp=08f38e569b72472aa4249223d347047185d8e2b1;hb=3be22308fb07213fb33b8781932d6ab8675e9cc4;hpb=69255fd2e256fd19cbd90830ccfe19b5bf69731e

diff --git a/pvecm.adoc b/pvecm.adoc
index 08f38e5..2b7f5d2 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -303,13 +303,12 @@ access to the shared storages! This must be resolved before you start removing
 the node from the cluster. A {pve} cluster cannot share the exact same
 storage with another cluster, as it leads to VMID conflicts.
 
-Move the guests which you want to keep on this node now, after the removal you
-can do this only via backup and restore. Its suggested that you create a new
-storage where only the node which you want to separate has access. This can be
-an new export on your NFS or a new Ceph pool, to name a few examples. Its just
-important that the exact same storage does not gets accessed by multiple
-clusters. After setting this storage up move all data from the node and its VMs
-to it. Then you are ready to separate the node from the cluster.
+Its suggested that you create a new storage where only the node which you want
+to separate has access. This can be an new export on your NFS or a new Ceph
+pool, to name a few examples. Its just important that the exact same storage
+does not gets accessed by multiple clusters. After setting this storage up move
+all data from the node and its VMs to it. Then you are ready to separate the
+node from the cluster.
 
 WARNING: Ensure all shared resources are cleanly separated! You will run into
 conflicts and problems else.