Installation and testing xtrabackup8.0

Installation and testing xtrabackup8.0
xtrabackup 2.4. MySQL 8.0 is no longer supported backup recovery, use the following errors will be reported!
Error: MySQL 8.0 and 8.0 are not Percona Server Supported by Percona xtrabackup 2.4.x Series Please use Percona xtrabackup 8.0.x for Backups and restores..
Mysql8.0
[root @ Enbao ~] # the Clear
[root @ Enbao ~] # CAT / etc / RedHat-Release
the CentOS the Linux Release 7.5.1804 (Core)
mounted xtrabackup-80-Percona
[@ Enbao the root Soft] # yum the install Percona -Y-xtrabackup-80-8.0.7-1.el7.x86_64.rpm
the installed :
Percona-xtrabackup-80.x86_64 0: 8.0.7-1.el7

Complete!
View installed after the results, found to have no innobackupex command
[root @ Enbao Soft] # RPM -ql Percona-xtrabackup-80-8.0.7-1.el7.x86_64
/ usr / bin / xbcloud
/ usr / bin / xbcloud_osenv
/ usr / bin / xbcrypt
/ usr / bin / xbstream
/ usr / bin / xtrabackup
/usr/lib64/xtrabackup/plugin/keyring_file.so
/usr/lib64/xtrabackup/plugin/keyring_vault.so
/ usr / Share / DOC / percona- 80-8.0.7-xtrabackup
/usr/share/doc/percona-xtrabackup-80-8.0.7/LICENSE
/usr/share/man/man1/xbcrypt.1.gz
/ usr / Share / man / man1 / xbstream. 1.gz
/usr/share/man/man1/xtrabackup.1.gz
backup restore back to 3306 and 3306 instances
create test data
root @ Enbao 09:56: [Enbao]> the test the create Database;
Query the OK, 1 Row affected (0.06 sec)

root@enbao 09:57: [enbao]> use test;
Database changed
root@enbao 09:57: [test]> create table t1(id int(10) NOT NULL AUTO_INCREMENT,name varchar(20),primary key(id));
Query OK, 0 rows affected, 1 warning (0.09 sec)
root@enbao 09:59: [test]> insert into t1(name) values('a'),('b'),('c');
Query OK, 3 rows affected (0.09 sec)
Records: 3 Duplicates: 0 Warnings: 0

root@enbao 10:00: [test]> select * from t1;
+----+------+
| id | name |
+----+------+
| 1 | a |
| 2 | b |
| 3 | c |
+----+------+
3 rows in set (0.00 sec)
创建备份目录
[root@enbao data]# mkdir -p /data/backup/
1.xtrabackup --defaults-file=/data/mysql/my3306.cnf -S /data/mysql/mysql3306.sock -uroot -proot123 --backup --no-timestamp --target-dir=/data/backup/db3306_date +%Y%m%d

  1. Examples of the original shutdown, the cold backup of the original data
    [@ Enbao the root Soft] # mysqladmin -uroot--proot123 shutdown
    Music Videos mysql3306 mysql3306_bak
  2. mkdir mysql3306 / {data, logs, tmp} -p
    data recovery
  3. xtrabackup --defaults-file = / data / mysql / my3306.cnf --copy-back --target-dir = / data / backup / db3306_20191027 /
    Change Directory Permissions
  4. chown -R mysql:mysql mysql3306
  5. /usr/local/mysql/bin/mysqld --defaults-file=/data/mysql/my3306.cnf &
    查看error日志是否有错误,登录到数据库验证可用性!
    [root@enbao logs]# grep -i "error" /data/mysql/mysql3306/logs/error.log
    2019-10-27T10:37:35.389830-04:00 1 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_system' Page [page id: space=0, page number=5] log sequence number 29956511 is in the future! Current system log sequence number 29861388.
    2019-10-27T10:37:35.389873-04:00 1 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
    [root@enbao logs]# mysql -S /data/mysql/mysql3306.sock -p
    Enter password:
    Welcome to the MySQL monitor. Commands end with ; or \g.
    Your MySQL connection id is 9
    Server version: 8.0.17 MySQL Community Server - GPL
    root@enbao 11:01: [test]> select * from t1;
    +----+------+
    | id | name |
    +----+------+
    | 1 | a |
    | 2 | b |
    | 3 | c |
    +----+------+
    3 rows in set (0.00 sec)

root@enbao 11:01: [test]> insert into t1(name) values('d'),('e');
Query OK, 2 rows affected (0.04 sec)
Records: 2 Duplicates: 0 Warnings: 0

Guess you like

Origin blog.51cto.com/1146695/2445836