老王笔记

XtraBackup

XtraBackup是什么？

XtraBackup是Percona提供的一款备份工具，支持InnoDB,MyISAM, XtraDB(Percona研发的引擎)，是一款开源免费的Mysql备份工具；支持全量备份，增量备份，增量备份只有Innodeb支持，MyISAM不支持，因为Innodb有LSN(Log Sequence Number)，xtrabackup依靠检测全量的LSN号，只备份比其大的，就是增量备份；

Xtrabackup有如下特点:

备份集高效，完整，可用
备份任务执行过程中不会阻塞事物
节省空间，降低宽带
备份集自动验证机制
恢复速度块

安装XtraBackup：

创建repo文件，内容如下：

[root@localhost yum.repos.d]# pwd
/etc/yum.repos.d
[root@localhost yum.repos.d]# 
[root@localhost yum.repos.d]# cat Percona.repo 
[percona]
name = CentOS $releasever - Percona
baseurl=http://repo.percona.com/centos/$releasever/os/$basearch/
enabled = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-percona
gpgcheck = 1
[root@localhost yum.repos.d]#

下载并保存key：

#wget http://www.percona.com/redir/downloads/percona-release/RPM-GPG-KEY-percona

#cp RPM-GPG-KEY-percona /etc/pki/rpm-gpg/RPM-GPG-KEY-percona

yum安装：

#yum -y install percona-xtrabackup

#yum -y install percona-toolkit

Xtrabackup使用：

xtrabacup 仅用于备份Innodb

--defaults-file=/etc/my.cnf : 指定my.cnf文件，而且必须要放在第一个位置；主要为了获取datadir位置

--backup | --prepare 两者选其一，前者为了备份，后者为了恢复 --target-dir 制定目标路径，即备份文件存储的路径

--incremental-dir 恢复的时候，制定恢复增量备份路径

innobackupex的使用

innobackupex可以备份Myisam，备份Innodb的时候会自动调用xtrabackup，所以我们直接用innobackupex的比较多，两种引擎都能用

--incremental 进行增量备份，工具针对Innodb有增量，针对MyISAM自动进行全量；

--incremental-basedir 指定一个全量备份作为基数，在此基础上进行增量备份

--apply-log 用于准备恢复

--defaults-file 指定配置文件

--user 指定用户名，要有足够的权限，我这里直接all privileges了

--password 密码

--port 端口

--socket socket文件路径

--slave-info 备份完毕xtrabackup_info中会含有position

--copy-back 待数据准备好后，将备份文件copy至数据目录下

--redo-only 准备恢复的时候，如果后续还有增量，则必须跟上该参数；如果该备份机已经是最后一个，则不用加

--incremental-dir 恢复的时候，制定恢复增量备份路径

--stream=tar | gzip 采用流模式，将所有的备份文件流入到标准输出的格式，支持tar和xbstream(xtrabackup专用格式)

--slave-info 输出信息中含有CHANGE MASTER TO...

异地备份

innobackupex --user root --password "rootpassword" --slave-info --defaults-file=/etc/my.cnf --stream=tar ./ | ssh root@ipaddress "cat - > /data/mysql/dbbak/backup.tar"

全量备份：

innobackupex --defaults-file=/etc/my.cnf --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info /export/data/dbbak/

[root@localhost dbbak]# ls
2018-09-02_22-34-32
[root@localhost dbbak]# ls 2018-09-02_22-34-32/
apple  backup-my.cnf  ibdata1  llj  mysql  performance_schema  test  xtrabackup_binlog_info  xtrabackup_checkpoints  xtrabackup_info  xtrabackup_logfile
[root@localhost dbbak]# ls 2018-09-02_22-34-32/xtrabackup_info 
2018-09-02_22-34-32/xtrabackup_info
[root@localhost dbbak]# cat 2018-09-02_22-34-32/xtrabackup_info
uuid = 4fefba18-aebd-11e8-8b66-000c29081196
name = 
tool_name = innobackupex
tool_command = --defaults-file=/etc/my.cnf --user=llj --password=... --port=3306 --socket=/tmp/mysql.sock --slave-info /export/data/dbbak/
tool_version = 2.3.10
ibbackup_version = 2.3.10
server_version = 5.6.36-log
start_time = 2018-09-02 22:34:32
end_time = 2018-09-02 22:34:34
lock_time = 0
binlog_pos = filename 'mysql-bin.000001', position '209'
innodb_from_lsn = 0
innodb_to_lsn = 1666702
partial = N
incremental = N
format = file
compact = N
compressed = N
encrypted = N
[root@localhost dbbak]#

备份指定的库：

innobackupex --defaults-file=/etc/my.cnf --databases=apple --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info /export/data/dbbak/

--databases=库名指定要备份的库，也支持表粒度备份，库名.表名即可，多个库中间空格隔开

"databasename1[.table_name1] databasename2[.table_name2] . . ."

[root@localhost dbbak]# innobackupex  --defaults-file=/etc/my.cnf  --databases=apple --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info /export/data/dbbak/
180902 22:31:42 innobackupex: Starting the backup operation

IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

180902 22:31:42  version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/tmp/mysql.sock' as 'llj'  (using password: YES).
180902 22:31:42  version_check Connected to MySQL server
180902 22:31:42  version_check Executing a version check against the server...
180902 22:31:42  version_check Done.
180902 22:31:42 Connecting to MySQL server host: localhost, user: llj, password: set, port: 3306, socket: /tmp/mysql.sock
Using server version 5.6.36-log
innobackupex version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /export/data/mysql
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 2
xtrabackup:   innodb_log_file_size = 50331648
180902 22:31:42 >> log scanned up to (1666702)
xtrabackup: Generating a list of tablespaces
Skipping db: ./mysql
Skipping db: ./test
Skipping db: ./performance_schema
Skipping db: ./llj
180902 22:31:42 [01] Copying ./ibdata1 to /export/data/dbbak/2018-09-02_22-31-42/ibdata1
180902 22:31:43 [01]        ...done
180902 22:31:43 [01] Copying ./apple/a.ibd to /export/data/dbbak/2018-09-02_22-31-42/apple/a.ibd
180902 22:31:43 [01]        ...done
180902 22:31:43 [01] Copying ./apple/b.ibd to /export/data/dbbak/2018-09-02_22-31-42/apple/b.ibd
180902 22:31:43 [01]        ...done
180902 22:31:43 >> log scanned up to (1666702)
180902 22:31:43 Executing FLUSH NO_WRITE_TO_BINLOG TABLES...
180902 22:31:43 Executing FLUSH TABLES WITH READ LOCK...
180902 22:31:43 Starting to backup non-InnoDB tables and files
Skipping db: ./mysql
Skipping db: ./test
Skipping db: ./performance_schema
180902 22:31:43 [01] Copying ./apple/db.opt to /export/data/dbbak/2018-09-02_22-31-42/apple/db.opt
180902 22:31:43 [01]        ...done
180902 22:31:43 [01] Copying ./apple/a.frm to /export/data/dbbak/2018-09-02_22-31-42/apple/a.frm
180902 22:31:43 [01]        ...done
180902 22:31:43 [01] Copying ./apple/b.frm to /export/data/dbbak/2018-09-02_22-31-42/apple/b.frm
180902 22:31:43 [01]        ...done
Skipping db: ./llj
180902 22:31:43 Finished backing up non-InnoDB tables and files
Failed to get master binlog coordinates from SHOW SLAVE STATUS
This means that the server is not a replication slave. Ignoring the --slave-info option
180902 22:31:43 [00] Writing xtrabackup_binlog_info
180902 22:31:43 [00]        ...done
180902 22:31:43 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
xtrabackup: The latest check point (for incremental): '1666702'
xtrabackup: Stopping log copying thread.
.180902 22:31:43 >> log scanned up to (1666702)

