NDB Cluster Configuration Files Enabling this parameter causes backup files to be compressed. The compression used is equivalent to  gzip --fast , and can save 50% or more of the space required on the data node to store uncompressed backup files. Compressed backups can be enabled for individual data nodes, or for all data nodes (by setting this parameter in the  [ndbd default]  section of the  config.ini  file). You cannot restore a compressed backup to a cluster running a MySQL version that does not support this feature. The default value is  0  (disabled). If set to 1, backups must be encrypted. While it is possible to set this parameter for each data node individually, it is recommended that you set it in the  [ndbd default]  section of the config.ini  global configuration file. For more information about performing encrypted backups, see Section 23.5.8.2, “Using The NDB Cluster Management Client to Create a Backup” . Added in NDB 8.0.22. The location of the backup files is determined by the  BackupDataDir  data node configuration parameter. Additional requirements.   When specifying these parameters, the following relationships must hold true. Otherwise, the data node cannot start. The  [ndbd]  parameters discussed in this section are used in scheduling and locking of threads to specific CPUs on multiprocessor data node hosts. To make use of these parameters, the data node process must be run as system root. NDB Cluster Realtime Performance Parameters • BuildIndexThreads • BackupDataBufferSize >= BackupWriteSize + 188KB • BackupLogBufferSize >= BackupWriteSize + 16KB • BackupMaxWriteSize >= BackupWriteSize • RequireEncryptedBackup Note Note 4123 Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.22 Type or units integer Default 0 Range 0 - 1 Added NDB 8.0.22 Restart Type N (NDB 8.0.13) Important