Skip to content

Commit c2fbd32

Browse files
Update Backups guide in preparation for rabbitmq/rabbitmq-server#10367 rabbitmq/rabbitmq-server#10369
1 parent 5068b4f commit c2fbd32

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

site/backup.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -113,18 +113,8 @@ copy the messages, skip copying the [message directories](#manual-messages-backu
113113

114114
### <a id="manual-definitions-restore" class="anchor" href="#manual-definitions-restore">Restoring from a Manual Definitions Backup</a>
115115

116-
Internal node database stores node's name in certain records. Should node name change, the database must first
117-
be updated to reflect the change using the following [rabbitmqctl](./cli.html) command:
118-
119-
<pre class="lang-sh">
120-
rabbitmqctl rename_cluster_node &lt;oldnode&gt; &lt;newnode&gt;
121-
</pre>
122-
123-
The command can take multiple old name/new name pairs if multiple nodes in a cluster are being renamed
124-
at the same time.
125-
126-
When a new node starts with a backed up directory and a matching node name, it should perform
127-
the upgrade steps as needed and proceed booting.
116+
To perform a restore, a new node starts with a backed up directory and the original node name.
117+
The node then should perform the upgrade steps as needed and proceed booting.
128118

129119

130120
## <a id="messages-backup" class="anchor" href="#messages-backup">Backing Up Messages</a>

0 commit comments

Comments
 (0)