180902 22:31:44 Executing UNLOCK TABLES
180902 22:31:44 All tables unlocked
180902 22:31:44 Backup created in directory '/export/data/dbbak/2018-09-02_22-31-42/'
MySQL binlog position: filename 'mysql-bin.000001', position '209'
180902 22:31:44 [00] Writing backup-my.cnf
180902 22:31:44 [00]        ...done
180902 22:31:44 [00] Writing xtrabackup_info
180902 22:31:44 [00]        ...done
xtrabackup: Transaction log of lsn (1666702) to (1666702) was copied.
180902 22:31:44 completed OK!

可以看到只有apple一个库文件夹

[root@localhost dbbak]# ls
2018-09-02_22-31-42
[root@localhost dbbak]# cd 2018-09-02_22-31-42/
[root@localhost 2018-09-02_22-31-42]# ls
apple  backup-my.cnf  ibdata1  xtrabackup_binlog_info  xtrabackup_checkpoints  xtrabackup_info  xtrabackup_logfile
[root@localhost 2018-09-02_22-31-42]#

实现远程备份：

方法一：安装nc, pigz（并发的gzip）

先在远端机器上操作，执行后，系统会一直监听；

nc -l 1234 | gunzip | tar ixvf - &> xtrabackup.log
然后在本地mysql上执行备份命令：

（这种方法不错是不错，就是无法挂到后台执行，nohup就报错，不明原因；数据量大要执行好几个小时的时候，网络一断的话就呵呵了）

[root@bogon dbbak]# nc -l 1234 | gunzip | tar ixvf - &> xtrabackup.log
[root@bogon dbbak]# 
[root@bogon dbbak]# ls
1.sh  apple  backup-my.cnf  ibdata1  xtrabackup_binlog_info  xtrabackup_checkpoints  xtrabackup_info  xtrabackup.log  xtrabackup_logfile
[root@bogon dbbak]#

innobackupex --defaults-file=/etc/my.cnf --databases=apple --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info --stream=tar ./ | pigz | nc 192.168.199.134 1234

[root@localhost dbbak]# 
[root@localhost dbbak]# innobackupex  --defaults-file=/etc/my.cnf  --databases=apple --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info --stream=tar ./ | pigz | nc 192.168.199.134 1234
180902 22:43:10 innobackupex: Starting the backup operation

IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

180902 22:43:10  version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/tmp/mysql.sock' as 'llj'  (using password: YES).
180902 22:43:10  version_check Connected to MySQL server
180902 22:43:10  version_check Executing a version check against the server...
180902 22:43:10  version_check Done.
180902 22:43:10 Connecting to MySQL server host: localhost, user: llj, password: set, port: 3306, socket: /tmp/mysql.sock
Using server version 5.6.36-log
innobackupex version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /export/data/mysql
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 2
xtrabackup:   innodb_log_file_size = 50331648
180902 22:43:11 >> log scanned up to (1666702)
xtrabackup: Generating a list of tablespaces
Skipping db: ./mysql
Skipping db: ./test
Skipping db: ./performance_schema
Skipping db: ./llj
180902 22:43:11 [01] Streaming ./ibdata1
180902 22:43:11 [01]        ...done
180902 22:43:11 [01] Streaming ./apple/a.ibd
180902 22:43:11 [01]        ...done
180902 22:43:11 [01] Streaming ./apple/b.ibd
180902 22:43:11 [01]        ...done
180902 22:43:12 >> log scanned up to (1666702)
180902 22:43:12 Executing FLUSH NO_WRITE_TO_BINLOG TABLES...
180902 22:43:12 Executing FLUSH TABLES WITH READ LOCK...
180902 22:43:12 Starting to backup non-InnoDB tables and files
Skipping db: ./mysql
Skipping db: ./test
Skipping db: ./performance_schema
180902 22:43:12 [01] Streaming ./apple/db.opt to 
180902 22:43:12 [01]        ...done
180902 22:43:12 [01] Streaming ./apple/a.frm to 
180902 22:43:12 [01]        ...done
180902 22:43:12 [01] Streaming ./apple/b.frm to 
180902 22:43:12 [01]        ...done
Skipping db: ./llj
180902 22:43:12 Finished backing up non-InnoDB tables and files
Failed to get master binlog coordinates from SHOW SLAVE STATUS
This means that the server is not a replication slave. Ignoring the --slave-info option
180902 22:43:12 [00] Streaming xtrabackup_binlog_info
180902 22:43:12 [00]        ...done
180902 22:43:12 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
xtrabackup: The latest check point (for incremental): '1666702'
xtrabackup: Stopping log copying thread.
.180902 22:43:12 >> log scanned up to (1666702)

180902 22:43:12 Executing UNLOCK TABLES
180902 22:43:12 All tables unlocked
180902 22:43:12 Backup created in directory '/export/data/dbbak/'
MySQL binlog position: filename 'mysql-bin.000001', position '209'
180902 22:43:12 [00] Streaming backup-my.cnf
180902 22:43:12 [00]        ...done
180902 22:43:12 [00] Streaming xtrabackup_info
180902 22:43:12 [00]        ...done
xtrabackup: Transaction log of lsn (1666702) to (1666702) was copied.
180902 22:43:12 completed OK!
[root@localhost dbbak]#

方法二：异地备份也可以设置免密登陆，然后通过ssh的方式复制过去

ssh-keygen
ssh-copy-id -i [email protected]

innobackupex --defaults-file=/etc/my.cnf --databases=apple --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info /export/data/dbbak/ --stream=tar | gzip | ssh [email protected] "cat -> /export/data/dbbak/bak.tar"

挂到后台备份：如果要保存到远端主机，用setsid比较好，我用nohup的tar文件解压的时候会报错，1T多，复制了好几个小时啊，解压就报错，都是泪；

setsid innobackupex --defaults-file=/etc/my.cnf --user=llj --password=llj --port=3306 --socket=/tmp/mysql.sock --slave-info /export/data/dbbak/ --stream=tar | gzip | ssh [email protected] "cat -> /export/data/dbbak/bak.tar" &

然后是准备恢复：

[[email protected] dbbak]#innobackupex --defaults-file=/etc/my.cnf --apply-log /export/data/dbbak/2018-08-25_01-27-26/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013.  All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

