Search Results
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-partial-options.html
If the database specified with new_db_name does not exist on the target server, it will be created during the restore process. The restore fails if old_table_name does not match with the table specified using the --include-tables or --exclude-tables ... To select specific data to be backed up or restored, use the partial backup and restore options described in this ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-special-options.html
These options are for backing up database servers that play specific roles in replication, or contain certain kinds of data that require special care in backing up. --replica-info When backing up a replica server, this option captures information ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/index.html
Abstract This is the user manual for MySQL Enterprise Backup, a commercially licensed backup utility for MySQL databases. It explains the different kinds of backup and restore that can be performed with MySQL Enterprise Backup, and describes the ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-files-backed-up-summary.html
If any external tablespace exists on a backed up server, the tracker file is going to be found in the datadir folder inside the backup. The following table shows the different types of files that are included in a single-file backup image or a ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/restore.partial.html
For non-TTS backups: The tables being restored must already exist on the destination server, in the same table definition. For TTS backups: The tables being restored must not already exist on the destination server. Table-Level Recovery (TLR) ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/standard-options.html
The general options are options of a general nature, or options that are not classified under any other specific option group: The following general options also exist for the mysql command. --force: (Deprecated and ignored ): By default, some of ...Full descriptions for these options can be found in the MySQL reference manual, for example in Server Option, System Variable, and Status Variable ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-create-certs.html
The command fails if any of the following conditions is true: A CA already exists when creating the CA. create certs [--ca|--keys] [--added] cluster_name The command creates all certificate authorities (CAs), keys, and certificate files needed for ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-delete-cluster.html
For MySQL Cluster Manager 8.4.4 and later: The delete cluster command also fails if a backup of the cluster exists somewhere under /path-to-mcm-data-repository/clusters/clustername (the default arrangement). delete cluster [--removedirs] ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-import-cluster.html
The cluster named in the command must already exist in MySQL Cluster Manager. When this option is used, only the checks required for importation are performed against the existing cluster. import cluster [--dryrun|-y] [--remove-angel] cluster_name ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-install-upgrading.html
For illustrative purposes, we assume an upgrade from an existing installation of MySQL Cluster Manager 8.0.44 to a new installation of MySQL Cluster Manager 8.4.6. Although the MySQL NDB Cluster software typically comes bundled with the MySQL ...