Search Results
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-encrypted-innodb-options.html
The same password supplied during backup must be supplied again during a copy-back-and-apply-log, apply-log, or an apply-incremental-backup operation for the backup, or mysqlbackup will error out when it encounters encrypted InnoDB tables or ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-incremental-options.html
If this value has been set explicitly but page tracking cannot be used, the backup fails with an error. For an overview of incremental backups and usage examples for these options, see Section 4.3.3, “Making a Differential or Incremental ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-progress-report-options.html
The argument of the option controls the destination to which the progress indicators are sent: stderr: Progress indicators are sent to the standard error stream. There are two options for controlling the progress reporting function of mysqlbackup: ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/connection-options.html
Unknown connection parameters cause mysqlbackup to throw an error and quit. When mysqlbackup creates a backup, it sends SQL commands to a MySQL server using a database server connection. The way to create a connection is similar to what is ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-faq.html
Otherwise, the error message makes it look as if the option name is not recognized. This section lists some common questions about MySQL Enterprise Backup, with answers and pointers to further information. A.2: What is the big ibdata file that is ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.usage.html
--error-code The exit code for which the print-message command prints the corresponding exit message. The following sections describe the command-line options for the different modes of operation of mysqlbackup. Use the hyperlinks at the option ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-autotune.html
The cluster must be in the created or fully operational status for this command to work, or an error will result. autotune [--dryrun] [--sequential-restart] [--writeload=writeload] template cluster_name writeload: {low|medium|high} template: ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-create-cluster.html
Caution While it is possible to import into a cluster that was created without this option, it is not advisable, since the cluster is not protected against accidentally performing any of the operations listed previously, which may result in ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-delete-cluster.html
delete cluster [--removedirs] cluster_name This command deletes the cluster named cluster_name, removing it from the list of clusters managed by MySQL Cluster Manager. delete cluster does not remove any MySQL NDB Cluster binaries from hosts.
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-delete-package.html
If you attempt to use the unregistered package in a create cluster command, the command fails, as shown here: mcm> create cluster --package=mypackage > --processhosts=ndb_mgmd@tonfisk,ndbd@grindval,ndbd@flundra,mysqld@tonfisk mycluster; ERROR 4001 ... delete package [{--hosts=|-h }host_list] package_name host_list: host[,host[,...]] This command is used to unregister a ...