IMPORTANT: Please check that the apply-log run completes successfully.
           At the end of a successful apply-log run innobackupex
           prints "completed OK!".



180825 01:29:17  innobackupex: Starting ibbackup with command: xtrabackup_56  --defaults-file="/etc/my.cnf"  --defaults-group="mysqld" --prepare --target-dir=/export/data/dbbak/2018-08-25_01-27-26 --tmpdir=/export/data/mysqltmp

xtrabackup_56 version 2.1.9 for MySQL server 5.6.17 Linux (x86_64) (revision id: 746)
xtrabackup: cd to /export/data/dbbak/2018-08-25_01-27-26
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1610164)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:100M;ibdata2:100M:autoextend:max:200M
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:100M;ibdata2:100M:autoextend:max:200M
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
...................
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1614888
180825 01:29:25  innobackupex: completed OK!

最后是执行恢复

执行前，将原数据文件删除或者备份；删除ib_logfile0 ib_logfile1 文件，删除 ibdata1 ibdata2文件

然后执行恢复

innobackupex --defaults-file=/etc/my.cnf --copy-back /export/data/dbbak/2018-08-25_01-27-26/

[[email protected] mysql]#innobackupex --defaults-file=/etc/my.cnf --copy-back /export/data/dbbak/2018-08-25_01-27-26/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013.  All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

IMPORTANT: Please check that the copy-back run completes successfully.
           At the end of a successful copy-back run innobackupex
           prints "completed OK!".

