mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-07-16 16:45:34 +00:00
cluster join: mention that storage config from cluster is inherited
and what to do about it. It's a rather common topic in forum threads. Suggested in the community forum: https://forum.proxmox.com/threads/118492/post-513743 Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
This commit is contained in:
parent
58e695ca6a
commit
aaf632d5fe
13
pvecm.adoc
13
pvecm.adoc
@ -172,11 +172,14 @@ infrastructure for bigger clusters.
|
|||||||
Adding Nodes to the Cluster
|
Adding Nodes to the Cluster
|
||||||
---------------------------
|
---------------------------
|
||||||
|
|
||||||
CAUTION: A node that is about to be added to the cluster cannot hold any guests.
|
CAUTION: All existing configuration in `/etc/pve` is overwritten when joining a
|
||||||
All existing configuration in `/etc/pve` is overwritten when joining a cluster,
|
cluster. In particular, a joining node cannot hold any guests, since guest IDs
|
||||||
since guest IDs could otherwise conflict. As a workaround, you can create a
|
could otherwise conflict, and the node will inherit the cluster's storage
|
||||||
backup of the guest (`vzdump`) and restore it under a different ID, after the
|
configuration. To join a node with existing guest, as a workaround, you can
|
||||||
node has been added to the cluster.
|
create a backup of each guest (using `vzdump`) and restore it under a different
|
||||||
|
ID after joining. If the node's storage layout differs, you will need to re-add
|
||||||
|
the node's storages, and adapt each storage's node restriction to reflect on
|
||||||
|
which nodes the storage is actually available.
|
||||||
|
|
||||||
Join Node to Cluster via GUI
|
Join Node to Cluster via GUI
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
Loading…
Reference in New Issue
Block a user