NDB Cluster Backups With NDB Cluster Replication IP address or host name of the  NDB  management server for the source cluster, and  port  is the management server’s port number: ndb-connectstring= management_host [: port ] shell S >  ndb_mgm -e "START BACKUP"  In this case, the backup can be started by executing this statement on the replication source: Note The port number needs to be specified only if the default port (1186) is not being used. See Section 23.2.3, “Initial Configuration of NDB Cluster” , for more information about ports and port allocation in NDB Cluster. • Method B.   If the  my.cnf  file does not specify where to find the management host, you can start the backup process by passing this information to the  NDB  management client as part of the  START BACKUP  command. This can be done as shown here, where  management_host  and  port  are the host name and port number of the management server: shell S >  ndb_mgm  management_host : port  -e "START BACKUP" shell S >  ndb_mgm rep-source:1186 -e "START BACKUP" In our scenario as outlined earlier (see Section 23.6.5, “Preparing the NDB Cluster for Replication” ), this would be executed as follows: 2. Copy the cluster backup files to the replica that is being brought on line. Each system running an  ndbd process for the source cluster has cluster backup files located on it, and  all  of these files must be copied to the replica to ensure a successful restore. The backup files can be copied into any directory on the computer where the replica’s management host resides, as long as the MySQL and NDB binaries have read permissions in that directory. In this case, we assume that these files have been copied into the directory  /var/BACKUPS/BACKUP-1 . 3. Create any databases on the replica cluster that are present on the source cluster and that are to be replicated. While it is not necessary that the replica cluster have the same number of data nodes as the source, it is highly recommended this number be the same. It  is  necessary that the replication process is prevented from starting when the replica server starts. You can do this by starting the replica with the --skip-slave-start  option on the command line, by including  skip-slave-start  in the replica’s my.cnf  file, or in MySQL 8.0.24 or later, by setting the  skip_slave_start  system variable. In MySQL 8.0.22 or later, you can also use this statement: A  CREATE DATABASE  (or  CREATE SCHEMA ) statement corresponding to each database to be replicated must be executed on each SQL node in the replica cluster. 4631 Important 4. Reset the replica cluster using this statement in the  mysql  client: mysql R >  RESET SLAVE; mysql R >  RESET REPLICA;