innobackupex: Starting to copy files in '/export/data/dbbak/2018-08-25_01-27-26'
innobackupex: back to original data directory '/export/data/mysql'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/xtrabackup_binlog_pos_innodb' to '/export/data/mysql/xtrabackup_binlog_pos_innodb'
innobackupex: Creating directory '/export/data/mysql/test'
innobackupex: Creating directory '/export/data/mysql/performance_schema'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_summary_by_thread_by_event_name.frm' to '/export/data/mysql/performance_schema/events_waits_summary_by_thread_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/threads.frm' to '/export/data/mysql/performance_schema/threads.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_current.frm' to '/export/data/mysql/performance_schema/events_waits_current.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_summary_by_account_by_event_name.frm' to '/export/data/mysql/performance_schema/events_statements_summary_by_account_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/table_io_waits_summary_by_index_usage.frm' to '/export/data/mysql/performance_schema/table_io_waits_summary_by_index_usage.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/table_lock_waits_summary_by_table.frm' to '/export/data/mysql/performance_schema/table_lock_waits_summary_by_table.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_summary_by_user_by_event_name.frm' to '/export/data/mysql/performance_schema/events_statements_summary_by_user_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_current.frm' to '/export/data/mysql/performance_schema/events_statements_current.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/rwlock_instances.frm' to '/export/data/mysql/performance_schema/rwlock_instances.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_summary_global_by_event_name.frm' to '/export/data/mysql/performance_schema/events_stages_summary_global_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/socket_summary_by_event_name.frm' to '/export/data/mysql/performance_schema/socket_summary_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/db.opt' to '/export/data/mysql/performance_schema/db.opt'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_summary_by_host_by_event_name.frm' to '/export/data/mysql/performance_schema/events_stages_summary_by_host_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_summary_by_account_by_event_name.frm' to '/export/data/mysql/performance_schema/events_waits_summary_by_account_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_summary_by_user_by_event_name.frm' to '/export/data/mysql/performance_schema/events_waits_summary_by_user_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/setup_objects.frm' to '/export/data/mysql/performance_schema/setup_objects.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_history_long.frm' to '/export/data/mysql/performance_schema/events_statements_history_long.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_summary_by_host_by_event_name.frm' to '/export/data/mysql/performance_schema/events_waits_summary_by_host_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/file_summary_by_instance.frm' to '/export/data/mysql/performance_schema/file_summary_by_instance.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_history.frm' to '/export/data/mysql/performance_schema/events_statements_history.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/objects_summary_global_by_type.frm' to '/export/data/mysql/performance_schema/objects_summary_global_by_type.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_summary_by_thread_by_event_name.frm' to '/export/data/mysql/performance_schema/events_stages_summary_by_thread_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_summary_by_host_by_event_name.frm' to '/export/data/mysql/performance_schema/events_statements_summary_by_host_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/hosts.frm' to '/export/data/mysql/performance_schema/hosts.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_history.frm' to '/export/data/mysql/performance_schema/events_waits_history.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_summary_by_thread_by_event_name.frm' to '/export/data/mysql/performance_schema/events_statements_summary_by_thread_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/session_connect_attrs.frm' to '/export/data/mysql/performance_schema/session_connect_attrs.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/file_summary_by_event_name.frm' to '/export/data/mysql/performance_schema/file_summary_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/cond_instances.frm' to '/export/data/mysql/performance_schema/cond_instances.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/session_account_connect_attrs.frm' to '/export/data/mysql/performance_schema/session_account_connect_attrs.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/setup_instruments.frm' to '/export/data/mysql/performance_schema/setup_instruments.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_summary_by_digest.frm' to '/export/data/mysql/performance_schema/events_statements_summary_by_digest.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_current.frm' to '/export/data/mysql/performance_schema/events_stages_current.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/socket_instances.frm' to '/export/data/mysql/performance_schema/socket_instances.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_summary_by_user_by_event_name.frm' to '/export/data/mysql/performance_schema/events_stages_summary_by_user_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_statements_summary_global_by_event_name.frm' to '/export/data/mysql/performance_schema/events_statements_summary_global_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/setup_actors.frm' to '/export/data/mysql/performance_schema/setup_actors.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/users.frm' to '/export/data/mysql/performance_schema/users.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/setup_timers.frm' to '/export/data/mysql/performance_schema/setup_timers.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/socket_summary_by_instance.frm' to '/export/data/mysql/performance_schema/socket_summary_by_instance.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/performance_timers.frm' to '/export/data/mysql/performance_schema/performance_timers.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_summary_by_instance.frm' to '/export/data/mysql/performance_schema/events_waits_summary_by_instance.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/setup_consumers.frm' to '/export/data/mysql/performance_schema/setup_consumers.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/host_cache.frm' to '/export/data/mysql/performance_schema/host_cache.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_history_long.frm' to '/export/data/mysql/performance_schema/events_waits_history_long.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_history.frm' to '/export/data/mysql/performance_schema/events_stages_history.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/mutex_instances.frm' to '/export/data/mysql/performance_schema/mutex_instances.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_summary_by_account_by_event_name.frm' to '/export/data/mysql/performance_schema/events_stages_summary_by_account_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/file_instances.frm' to '/export/data/mysql/performance_schema/file_instances.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/accounts.frm' to '/export/data/mysql/performance_schema/accounts.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/table_io_waits_summary_by_table.frm' to '/export/data/mysql/performance_schema/table_io_waits_summary_by_table.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_waits_summary_global_by_event_name.frm' to '/export/data/mysql/performance_schema/events_waits_summary_global_by_event_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/performance_schema/events_stages_history_long.frm' to '/export/data/mysql/performance_schema/events_stages_history_long.frm'
innobackupex: Creating directory '/export/data/mysql/mysql'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/plugin.frm' to '/export/data/mysql/mysql/plugin.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/event.MYI' to '/export/data/mysql/mysql/event.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_relation.MYD' to '/export/data/mysql/mysql/help_relation.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slow_log.CSV' to '/export/data/mysql/mysql/slow_log.CSV'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_name.MYI' to '/export/data/mysql/mysql/time_zone_name.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_category.frm' to '/export/data/mysql/mysql/help_category.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/procs_priv.frm' to '/export/data/mysql/mysql/procs_priv.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slow_log.frm' to '/export/data/mysql/mysql/slow_log.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_name.frm' to '/export/data/mysql/mysql/time_zone_name.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/event.frm' to '/export/data/mysql/mysql/event.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_keyword.MYD' to '/export/data/mysql/mysql/help_keyword.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/innodb_index_stats.ibd' to '/export/data/mysql/mysql/innodb_index_stats.ibd'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_keyword.frm' to '/export/data/mysql/mysql/help_keyword.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/user.frm' to '/export/data/mysql/mysql/user.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_transition_type.MYD' to '/export/data/mysql/mysql/time_zone_transition_type.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/innodb_index_stats.frm' to '/export/data/mysql/mysql/innodb_index_stats.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/func.MYD' to '/export/data/mysql/mysql/func.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/servers.frm' to '/export/data/mysql/mysql/servers.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_transition.MYI' to '/export/data/mysql/mysql/time_zone_transition.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone.MYD' to '/export/data/mysql/mysql/time_zone.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_transition.MYD' to '/export/data/mysql/mysql/time_zone_transition.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/proc.MYI' to '/export/data/mysql/mysql/proc.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/procs_priv.MYD' to '/export/data/mysql/mysql/procs_priv.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/ndb_binlog_index.MYI' to '/export/data/mysql/mysql/ndb_binlog_index.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/func.MYI' to '/export/data/mysql/mysql/func.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/tables_priv.MYD' to '/export/data/mysql/mysql/tables_priv.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_transition_type.MYI' to '/export/data/mysql/mysql/time_zone_transition_type.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/columns_priv.frm' to '/export/data/mysql/mysql/columns_priv.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/ndb_binlog_index.frm' to '/export/data/mysql/mysql/ndb_binlog_index.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/proxies_priv.frm' to '/export/data/mysql/mysql/proxies_priv.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_topic.frm' to '/export/data/mysql/mysql/help_topic.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_leap_second.MYI' to '/export/data/mysql/mysql/time_zone_leap_second.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slave_relay_log_info.frm' to '/export/data/mysql/mysql/slave_relay_log_info.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/procs_priv.MYI' to '/export/data/mysql/mysql/procs_priv.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/proc.frm' to '/export/data/mysql/mysql/proc.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slave_master_info.ibd' to '/export/data/mysql/mysql/slave_master_info.ibd'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slave_relay_log_info.ibd' to '/export/data/mysql/mysql/slave_relay_log_info.ibd'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_topic.MYD' to '/export/data/mysql/mysql/help_topic.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slave_worker_info.ibd' to '/export/data/mysql/mysql/slave_worker_info.ibd'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/servers.MYD' to '/export/data/mysql/mysql/servers.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/db.frm' to '/export/data/mysql/mysql/db.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/general_log.frm' to '/export/data/mysql/mysql/general_log.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/tables_priv.MYI' to '/export/data/mysql/mysql/tables_priv.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone.frm' to '/export/data/mysql/mysql/time_zone.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_name.MYD' to '/export/data/mysql/mysql/time_zone_name.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone.MYI' to '/export/data/mysql/mysql/time_zone.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_relation.frm' to '/export/data/mysql/mysql/help_relation.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_transition_type.frm' to '/export/data/mysql/mysql/time_zone_transition_type.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/proc.MYD' to '/export/data/mysql/mysql/proc.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/user.MYD' to '/export/data/mysql/mysql/user.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/plugin.MYD' to '/export/data/mysql/mysql/plugin.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/proxies_priv.MYD' to '/export/data/mysql/mysql/proxies_priv.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slow_log.CSM' to '/export/data/mysql/mysql/slow_log.CSM'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/tables_priv.frm' to '/export/data/mysql/mysql/tables_priv.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_keyword.MYI' to '/export/data/mysql/mysql/help_keyword.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/proxies_priv.MYI' to '/export/data/mysql/mysql/proxies_priv.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/columns_priv.MYD' to '/export/data/mysql/mysql/columns_priv.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/db.MYD' to '/export/data/mysql/mysql/db.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_category.MYI' to '/export/data/mysql/mysql/help_category.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_relation.MYI' to '/export/data/mysql/mysql/help_relation.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/db.MYI' to '/export/data/mysql/mysql/db.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/innodb_table_stats.ibd' to '/export/data/mysql/mysql/innodb_table_stats.ibd'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slave_master_info.frm' to '/export/data/mysql/mysql/slave_master_info.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_category.MYD' to '/export/data/mysql/mysql/help_category.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/event.MYD' to '/export/data/mysql/mysql/event.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/plugin.MYI' to '/export/data/mysql/mysql/plugin.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/func.frm' to '/export/data/mysql/mysql/func.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_leap_second.MYD' to '/export/data/mysql/mysql/time_zone_leap_second.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_transition.frm' to '/export/data/mysql/mysql/time_zone_transition.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/general_log.CSV' to '/export/data/mysql/mysql/general_log.CSV'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/ndb_binlog_index.MYD' to '/export/data/mysql/mysql/ndb_binlog_index.MYD'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/time_zone_leap_second.frm' to '/export/data/mysql/mysql/time_zone_leap_second.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/columns_priv.MYI' to '/export/data/mysql/mysql/columns_priv.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/slave_worker_info.frm' to '/export/data/mysql/mysql/slave_worker_info.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/user.MYI' to '/export/data/mysql/mysql/user.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/innodb_table_stats.frm' to '/export/data/mysql/mysql/innodb_table_stats.frm'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/general_log.CSM' to '/export/data/mysql/mysql/general_log.CSM'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/servers.MYI' to '/export/data/mysql/mysql/servers.MYI'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/mysql/help_topic.MYI' to '/export/data/mysql/mysql/help_topic.MYI'
innobackupex: Creating directory '/export/data/mysql/apple'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/apple/db.opt' to '/export/data/mysql/apple/db.opt'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/apple/a.frm' to '/export/data/mysql/apple/a.frm'

innobackupex: Starting to copy InnoDB system tablespace
innobackupex: in '/export/data/dbbak/2018-08-25_01-27-26'
innobackupex: back to original InnoDB data directory '/export/data/dbdata'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/ibdata1' to '/export/data/dbdata/ibdata1'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/ibdata2' to '/export/data/dbdata/ibdata2'

