Online Backup of NDB Cluster Waiting for started, this may take several minutes Node 2: Backup 3 started from node 1 ndb_mgm> START BACKUP WAIT STARTED SNAPSHOTSTART START BACKUP SNAPSHOTSTART WAIT STARTED START BACKUP 4 WAIT COMPLETED SNAPSHOTSTART START BACKUP SNAPSHOTEND WAIT COMPLETED START BACKUP 4 NOWAIT SNAPSHOTSTART ndb_mgm>  START BACKUP Waiting for completed, this may take several minutes Node 2: Backup 1 started from node 1 Node 2: Backup 1 started from node 1 completed  StartGCP: 177 StopGCP: 180  #Records: 7362 #LogRecords: 0  Data: 453648 bytes Log: 0 bytes ndb_mgm> Node 2: Backup 1 started from node 1 Backup  backup_id  started from node  node_id  completed Backup  backup_id  started from node  node_id 3. When the backup has started the management client displays this message: 4. The management client indicates with a message like this one that the backup has started: 2. Execute the  START BACKUP  command. This produces several lines of output indicating the progress of the backup, as shown here: 1. Start the management client ( ndb_mgm ), if it not running already. •  WAIT COMPLETED  causes the management client to wait until the backup process is complete before returning control to the user. WAIT COMPLETED  is the default. A  snapshot_option  can be used to determine whether the backup matches the state of the cluster when  START BACKUP  was issued, or when it was completed.  SNAPSHOTSTART  causes the backup to match the state of the cluster when the backup began;  SNAPSHOTEND  causes the backup to reflect the state of the cluster when the backup was finished.  SNAPSHOTEND  is the default, and matches the behavior found in previous NDB Cluster releases. If you use the  SNAPSHOTSTART  option with  START BACKUP , and the CompressedBackup  parameter is enabled, only the data and control files are compressed—the log file is not compressed. If both a  wait_option  and a  snapshot_option  are used, they may be specified in either order. For example, all of the following commands are valid, assuming that there is no existing backup having 4 as its ID: The procedure for creating a backup consists of the following steps: backup_id  is the unique identifier for this particular backup. This identifier is saved in the cluster log, if it has not been configured otherwise.  node_id  is the identifier of the management server that is coordinating the backup with the data nodes. At this point in the backup process the cluster has received and processed the backup request. It does not mean that the backup has finished. An example of this statement is shown here: 4493 Note