Change the note

Author: NataliaIvakina

modules/ROOT/pages/backup-restore/planning.adoc

@@ -177,7 +177,7 @@ They must be run directly on the databases that are associated with that Composi
 ====
 
 
-=== Considerations for backing up and restoring databases in a cluster
+== Considerations for backing up and restoring databases in a cluster
 
 Backing up a database in a clustered environment is not essentially different from a standalone backup, apart from the fact that you must know which server in a cluster to connect to.
 Use `SHOW DATABASE <database>` to learn which servers are hosting the database you want to back up.
@@ -187,11 +187,12 @@ However, _restoring_ a database in a cluster is different since it is not known
 This method relies on the seed already existing on one of the servers.
 The recommended way to restore a database in a cluster is to xref::database-administration/standard-databases/seed-from-uri.adoc[seed from URI].
 
-[NOTE]
+[IMPORTANT]
 ====
-When backing up a clustered database, use the `--include-metadata=all` option.
-This option ensures that the backup includes not only `users` and `roles`, but also the cluster topology.
-Cluster topology metadata, stored in the `system` database, defines the servers in the cluster and their operational modes.
+When backing up a clustered database, be aware that the xref:clustering/introduction.adoc#clustering-introduction-operational[cluster topology] metadata is not included in the backup.
+The cluster topology is stored in the `system` database and describes how the copies of a database should be spread across the servers in a cluster.
+
+Because this metadata is excluded from backups, restoring to a new cluster environment requires manual reconfiguration of servers modes and database allocations. 
 ====
 
 [[backup-planning-databases]]