innobackupex: Starting to copy InnoDB undo tablespaces
innobackupex: in '/export/data/dbbak/2018-08-25_01-27-26'
innobackupex: back to '/export/data/dbdata'

innobackupex: Starting to copy InnoDB log files
innobackupex: in '/export/data/dbbak/2018-08-25_01-27-26'
innobackupex: back to original InnoDB log directory '/export/data/dblog'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/ib_logfile1' to '/export/data/dblog/ib_logfile1'
innobackupex: Copying '/export/data/dbbak/2018-08-25_01-27-26/ib_logfile0' to '/export/data/dblog/ib_logfile0'
innobackupex: Finished copying back files.

180825 01:45:10  innobackupex: completed OK!

工具会将数据文件copy回datadir路径；

最后还有一步，就是修改data权限，属主和属组改为mysql

chown -R mysql.mysql /export/data/

最后开启服务，登陆进去校验建的表都正常

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| apple              |
| mysql              |
| performance_schema |
| test               |
+--------------------+
5 rows in set (0.03 sec)

mysql> show tables from apple;
+-----------------+
| Tables_in_apple |
+-----------------+
| a               |
+-----------------+
1 row in set (0.01 sec)

mysql> select * from apple.a limit 1 \G
*************************** 1. row ***************************
                  Host: localhost
                  User: root

如果想要保险些，可以做下全表的check： mysqlcheck -u root -p123456 -A -c

最后如果需要作为Slave挂在到Master上面怎么办呢？挂在需要知道binlog file 和position才可以；没关系，Xtrabackup都帮我们记着呢；在备份中有xtrabackup_binlog_info文件，里面有记录；然后根据这2个参数挂在即可；

[email protected] 2018-08-25_03-08-46]#ls
apple          ibdata1  ib_logfile0  mysql               test     undo002  undo004            xtrabackup_binlog_info        xtrabackup_checkpoints
backup-my.cnf  ibdata2  ib_logfile1  performance_schema  undo001  undo003  xtrabackup_binary  xtrabackup_binlog_pos_innodb  xtrabackup_logfile
[[email protected] 2018-08-25_03-08-46]#cat  xtrabackup_binlog_info
mysql-bin.000003	3226
[[email protected] 2018-08-25_03-08-46]#

等到主从同步了以后，可以再做checksum，进行一致性校验就更完美了；

你可能感兴趣的:(mysql)

