Percona XtraBackup 8.0 Documentation, Release 8.0.4
Note: In case of multiple server instances, the correct connection parameters (port, socket, host) must be specified in
order for xtrabackup to talk to the correct server.
Permissions and Privileges Needed
Once connected to the server, in order to perform a backup you will need READ, WRITE and EXECUTE permissions
at a filesystem level in the server’s datadir.
The database user needs the following privileges on the tables/databases to be backed up:
• RELOAD and LOCK TABLES (unless the --no-lock option is specified) in order to run FLUSH TABLES
WITH READ LOCK and FLUSH ENGINE LOGS prior to start copying the files, and requires this privilege
when Backup Locks are used
• BACKUP_ADMIN privilege is needed to query the performance_schema.log_status table, and run LOCK
INSTANCE FOR BACKUP, LOCK BINLOG FOR BACKUP, or LOCK TABLES FOR BACKUP.
• REPLICATION CLIENT in order to obtain the binary log position,
• CREATE TABLESPACE in order to import tables (see Restoring Individual Tables),
• PROCESS in order to run SHOW ENGINE INNODB STATUS (which is mandatory), and optionally to see all
threads which are running on the server (see Handling FLUSH TABLES WITH READ LOCK),
• SUPER in order to start/stop the slave threads in a replication environment, use XtraDB Changed Page Tracking
for Incremental Backups and for handling FLUSH TABLES WITH READ LOCK,
• CREATE privilege in order to create the PERCONA_SCHEMA.xtrabackup_history database and table,
• INSERT privilege in order to add history records to the PERCONA_SCHEMA.xtrabackup_history table,
• SELECT privilege in order to use --incremental-history-name or
--incremental-history-uuid in order for the feature to look up the innodb_to_lsn values
in the PERCONA_SCHEMA.xtrabackup_history table.
The explanation of when these are used can be found in How Percona XtraBackup Works.
An SQL example of creating a database user with the minimum privileges required to full backups would be:
mysql> CREATE USER 'bkpuser'@'localhost' IDENTIFIED BY 's3cret';
mysql> GRANT RELOAD, LOCK TABLES, PROCESS, REPLICATION CLIENT ON
*
.
*
TO
'bkpuser'@'localhost';
mysql> FLUSH PRIVILEGES;
4.2. Permissions and Privileges Needed 17
我的内容管理
展开
