What is New in NDB Cluster backup if it were not encrypted.  ndb_print_backup_file  and  ndbxfrm  can also read encrypted files using, respectively,  -P password  and  --decrypt-password= password . In all cases in which a password is supplied together with an option for encryption or decryption, the password must be quoted; you can use either single or double quotation marks to delimit the password. Beginning with NDB 8.0.24, several  NDB  programs, listed here, also support input of the password from standard input, similarly to how this is done when logging in interactively with the  mysql  client using the --password  option (without including the password on the command line): See the descriptions of the programs just listed for more information. It is also possible, beginning with NDB 8.0.22, to enforce encryption of backups by setting RequireEncryptedBackup=1  in the  [ndbd default]  section of the cluster global configuration file. When this is done, the  ndb_mgm  client rejects any attempt to perform a backup that is not encrypted. Beginning with NDB 8.0.24, you can cause  ndb_mgm  to use encryption whenever it creates a backup by starting it with  --encrypt-backup . In this case, the user is prompted for a password when invoking START BACKUP  if none is supplied. For IPv6 addressing to work, the operating platform and network on which the cluster is deployed must support IPv6. As when using IPv4 addressing, hostname resolution to IPv6 addresses must be provided by the operating platform. IPv4 addressing continues to be supported by  NDB . Using IPv4 and IPv6 addresses concurrently is not recommended, but can be made to work in the following cases: These cases work because  ndb_mgmd  does not bind to any IP address by default. To perform an upgrade from a version of  NDB  that does not support IPv6 addressing to one that does, provided that the network supports IPv4 and IPv6, first perform the software upgrade; after this has been 3951 •When the management node is configured with IPv6 and data nodes are configured with IPv4 addresses in the  config.ini  file: This works if  --bind-address  is not used with  mgmd , and data nodes are started with  --ndb-connectstring  set to the IPv4 address of the management nodes. •When the management node is configured with IPv4 and data nodes are configured with IPv6 addresses in  config.ini : Similarly to the other case, this works if  --bind-address  is not passed to  mgmd  and data nodes are started with  --ndb-connectstring  set to the IPv6 address of the management node. • IPv6 support.   Beginning with NDB 8.0.22, IPv6 addressing is supported for connections to management and data nodes; this includes connections between management and data nodes with SQL nodes. When configuring a cluster, you can use numeric IPv6 addresses, host names which resolve to IPv6 addresses or both. •Two  ndbxfrm  options,  --encrypt-password-from-stdin  and  --decrypt-password-from- stdin , cause similar behavior when using that program to encrypt or to decrypt a backup file. •For  ndb_mgm  the option  --backup-password-from-stdin , is supported together with  -- execute "START BACKUP [ options ]"  for starting a cluster backup from the system shell. •For  ndb_restore  and  ndb_print_backup_file , the  --backup-password-from-stdin option enables input of the password in a secure fashion, similar to how it is done by the  mysql  client’ --password  option. For  ndb_restore , use the option together with the  --decrypt  option; for ndb_print_backup_file , use the option in place of the  -P  option.