mysql禁用远程登录 igotyback mysql
去mysql库中的user表里，将host都改成localhost之后刷新权限FLUSHPRIVILEGES;
MYSQL面试系列-04 king01299 面试 mysql 面试
MYSQL面试系列-0417.关于redolog和binlog的刷盘机制、redolog、undolog作用、GTID是做什么的？innodb_flush_log_at_trx_commit及sync_binlog参数意义双117.1innodb_flush_log_at_trx_commit该变量定义了InnoDB在每次事务提交时，如何处理未刷入（flush）的重做日志信息（redolog）。它
关于Mysql 中 Row size too large (＞ 8126) 错误的解决和理解秋刀prince mysql mysql 数据库
提示：啰嗦一嘴，数据库的任何操作和验证前，一定要记得先备份！！！不会有错；文章目录问题发现一、问题导致的可能原因1、页大小2、行格式2.1compact格式2.2Redundant格式2.3Dynamic格式2.4Compressed格式3、BLOB和TEXT列二、解决办法1、修改页大小（不推荐）2、修改行格式3、修改数据类型为BLOB和TEXT列4、其他优化方式（可以参考使用）4.1合理设置数据
MongoDB知识概括 GeorgeLin98 持久层 mongodb
MongoDB知识概括MongoDB相关概念单机部署基本常用命令索引-IndexSpirngDataMongoDB集成副本集分片集群安全认证MongoDB相关概念业务应用场景：传统的关系型数据库（如MySQL），在数据操作的“三高”需求以及应对Web2.0的网站需求面前，显得力不从心。解释：“三高”需求：①Highperformance-对数据库高并发读写的需求。②HugeStorage-对海量数
入门MySQL——查询语法练习 K_un
前言：前面几篇文章为大家介绍了DML以及DDL语句的使用方法，本篇文章将主要讲述常用的查询语法。其实MySQL官网给出了多个示例数据库供大家实用查询，下面我们以最常用的员工示例数据库为准，详细介绍各自常用的查询语法。1.员工示例数据库导入官方文档员工示例数据库介绍及下载链接：https://dev.mysql.com/doc/employee/en/employees-installation.h
博客网站制作教程 2401_85194651 java maven
首先就是技术框架：后端：Java+SpringBoot数据库：MySQL前端：Vue.js数据库连接：JPA(JavaPersistenceAPI)1.项目结构blog-app/├──backend/│├──src/main/java/com/example/blogapp/││├──BlogApplication.java││├──config/│││└──DatabaseConfig.java
ubuntu安装wordpress lissettecarlr
1安装nginx网上安装方式很多，这就就直接用apt-get了apt-getinstallnginx不用启动啥，然后直接在浏览器里面输入IP:80就能看到nginx的主页了。如果修改了一些配置可以使用下列命令重启一下systemctlrestartnginx.service2安装mysql输入安装前也可以更新一下软件源，在安装过程中将会让你输入数据库的密码。sudoapt-getinstallmy
计算机毕业设计PHP仓储综合管理系统（源码+程序+VUE+lw+部署） java毕设程序源码王哥 php 课程设计 vue.js
该项目含有源码、文档、程序、数据库、配套开发软件、软件安装教程。欢迎交流项目运行环境配置：phpStudy+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue+Express。项目技术：原生PHP++Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是小皮phpstudy最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
You have an error in your SQL syntax； check the manual that corresponds to your MySQL server version 努力的菜鸟~ sql 数据库
YouhaveanerrorinyourSQLsyntax;checkthemanualthatcorrespondstoyourMySQLserverversionfortherightsyntaxtousenear‘IDENTIFIEDBY‘123456’WITHGRANTOPTION’atline1在mysql5.7之前GRANTALLPRIVILEGESON*.*TO'root'@'%'I
mysql学习教程，从入门到精通，TOP 和MySQL LIMIT 子句（15）知识分享小能手大数据数据库 MySQL mysql 学习 oracle 数据库开发语言 adb 大数据
1、TOP和MySQLLIMIT子句内容在SQL中，不同的数据库系统对于限制查询结果的数量有不同的实现方式。TOP关键字主要用于SQLServer和Access数据库中，而LIMIT子句则主要用于MySQL、PostgreSQL（通过LIMIT/OFFSET语法）、SQLite等数据库中。下面将分别详细介绍这两个功能的语法、语句以及案例。1.1、TOP子句（SQLServer和Access）1.1
鲲鹏 ARM 架构麒麟 Lylin v10 安装 Nginx (离线) 焚木灵 arm开发架构 nginx 服务器
最近做一个银行的项目，银行的服务器是鲲鹏ARM架构的服务器，并且是麒麟v10的系统，这里记录一下在无法访问外网安装Nginx的方法。其他文章：鲲鹏ARM架构麒麟Lylinv10安装Mysql8.3(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Node和NVM(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Pm2(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装P
Kubernetes部署MySQL数据持久化沫殇-MS Kubernetes MySQL数据库 kubernetes mysql 容器
一、安装配置NFS服务端1、安装nfs-kernel-server：sudoapt-yinstallnfs-kernel-server2、服务端创建共享目录#列出所有可用块设备的信息lsblk#格式化磁盘sudomkfs-text4/dev/sdb#创建一个目录：sudomkdir-p/data/nfs/mysql#更改目录权限：sudochown-Rnobody:nogroup/data/nfs
MySQL事务隔离级别和MVCC 简书徐小耳
MySQL事务隔离级别和MVCC参考：https://mp.weixin.qq.com/s/Jeg8656gGtkPteYWrG5_Nw1.MVCC只对读已提交和可重复的读有效果，而未提交读和串行则无意义。2.每条记录都会有trx_id(事务修改记录的id）和roll_pointer是一个指针指向旧版本的undo日志链表（row_id不是必必要的，如果有主键存在就不需要了）3.版本链的头结点就是记
CentOS7 安装MySQL5.7.44 不要Null了 java centos mysql
1.下载mysql安装包，我放在百度网盘里(下方链接)链接：https://pan.baidu.com/s/1_Mn1XW_1mWdTV4mhnLG66A提取码：s31n2.首先看看以前是否安装过mysqlrpm-qa|grep-imysql如果已经安装过mysql会提示卸载mysqlrpm-emysql-…3.使用FinallShell或者Xftp进行上传放到/usr/local/mysql，没
非关系型数据库天秤-white nosql
一、为什么要用Nosql1.单机MySQL的时代。一个基本的网站访问量一般不会太大，单个数据库完全足够。那时候更多使用的静态网页html，服务器根本没有太大压力。这时候网站的瓶颈是什么？-数据量如果太大，一个机器放不下。-数据量太大需要建立数据的索引（B+Tree），一个服务器内存放不下。-访问量读写混合，一个服务器承受不了。2.memcached缓存+MySQL+垂直拆分（读写分离）。网站80%
六、全局锁和表锁：给表加个字段怎么有这么多阻碍 nieniemin
数据库锁设计的初衷是处理并发问题。作为多用户共享的资源，当出现并发访问的时候，数据库需要合理地控制资源的访问规则。而锁就是用来实现这些访问规则的重要数据结构。根据加锁的范围，MySQL里面的锁大致可以分成全局锁、表级锁和行锁三类。6.1全局锁全局锁就是对整个数据库实例加锁。MySQL提供了一个加全局读锁的方法，命令是Flushtableswithreadlock(FTWRL)。当你需要让整个库处于
Kubernetes 自定义控制器开发 IT回忆录 Kubenetes kubernetes
目录前言一、CRD二、创建数据库表（Mysql）二、控制器开发1.使用kubernetes的examplecontroller模板2.在controller.go中新增数据表监听方法3.修改tools工具生成资源对象结构体定义这里记录开发k8s控制器的一般方式，controller开发主要使用k8s提供的client-go库进行。前言Controller监听集群内部资源对象的变化，编辑资源对象(增
【K8s】专题十一：Kubernetes 集群证书过期处理方法行者Sun1989 Kubernetes kubernetes 云原生容器
本文内容均来自个人笔记并重新梳理，如有错误欢迎指正！如果对您有帮助，烦请点赞、关注、转发、订阅专栏！专栏订阅入口Linux专栏|Docker专栏|Kubernetes专栏往期精彩文章【Docker】（全网首发）KylinV10下MySQL容器内存占用异常的解决方法【Docker】（全网首发）KylinV10下MySQL容器内存占用异常的解决方法（续）【Docker】MySQL源码构建Docker镜
MySQl篇（SQL - 基本介绍）（持续更新迭代） wclass-zhengge mysql sql 数据库
目录一、简介二、SQL方言（分页查询为例）1.简介2.SQL方言大比拼2.1.Oracle2.1.1.使用ROWNUM实现分页查询2.1.2.使用ROW_NUMBER()实现分页查询2.2.MySQL2.3.PostgreSQL三、语法规范四、注释五、MySQL脚本中的标点符号一、简介1、SQL是结构化查询语言（StructureQueryLanguage），专门用来操作/访问关系型数据库的通用语
跟着黑马学mysql（5）小杜不吃糖 mysql 数据库
17.DQL-聚合函数DQL-聚合函数介绍将一列数据作为一个整体，进行纵向计算。常见聚合函数函数功能count统计数量max最大值min最小值avg平均值sum求和语法SELECT聚合函数(字段列表)FROM表名;注意：所有的null值不参与聚合函数的运算18.DQL-分组查询语法SELECT字段列表FROM表名[WHERE条件]GROUPBY分组字段名[HAVING分组后的过滤条件];where
梧桐数据库（WuTongDB）：数据库技术中都有哪些常见的优化器鲁鲁517 梧桐数据库梧桐数据库
以下是一些常见的数据库优化器：1.CBO（Cost-BasedOptimizer）应用场景：广泛应用于关系型数据库中，如Oracle、PostgreSQL、MySQL等。工作原理：通过计算不同执行计划的代价（如CPU、I/O等资源消耗），选择最低代价的执行计划。代表数据库：Oracle、PostgreSQL、MySQL。特点：CBO使用统计信息（如表大小、索引分布）来评估查询的代价。2.RBO（R
MySQL日志沉着冷静2024 MySQL mysql 数据库
MySQL日志文章目录MySQL日志MySQL三大日志binlog的三种格式redolog和binlog的区别和应用场景为什么崩溃恢复不用binlog而用redolog？redolog如何实现持久化redolog还能做什么？redolog的三种刷盘策略两阶段提交什么是？为什么？两阶段提交过程MySQL三大日志1.undologundolog是InnoDB存储引擎层的日志，实现了事务的原子性，主要用
MySQL锁沉着冷静2024 MySQL mysql 数据库
MySQL锁文章目录MySQL锁MySQL中锁的分类创建索引时会锁表吗线上修改表结构会加什么锁Innodb存储引擎的行级锁有哪些Update语句中，不带where条件，加什么锁？MySQL实现乐观锁MySQL死锁MySQL死锁是怎么发生的？检查死锁如何避免死锁MySQL中锁的分类全局锁：主要用于全库逻辑备份表级锁：表锁、元数据锁、意向锁表锁：通过locktables语句对表进行加锁，它不仅限制其他
Python实现mysql命令行 xu-jssy python mysql adb
一、源码importosimportpymysqldefsql_shell():password=input("EnterPassword:")#访问密码ifpassword.strip()!="yyds":print("Bye")return#清空控制台输出os.system("cls"ifos.name=="nt"else"clear")try:#连接到MySQL数据库conn=pymysql
mysql case 干货 lack倪酱
这是我舍友@某人提供的是为了做酒店时判断每个楼栋有几间空房子的。房间表与数据楼栋表与数据查询楼栋房间总数查询空房间数当时就在想怎么把后一个单列的数据合并到前面那三列的数据里呢？又是百度，又是谷歌，都是什么“unitall”。。表示我要的不是这个。有点难为我小脑瓜，实在是对数据库不了解，只会日常操作。最后是我舍友想出了解决办法直接贴图好了，如果想要了解case是什么，你可以自行查资料。学习查东西也是
计算机毕设Node.js+Vue校园易购二手交易平台（程序+LW+部署） Node程序源码强子 vue.js 课程设计 node.js
项目运行环境配置：Node.js最新版+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue。项目技术：Express框架+Node.js+Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是Nodejs最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
MySQL 源码｜55 - 语法解析(V2)：基础查询语句（query_specification）｜V20240915 长行 MySQL源码 mysql 源码语法解析查询
目录文档：MySQL源码｜源码剖析文档目录源码位置（版本=MySQL8.0.37）：sql/sql_yacc.yy前置文档：MySQL源码｜68-语法解析(V2)：LOCKING子句（锁定读取）｜V20240909MySQL源码｜39-语法解析(V2)：ORDERBY子句｜V20240814｜V20240912（第2版）MySQL源码｜40-语法解析(V2)：GROUPBY子句｜V20240814
老生常谈：MySQL高可用架构我有一头小花驴 mysql 架构数据库
引言“高可用”是互联网一个永恒的话题，先避开MySQL不谈，为了保证各种服务的高可用有几种常用的解决方案。服务冗余：把服务部署多份，当某个节点不可用时，切换到其他节点。服务冗余对于无状态的服务是相对容易的。服务备份：有些服务是无法同时存在多个运行时的，比如说：Nginx的反向代理，一些集群的leader节点。这时可以存在一个备份服务，处于随时待命状态。自动切换：服务冗余之后，当某个节点不可用时，要
mysql 隐秘后门_【技术分享】CVE-2016-5483：利用mysqldump备份可生成后门 Toby Dai mysql 隐秘后门
预估稿费：100RMB投稿方式：发送邮件至linwei#360.cn，或登陆网页版在线投稿前言mysqldump是用来创建MySQL数据库逻辑备份的一个常用工具。它在默认配置下可以生成一个.sql文件，其中包含创建/删除表和插入数据等。在导入转储文件的时候，攻击者可以通过制造恶意表名来实现任意SQL语句查询和shell命令执行的目的。另一个与之相关的漏洞利用场景可以参考。攻击场景攻击者已经能够访问
处理绿盟科技安全评估的系统漏洞自我修炼的小石头数据库运维开发工具
如下图一次扫描,中度风险39个,这个是必须要处理的.其中mysql占了36个,一看这个感觉整个人都不好了.但是最后解决的办法也很简单,就是升级.系统版本Redhat7.31.telnet因为要升级openssh,openssl,为了避免意外,首先要开启telnet服务,并把所有相关的包上传到服务器.1.1确认是否安装了telnet和xinetd（默认是没有安装）rpm-qatelnet*rpm-q
scala的option和some 矮蛋蛋编程 scala
原文地址： http://blog.sina.com.cn/s/blog_68af3f090100qkt8.html 对于学习 Scala 的 Java™ 开发人员来说，对象是一个比较自然、简单的入口点。在本系列前几期文章中，我介绍了 Scala 中一些面向对象的编程方法，这些方法实际上与 Java 编程的区别不是很大。我还向您展示了 Scala 如何重新应用传统的面向对象概念，找到其缺点
NullPointerException Cb123456 android BaseAdapter
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.view.View.getImportantForAccessibility()' on a null object reference 出现以上异常.然后就在baidu上
PHP使用文件和目录天子之骄 php文件和目录读取和写入 php验证文件 php锁定文件
PHP使用文件和目录 1.使用include()包含文件 (1)：使用include()从一个被包含文档返回一个值 (2)：在控制结构中使用include() include_once()函数需要一个包含文件的路径，此外，第一次调用它的情况和include()一样，如果在脚本执行中再次对同一个文件调用，那么这个文件不会再次包含。在php.ini文件中设置
SQL SELECT DISTINCT 语句何必如此 sql
SELECT DISTINCT 语句用于返回唯一不同的值。 SQL SELECT DISTINCT 语句在表中，一个列可能会包含多个重复值，有时您也许希望仅仅列出不同（distinct）的值。 DISTINCT 关键词用于返回唯一不同的值。 SQL SELECT DISTINCT 语法 SELECT DISTINCT column_name,column_name F
java冒泡排序 3213213333332132 java 冒泡排序
package com.algorithm; /** * @Description 冒泡 * @author FuJianyong * 2015-1-22上午09:58:39 */ public class MaoPao { public static void main(String[] args) { int[] mao = {17,50,26,18,9,10
struts2.18 +json,struts2-json-plugin-2.1.8.1.jar配置及问题！ 7454103 DAO spring Ajax json qq
struts2.18 出来有段时间了！（貌似是稳定版）闲时研究下下！貌似 sruts2 搭配 json 做 ajax 很吃香！实践了下下！不当之处请绕过！呵呵网上一大堆 struts2+json 不过大多的json 插件都是 jsonplugin.34.jar strut
struts2 数据标签说明 darkranger jsp bean struts servlet Scheme
数据标签主要用于提供各种数据访问相关的功能，包括显示一个Action里的属性，以及生成国际化输出等功能数据标签主要包括： action ：该标签用于在JSP页面中直接调用一个Action，通过指定executeResult参数，还可将该Action的处理结果包含到本页面来。 bean ：该标签用于创建一个javabean实例。如果指定了id属性，则可以将创建的javabean实例放入Sta
链表.简单的链表节点构建 aijuans 编程技巧
/*编程环境WIN-TC*/ #include "stdio.h" #include "conio.h" #define NODE(name, key_word, help) \ Node name[1]={{NULL, NULL, NULL, key_word, help}} typedef struct node { &nbs
tomcat下jndi的三种配置方式 avords tomcat
jndi(Java Naming and Directory Interface，Java命名和目录接口)是一组在Java应用中访问命名和目录服务的API。命名服务将名称和对象联系起来，使得我们可以用名称访问对象。目录服务是一种命名服务，在这种服务里，对象不但有名称，还有属性。 tomcat配置
关于敏捷的一些想法 houxinyou 敏捷
从网上看到这样一句话：“敏捷开发的最重要目标就是：满足用户多变的需求，说白了就是最大程度的让客户满意。” 感觉表达的不太清楚。感觉容易被人误解的地方主要在“用户多变的需求”上。第一种多变，实际上就是没有从根本上了解了用户的需求。用户的需求实际是稳定的，只是比较多，也比较混乱，用户一般只能了解自己的那一小部分，所以没有用户能清楚的表达出整体需求。而由于各种条件的，用户表达自己那一部分时也有
富养还是穷养，决定孩子的一生 bijian1013 教育人生
是什么决定孩子未来物质能否丰盛？为什么说寒门很难出贵子，三代才能出贵族？真的是父母必须有钱，才能大概率保证孩子未来富有吗？-----作者：@李雪爱与自由事实并非由物质决定，而是由心灵决定。一朋友富有而且修养气质很好，兄弟姐妹也都如此。她的童年时代，物质上大家都很贫乏，但妈妈总是保持生活中的美感，时不时给孩子们带回一些美好小玩意，从来不对孩子传递生活艰辛、金钱来之不易、要懂得珍惜
oracle 日期时间格式转化征客丶 oracle
oracle 系统时间有 SYSDATE 与 SYSTIMESTAMP； SYSDATE：不支持毫秒，取的是系统时间； SYSTIMESTAMP：支持毫秒，日期，时间是给时区转换的，秒和毫秒是取的系统的。日期转字符窜：一、不取毫秒： TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS') 简要说明， YYYY 年 MM 月
【Scala六】分析Spark源代码总结的Scala语法四 bit1129 scala
1. apply语法 FileShuffleBlockManager中定义的类ShuffleFileGroup，定义： private class ShuffleFileGroup(val shuffleId: Int, val fileId: Int, val files: Array[File]) { ... def apply(bucketId
Erlang中有意思的bug bookjovi erlang
代码中常有一些很搞笑的bug，如下面的一行代码被调用两次（Erlang beam） commit f667e4a47b07b07ed035073b94d699ff5fe0ba9b Author: Jovi Zhang <[email protected]> Date: Fri Dec 2 16:19:22 2011 +0100 erts:
移位打印10进制数转16进制-2008-08-18 ljy325 java 基础
/** * Description 移位打印10进制的16进制形式 * Creation Date 15-08-2008 9:00 * @author 卢俊宇 * @version 1.0 * */ public class PrintHex { // 备选字符 static final char di
读《研磨设计模式》-代码笔记-组合模式 bylijinnan java 设计模式
声明：本文只为方便我个人查阅和理解，详细的分析以及源代码请移步原作者的博客http://chjavach.iteye.com/ import java.util.ArrayList; import java.util.List; abstract class Component { public abstract void printStruct(Str
利用cmd命令将.class文件打包成jar chenyu19891124 cmd jar
cmd命令打jar是如下实现：在运行里输入cmd，利用cmd命令进入到本地的工作盘符。(如我的是D盘下的文件有此路径 D:\workspace\prpall\WEB-INF\classes) 现在是想把D:\workspace\prpall\WEB-INF\classes路径下所有的文件打包成prpall.jar。然后继续如下操作： cd D: 回车 cd workspace/prpal
[原创]JWFD v0.96 工作流系统二次开发包 for Eclipse 简要说明 comsci eclipse 设计模式算法工作 swing
JWFD v0.96 工作流系统二次开发包 for Eclipse 简要说明 &nb
SecureCRT右键粘贴的设置 daizj secureCRT 右键粘贴
一般都习惯鼠标右键自动粘贴的功能，对于SecureCRT6.7.5 ，这个功能也已经是默认配置了。老版本的SecureCRT其实也有这个功能，只是不是默认设置，很多人不知道罢了。菜单： Options->Global Options ...->Terminal 右边有个Mouse的选项块。 Copy on Select Paste on Right/Middle
Linux 软链接和硬链接 dongwei_6688 linux
1.Linux链接概念Linux链接分两种，一种被称为硬链接（Hard Link），另一种被称为符号链接（Symbolic Link）。默认情况下，ln命令产生硬链接。【硬连接】硬连接指通过索引节点来进行连接。在Linux的文件系统中，保存在磁盘分区中的文件不管是什么类型都给它分配一个编号，称为索引节点号(Inode Index)。在Linux中，多个文件名指向同一索引节点是存在的。一般这种连
DIV底部自适应 dcj3sjt126com JavaScript
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml&q
Centos6.5使用yum安装mysql——快速上手必备 dcj3sjt126com mysql
第1步、yum安装mysql [root@stonex ~]# yum -y install mysql-server 安装结果： Installed: mysql-server.x86_64 0:5.1.73-3.el6_5 &nb
如何调试JDK源码 frank1234 jdk
相信各位小伙伴们跟我一样，想通过JDK源码来学习Java，比如collections包，java.util.concurrent包。可惜的是sun提供的jdk并不能查看运行中的局部变量，需要重新编译一下rt.jar。下面是编译jdk的具体步骤： 1.把C:\java\jdk1.6.0_26\sr
Maximal Rectangle hcx2013 max
Given a 2D binary matrix filled with 0's and 1's, find the largest rectangle containing all ones and return its area. public class Solution { public int maximalRectangle(char[][] matrix)
Spring MVC测试框架详解——服务端测试 jinnianshilongnian spring mvc test
随着RESTful Web Service的流行，测试对外的Service是否满足期望也变的必要的。从Spring 3.2开始Spring了Spring Web测试框架，如果版本低于3.2，请使用spring-test-mvc项目（合并到spring3.2中了）。 Spring MVC测试框架提供了对服务器端和客户端（基于RestTemplate的客户端）提供了支持。 &nbs
Linux64位操作系统（CentOS6.6）上如何编译hadoop2.4.0 liyong0802 hadoop
一、准备编译软件 1.在官网下载jdk1.7、maven3.2.1、ant1.9.4，解压设置好环境变量就可以用。环境变量设置如下：（1）执行vim /etc/profile （2）在文件尾部加入: export JAVA_HOME=/home/spark/jdk1.7 export MAVEN_HOME=/ho
StatusBar 字体白色 pangyulei status
[[UIApplication sharedApplication] setStatusBarStyle:UIStatusBarStyleLightContent]; /*you'll also need to set UIViewControllerBasedStatusBarAppearance to NO in the plist file if you use this method
如何分析Java虚拟机死锁 sesame java thread oracle 虚拟机 jdbc
英文资料： Thread Dump and Concurrency Locks Thread dumps are very useful for diagnosing synchronization related problems such as deadlocks on object monitors. Ctrl-\ on Solaris/Linux or Ctrl-B
位运算简介及实用技巧（一）：基础篇 tw_wangzhengquan 位运算
http://www.matrix67.com/blog/archives/263 去年年底写的关于位运算的日志是这个Blog里少数大受欢迎的文章之一，很多人都希望我能不断完善那篇文章。后来我看到了不少其它的资料，学习到了更多关于位运算的知识，有了重新整理位运算技巧的想法。从今天起我就开始写这一系列位运算讲解文章，与其说是原来那篇文章的follow-up，不如说是一个r
jsearch的索引文件结构 yangshangchuan 搜索引擎 jsearch 全文检索信息检索 word分词
jsearch是一个高性能的全文检索工具包，基于倒排索引，基于java8，类似于lucene，但更轻量级。 jsearch的索引文件结构定义如下： 1、一个词的索引由=分割的三部分组成：第一部分是词第二部分是这个词在多少