wsql

percona mysql备份与恢复(二) --------增量备份与恢复

author：skate
time:2012/06/27

percona mysql增量备份与恢复

版本：
mysql> select version();
+------------+
| version() |
+------------+
| 5.5.24-log |
+------------+
1 row in set (0.05 sec)

步骤：

1.全备
2.增量备份
3.prepare增量备份
4.restore增量备份

1.做个full备份是必须的
[root@localhost data]# innobackupex --user=root /data/backup/

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

120627 17:49:43 innobackupex: Starting mysql with options: --user='root' --unbuffered --
120627 17:49:43 innobackupex: Connected to database with mysql child process (pid=16053)
120627 17:49:49 innobackupex: Connection to database server closed
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".

innobackupex: Using mysql Ver 14.12 Distrib 5.0.95, for redhat-linux-gnu (i686) using readline 5.1
innobackupex: Using mysql server version Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.

innobackupex: Created backup directory /data/backup/2012-06-27_17-49-49
120627 17:49:49 innobackupex: Starting mysql with options: --user='root' --unbuffered --
120627 17:49:49 innobackupex: Connected to database with mysql child process (pid=16077)
120627 17:49:51 innobackupex: Connection to database server closed

120627 17:49:51 innobackupex: Starting ibbackup with command: xtrabackup_55 --backup --suspend-at-end --target-dir=/data/backup/2012-06-27_17-49-49
innobackupex: Waiting for ibbackup (pid=16084) to suspend
innobackupex: Suspend file '/data/backup/2012-06-27_17-49-49/xtrabackup_suspended'

xtrabackup_55 version 2.0.0 for Percona Server 5.5.16 Linux (i686) (revision id: 417)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /data/mysql/usr/local/mysql/data/
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
120627 17:49:51 InnoDB: Using Linux native AIO
>> log scanned up to (1598476)
[01] Copying ./ibdata1 to /data/backup/2012-06-27_17-49-49/ibdata1
[01] ...done

120627 17:49:53 innobackupex: Continuing after ibbackup has suspended
120627 17:49:53 innobackupex: Starting mysql with options: --user='root' --unbuffered --
120627 17:49:53 innobackupex: Connected to database with mysql child process (pid=16098)
120627 17:49:55 innobackupex: Starting to lock all tables...
>> log scanned up to (1598476)
>> log scanned up to (1598476)
120627 17:50:06 innobackupex: All tables locked and flushed to disk

120627 17:50:06 innobackupex: Starting to backup .frm, .MRG, .MYD, .MYI,
innobackupex: .TRG, .TRN, .ARM, .ARZ, .CSM, .CSV and .opt files in
innobackupex: subdirectories of '/data/mysql/usr/local/mysql/data/'
innobackupex: Backing up files '/data/mysql/usr/local/mysql/data//performance_schema/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (18 files)
innobackupex: Backing up files '/data/mysql/usr/local/mysql/data//mysql/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (72 files)
>> log scanned up to (1598476)
120627 17:50:08 innobackupex: Finished backing up .frm, .MRG, .MYD, .MYI, .TRG, .TRN, .ARM, .ARZ, .CSV, .CSM and .opt files

innobackupex: Resuming ibbackup

xtrabackup: The latest check point (for incremental): '1598476'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1598476)

xtrabackup: Transaction log of lsn (1598476) to (1598476) was copied.
120627 17:50:10 innobackupex: All tables unlocked
120627 17:50:10 innobackupex: Connection to database server closed

innobackupex: Backup created in directory '/data/backup/2012-06-27_17-49-49'
innobackupex: MySQL binlog position: filename 'mysql-bin.000003', position 4580
120627 17:50:10 innobackupex: completed OK!
[root@localhost data]#

看看备份的类型

[root@localhost backup]# more /data/backup/2012-06-27_17-49-49/xtrabackup_checkpoints
backup_type = full-backuped
from_lsn = 0
to_lsn = 1598476
last_lsn = 1598476
[root@localhost backup]#

2.
增量备份1

[root@localhost data]# innobackupex --user=root --incremental /data/backup --incremental-basedir=/data/backup/2012-06-27_17-49-49/

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

120627 17:53:40 innobackupex: Starting mysql with options: --user='root' --unbuffered --
120627 17:53:40 innobackupex: Connected to database with mysql child process (pid=16230)
120627 17:53:46 innobackupex: Connection to database server closed
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".

innobackupex: Created backup directory /data/backup/2012-06-27_17-53-46
120627 17:53:46 innobackupex: Starting mysql with options: --user='root' --unbuffered --
120627 17:53:46 innobackupex: Connected to database with mysql child process (pid=16256)
120627 17:53:48 innobackupex: Connection to database server closed

120627 17:53:48 innobackupex: Starting ibbackup with command: xtrabackup_55 --backup --suspend-at-end --target-dir=/data/backup/2012-06-27_17-53-46 --incremental-basedir='/data/backup/2012-06-27_17-49-49/'
innobackupex: Waiting for ibbackup (pid=16264) to suspend
innobackupex: Suspend file '/data/backup/2012-06-27_17-53-46/xtrabackup_suspended'

xtrabackup_55 version 2.0.0 for Percona Server 5.5.16 Linux (i686) (revision id: 417)
incremental backup from 1598476 is enabled.
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /data/mysql/usr/local/mysql/data/
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
120627 17:53:48 InnoDB: Using Linux native AIO
>> log scanned up to (1598476)
[01] Copying ./ibdata1 to /data/backup/2012-06-27_17-53-46/ibdata1.delta
[01] ...done

120627 17:53:52 innobackupex: Continuing after ibbackup has suspended
120627 17:53:52 innobackupex: Starting mysql with options: --user='root' --unbuffered --
120627 17:53:52 innobackupex: Connected to database with mysql child process (pid=16278)
>> log scanned up to (1598476)
120627 17:53:54 innobackupex: Starting to lock all tables...
>> log scanned up to (1598476)
>> log scanned up to (1598476)
120627 17:54:05 innobackupex: All tables locked and flushed to disk

120627 17:54:05 innobackupex: Starting to backup .frm, .MRG, .MYD, .MYI,
innobackupex: .TRG, .TRN, .ARM, .ARZ, .CSM, .CSV and .opt files in
innobackupex: subdirectories of '/data/mysql/usr/local/mysql/data/'
innobackupex: Backing up files '/data/mysql/usr/local/mysql/data//performance_schema/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (18 files)
innobackupex: Backing up files '/data/mysql/usr/local/mysql/data//mysql/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (72 files)
120627 17:54:06 innobackupex: Finished backing up .frm, .MRG, .MYD, .MYI, .TRG, .TRN, .ARM, .ARZ, .CSV, .CSM and .opt files

innobackupex: Resuming ibbackup

xtrabackup: The latest check point (for incremental): '1598476'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1598476)

xtrabackup: Transaction log of lsn (1598476) to (1598476) was copied.
120627 17:54:08 innobackupex: All tables unlocked
120627 17:54:08 innobackupex: Connection to database server closed

innobackupex: Backup created in directory '/data/backup/2012-06-27_17-53-46'
innobackupex: MySQL binlog position: filename 'mysql-bin.000003', position 5222
120627 17:54:08 innobackupex: completed OK!
[root@localhost data]#

查看此备份类型

[root@localhost backup]# more /data/backup/2012-06-27_17-53-46/xtrabackup_checkpoints
backup_type = incremental
from_lsn = 1598476
to_lsn = 1598476
last_lsn = 1598476
[root@localhost backup]#

增量备份2

[root@localhost data]# innobackupex --user=root --incremental /data/backup --incremental-basedir=/data/backup/2012-06-27_17-53-46/

.....
.....

xtrabackup: Transaction log of lsn (1598476) to (1598476) was copied.
120627 18:13:55 innobackupex: All tables unlocked
120627 18:13:55 innobackupex: Connection to database server closed

innobackupex: Backup created in directory '/data/backup/2012-06-27_18-13-35'
innobackupex: MySQL binlog position: filename 'mysql-bin.000003', position 5411
120627 18:13:55 innobackupex: completed OK!

查看此备份类型
[root@localhost backup]# more /data/backup/2012-06-27_18-13-35/xtrabackup_checkpoints
backup_type = incremental
from_lsn = 1598476
to_lsn = 1598476
last_lsn = 1598476

增量备份3
[root@localhost data]# innobackupex --user=root --incremental /data/backup --incremental-basedir=/data/backup/2012-06-27_18-13-35/

......
......

xtrabackup: Transaction log of lsn (1598476) to (1598476) was copied.
120627 18:30:37 innobackupex: All tables unlocked
120627 18:30:37 innobackupex: Connection to database server closed

innobackupex: Backup created in directory '/data/backup/2012-06-27_18-30-15'
innobackupex: MySQL binlog position: filename 'mysql-bin.000003', position 5600
120627 18:30:37 innobackupex: completed OK!
[root@localhost data]#

查看此备份类型

[root@localhost backup]# more /data/backup/2012-06-27_18-30-15/xtrabackup_checkpoints
backup_type = incremental
from_lsn = 1598476
to_lsn = 1598476
last_lsn = 1598476
[root@localhost backup]#

full备份应用log，提交committed事务

[root@localhost backup]# innobackupex --apply-log --redo-only /data/backup/2012-06-27_17-49-49/

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

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

120627 18:38:09 innobackupex: Starting ibbackup with command: xtrabackup_55 --prepare --target-dir=/data/backup/2012-06-27_17-49-49 --apply-log-only

[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
120627 18:38:10 InnoDB: Starting shutdown...
120627 18:38:10 InnoDB: Shutdown completed; log sequence number 1598476
120627 18:38:10 innobackupex: completed OK!
[root@localhost backup]#

增量备份1应用log，提交committed事务

[root@localhost backup]# innobackupex --apply-log --redo-only /data/backup/2012-06-27_17-49-49/ --incremental-dir=/data/backup/2012-06-27_17-53-46/

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

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

120627 18:39:42 innobackupex: Starting ibbackup with command: xtrabackup_55 --prepare --target-dir=/data/backup/2012-06-27_17-49-49 --apply-log-only --incremental-dir=/data/backup/2012-06-27_17-53-46/

xtrabackup_55 version 2.0.0 for Percona Server 5.5.16 Linux (i686) (revision id: 417)
incremental backup from 1598476 is enabled.
xtrabackup: cd to /data/backup/2012-06-27_17-49-49
xtrabackup: This target seems to be already prepared.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1598476)
xtrabackup: page size for /data/backup/2012-06-27_17-53-46//ibdata1.delta is 16384 bytes
Applying /data/backup/2012-06-27_17-53-46//ibdata1.delta ...
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = /data/backup/2012-06-27_17-53-46/
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
120627 18:39:42 InnoDB: Using Linux native AIO
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
120627 18:39:42 InnoDB: The InnoDB memory heap is disabled
120627 18:39:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120627 18:39:42 InnoDB: Compressed tables use zlib 1.2.3
120627 18:39:42 InnoDB: Using Linux native AIO
120627 18:39:42 InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
120627 18:39:42 InnoDB: Initializing buffer pool, size = 100.0M
120627 18:39:42 InnoDB: Completed initialization of buffer pool
120627 18:39:42 InnoDB: highest supported file format is Barracuda.

[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
120627 18:39:42 InnoDB: Starting shutdown...
120627 18:39:43 InnoDB: Shutdown completed; log sequence number 1598476
innobackupex: Starting to copy non-InnoDB files in '/data/backup/2012-06-27_17-53-46/'
innobackupex: to the full backup directory '/data/backup/2012-06-27_17-49-49'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/xtrabackup_binlog_info'
innobackupex: Creating directory '/data/backup/2012-06-27_17-49-49performance_schema'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/performance_timers.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/setup_timers.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/rwlock_instances.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/cond_instances.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/events_waits_summary_by_instance.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/mutex_instances.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/file_summary_by_event_name.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/events_waits_history.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/events_waits_current.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/db.opt'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/events_waits_summary_by_thread_by_event_name.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/file_summary_by_instance.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/setup_instruments.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/file_instances.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/setup_consumers.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/threads.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/events_waits_history_long.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/events_waits_summary_global_by_event_name.frm'
innobackupex: Creating directory '/data/backup/2012-06-27_17-49-49mysql'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_topic.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/host.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/servers.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/tables_priv.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/proc.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/plugin.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/func.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/host.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/user.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/db.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_leap_second.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/proxies_priv.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/slow_log.CSV'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_name.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/event.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition_type.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/columns_priv.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_category.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/general_log.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition_type.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_name.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_keyword.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_topic.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/procs_priv.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_relation.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/procs_priv.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_keyword.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_keyword.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/user.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_category.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/event.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/func.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/slow_log.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/db.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/db.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/host.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_leap_second.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_relation.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/procs_priv.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/func.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_name.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_topic.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/proc.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/servers.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/proc.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/general_log.CSM'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_leap_second.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/columns_priv.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/ndb_binlog_index.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/tables_priv.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/user.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/proxies_priv.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/plugin.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/ndb_binlog_index.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_category.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/servers.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/tables_priv.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition_type.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/columns_priv.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/help_relation.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/ndb_binlog_index.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/proxies_priv.frm'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/general_log.CSV'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/plugin.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/event.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/slow_log.CSM'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition.MYI'
innobackupex: Creating directory '/data/backup/2012-06-27_17-49-49test'
120627 18:39:44 innobackupex: completed OK!
[root@localhost backup]#

增量备份2应用log，提交committed事务

[root@localhost backup]# innobackupex --apply-log --redo-only /data/backup/2012-06-27_17-49-49/ --incremental-dir=/data/backup/2012-06-27_18-13-35/

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
.....
.....
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/plugin.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/event.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/slow_log.CSM'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition.MYI'
120627 18:42:47 innobackupex: completed OK!
[root@localhost backup]#

增量备份3应用log,提交committed事务

[root@localhost backup]# innobackupex --apply-log --redo-only /data/backup/2012-06-27_17-49-49/ --incremental-dir=/data/backup/2012-06-27_18-30-15/

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

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

.....
.....
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/plugin.MYI'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/event.MYD'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/slow_log.CSM'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/time_zone_transition.MYI'
120627 18:43:38 innobackupex: completed OK!
[root@localhost backup]#

把所有的增量备份合并到full全备份里，然后回滚uncommitted的事务

[root@localhost backup]# innobackupex --apply-log /data/backup/2012-06-27_17-49-49/

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

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

120627 18:45:32 innobackupex: Starting ibbackup with command: xtrabackup_55 --prepare --target-dir=/data/backup/2012-06-27_17-49-49

xtrabackup_55 version 2.0.0 for Percona Server 5.5.16 Linux (i686) (revision id: 417)
xtrabackup: cd to /data/backup/2012-06-27_17-49-49
xtrabackup: This target seems to be already prepared.
xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
120627 18:45:32 InnoDB: Using Linux native AIO
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
120627 18:45:32 InnoDB: The InnoDB memory heap is disabled
120627 18:45:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120627 18:45:32 InnoDB: Compressed tables use zlib 1.2.3
120627 18:45:32 InnoDB: Using Linux native AIO
120627 18:45:32 InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
120627 18:45:32 InnoDB: Initializing buffer pool, size = 100.0M
120627 18:45:32 InnoDB: Completed initialization of buffer pool
120627 18:45:32 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
120627 18:45:32 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
120627 18:45:33 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120627 18:45:33 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120627 18:45:33 InnoDB: Waiting for the background threads to start
120627 18:45:34 Percona XtraDB (http://www.percona.com) 1.1.8-20.1 started; log sequence number 1598988

[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
120627 18:45:34 InnoDB: Starting shutdown...
120627 18:45:38 InnoDB: Shutdown completed; log sequence number 1598988

120627 18:45:38 innobackupex: Restarting xtrabackup with command: xtrabackup_55 --prepare --target-dir=/data/backup/2012-06-27_17-49-49
for creating ib_logfile*

[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
120627 18:45:39 InnoDB: Starting shutdown...
120627 18:45:43 InnoDB: Shutdown completed; log sequence number 1598988
120627 18:45:43 innobackupex: completed OK!

这时可以restore增量备份了

[root@localhost backup]# mv /data/mysql/usr/local/mysql/data /data/mysql/usr/local/mysql/data.bak
[root@localhost backup]# mkdir /data/mysql/usr/local/mysql/data
[root@localhost backup]# innobackupex --copy-back /data/backup/2012-06-27_17-49-49

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

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 '/data/backup/2012-06-27_17-49-49'
innobackupex: back to original data directory '/data/mysql/usr/local/mysql/data/'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//xtrabackup_checkpoints'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//ib_logfile1'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//ib_logfile0'
innobackupex: Creating directory '/data/mysql/usr/local/mysql/data//performance_schema'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//performance_timers.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//setup_timers.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//rwlock_instances.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//cond_instances.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//events_waits_summary_by_instance.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//mutex_instances.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//file_summary_by_event_name.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//events_waits_history.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//events_waits_current.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//db.opt'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//events_waits_summary_by_thread_by_event_name.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//file_summary_by_instance.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//setup_instruments.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//file_instances.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//setup_consumers.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//threads.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//events_waits_history_long.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//events_waits_summary_global_by_event_name.frm'
innobackupex: Creating directory '/data/mysql/usr/local/mysql/data//mysql'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_topic.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_transition.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//host.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//servers.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//tables_priv.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//proc.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//plugin.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//func.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//host.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//user.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//db.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_leap_second.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//proxies_priv.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//slow_log.CSV'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_name.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//event.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_transition_type.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//columns_priv.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_category.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//general_log.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_transition_type.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_name.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_keyword.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_topic.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//procs_priv.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_relation.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//procs_priv.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_keyword.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_keyword.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//user.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_category.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_transition.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//event.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//func.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//slow_log.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//db.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//db.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//host.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_leap_second.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_relation.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//procs_priv.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//func.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_name.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_topic.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//proc.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//servers.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//proc.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//general_log.CSM'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_leap_second.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//columns_priv.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//ndb_binlog_index.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//tables_priv.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//user.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//proxies_priv.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//plugin.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//ndb_binlog_index.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_category.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//servers.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//tables_priv.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_transition_type.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//columns_priv.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//help_relation.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//ndb_binlog_index.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//proxies_priv.frm'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//general_log.CSV'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//plugin.MYI'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//event.MYD'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//slow_log.CSM'
innobackupex: Copying file '/data/mysql/usr/local/mysql/data//time_zone_transition.MYI'
innobackupex: Creating directory '/data/mysql/usr/local/mysql/data//test'

innobackupex: Starting to copy InnoDB system tablespace
innobackupex: in '/data/backup/2012-06-27_17-49-49'
innobackupex: back to original InnoDB data directory '/data/mysql/usr/local/mysql/data/'
innobackupex: Copying file '/data/backup/2012-06-27_17-49-49/ibdata1'

innobackupex: Starting to copy InnoDB log files
innobackupex: in '/data/backup/2012-06-27_17-49-49'
innobackupex: back to original InnoDB log directory '/data/mysql/usr/local/mysql/data/'
innobackupex: Finished copying back files.

120627 18:49:29 innobackupex: completed OK!
[root@localhost backup]#

----end----

参考：http://www.percona.com/doc/percona-xtrabackup/innobackupex/incremental_backups_innobackupex.html

你可能感兴趣的:(mysql备份)

Mysql备份还原 qBeautifulBoy mysql 数据库
Mysql备份还原1、备份类型热备份、温备份、冷备份（根据服务器状态）热备份：读、写不受影响；温备份：仅可以执行读操作；冷备份：离线备份；读、写操作均中止；物理备份与逻辑备份（从对象来分）物理备份：复制数据文件；逻辑备份：将数据导出至文本文件中；完全备份、增量备份、差异备份（从数据收集来分）完全备份：备份全部数据；增量备份：仅备份上次完全备份或增量备份以后变化的数据；差异备份：仅备份上次完全备份以
策略变更管理：MySQL数据备份策略的持续优化之路 2401_85760095 mysql 数据库
在数据库管理中，备份策略的变更管理是确保数据安全性和业务连续性的关键环节。随着业务需求的变化和技术的演进，MySQL备份策略也需要不断地进行调整和优化。本文将深入探讨如何在MySQL中实现数据备份的策略变更管理，包括变更的规划、实施、测试和文档化。1.理解变更管理的重要性变更管理是IT服务管理中的一个重要组成部分，它涉及对IT基础设施的任何变更进行控制和跟踪。在MySQL数据备份策略中，变更管理确
MySQL 管理：全面指南 wjs2024 开发语言
MySQL管理：全面指南引言MySQL是目前最流行的开源关系数据库管理系统之一，以其高性能、易用性和可靠性而闻名。本篇文章将深入探讨MySQL的管理，包括安装、配置、性能优化、安全性和备份恢复等方面，旨在为数据库管理员和开发者提供一份全面的管理指南。目录MySQL简介MySQL安装与配置MySQL性能优化MySQL安全性管理MySQL备份与恢复MySQL高可用与集群MySQL监控与维护MySQL常
MySQL备份与主备配置 jxtxzzw
数据备份类型全量备份：备份整个数据库增量备份：备份自上一次备份以来（增量或完全）以来变化的数据差异备份：备份自上一次完全备份以来变化的数据全量备份全量备份的方法有2种，一种是利用数据库管理工具提供的备份恢复和导入导出功能。例如：如果使用Navicat、PHPMyAdmin之类的可视化工具，可以直接点击转储SQL文件，或者导出SQL文件之类的功能。另一种是利用mysqldump。导出：sudomys
【数据库运维】MYSQL备份恢复管理（下）小胖鲸~ 运维数据库 mysql 服务器
目录五，mysql备份策略3，策略三：mydumper备份数据库案例一：备份数据库sc的信息4，策略四：lvm快照从物理角度实现几乎热备的完全备份，配合二进制日志备份实现增量备份案例：lvm备份5，策略五：xtrabackup备份数据库，实现完全热备份与增量热备份案例一：完全备份案例二：增量备份五，mysql备份策略3，策略三：mydumper备份数据库（1）Mydumper安装[root@nod
mysql如何备份某些库的某些表 T_LOYO MySQL mysql 数据库
MySQL备份数据库mysql如何备份某些库的某些表要备份某个库里的部分表，该如何操作？例如：要备份db01库里的20张表，表很多又不想备份整个库或者要备份多个库里的不同表，又如何操作？例如：备份db01、db02、db03库里的部分表都可用下面的脚本方式执行备份：#!/bin/bash#MySQL数据库连接信息DB_HOST="localhost"DB_USER="your_username"D
Mysql及Oracle在Windows下备份与恢复满脑子灵感 mysql oracle windows
Mysql备份恢复一、备份分类、备份策略1.1造成数据丢失的原因：程序错误人为操作错误运算错误磁盘故障灾难（如火灾、地震）和盗窃1.2数据库备份的分类1）物理备份：对数据库操作系统的物理文件（如数据文件、日志文件等）的备份。冷备份(脱机备份)：是在关闭数据库的时候进行的热备份(联机备份)：数据库处于运行状态，依赖于数据库的日志文件温备份：数据库锁定表格（不可写入但可读）的状态下进行备份操作2）逻辑
MySQL备份与恢复解决方案远方 hi mysql 数据库运维
备份的主要目的是灾难恢复，备份还可以测试应用，回滚数据修改，查询历史数据，审计等。我们将从生产运维的角度了解备份恢复的分类与方法。在企业中数据的价值至关重要，数据保障了企业业务的运行，因此数据的安全性及可靠性是运维的重中之重，任何数据的丢失都有可能会对企业产生严重的后果。造成数据丢失的原因如下：程序错误人为错误数据泄露运算失败磁盘故障灾难（如火灾、地震）数据库类型物理和逻辑备份脱机备份（冷备备份）
MySQL备份与还原 Real_man
大学时候写的文章，再用一下MySQL常见备份方案有以下三种：mysqldump+binloglvm+binlogxtrabackupmysqldump本例为方便演示，数据库里面数据为空。下面开始动手mkdir/opt/backup#创建备份目录mkdir-p/data/3309/{data,binlog}cd/usr/local/mysql/scripts/mysql_install_db--us
MySQL的备份与恢复 Smiling Mr. Rui DATABASES mysql 数据库
目录一、MySQL日志管理1.1MySQL日志类型1.2错误日志1.3通用查询日志1.4慢查询日志1.5二进制日志日志滚动：二、MySQL备份2.1备份类型2.2MySQL自带的备份工具基于DBMS=====>mysqldump一、MySQL日志管理在数据库保存数据时，有时候不可避免会出现数据丢失或者被破坏，这样情况下，我们必须保证数据的安全性和完整性，就需要使用日志来查看或者恢复数据了。数据库中
MySQL备份和恢复（二）mysqldump w_t_y_y 关系型数据库MySQL mysql 数据库
注意：mysqldump是完全备份一、mysqldump备份命令1、备份数据库含创建库语句（1）备份指定数据库完全备份一个或多个完整的库，mysqldump-uroot-p[密码]--databases库名1[库名2]..>/备份路径/备份文件名.sql#导出的就是数据库脚本文件如（2）备份所有数据库完全备份MySQL服务器中所有的库（包括库中所有的表）mysqldump-uroot-p[密码]-
centos stream 9下mysql 备份我就是一王道 centos mysql 数据库
centosstream9下mysql备份文章目录centosstream9下mysql备份备份方式一、冷备份1.逻辑备份2.暴力备份3.mydumper备份二、热备份1.xtrabackup（下载地址[https://www.percona.com/downloads](https://www.percona.com/downloads)）备份方式一、冷备份1.逻辑备份mysql>flushta
MySQL备份和恢复（一）综述 w_t_y_y 关系型数据库MySQL mysql 数据库
目录一、备份分类：1、物理备份1.1、介绍1.2、方法2、逻辑备份二、备份策略1、完全备份（全量备份）：2、差异备份：3、增量备份：3.1、增量备份产生的原因3.2、增量备份的方法3.3、增量备份的策略三、常见的备份方法1、物理冷备（完全备份）1.1、特点1.2、步骤2、专用备份工具mydump或mysqlhotcopy（完全备份，逻辑备份）3、启用二进制日志进行增量备份4、第三方工具备份四、完全
Mysql运维篇（三） MySQL备份与恢复董乐，快乐的乐！ mysql oracle 数据库
一路走来，所有遇到的人，帮助过我的、伤害过我的都是朋友，没有一个是敌人。如有侵权，请留言，我及时删除！一、物理备份与逻辑备份1、物理备份：备份数据文件，转储数据库物理文件到某一目录。物理备份恢复速度比较快，但占用空间比较大，MySQL中可以用xtrabackup工具来进行物理备份。2、逻辑备份：对数据库对象利用工具进行导出工作，汇总入备份文件内。逻辑备份恢复速度慢，但占用空间小，更灵活。MySQL
备份MySQL数据库到centos7服务器 Sunnary_blog mysql mysql centos 服务器运维 vim
MySQL备份环境准备确保MySQL已经安装成功，这是前提条件。备份路径#备份文件路径/home/backup/mysql-backupshell脚本在/usr/local/backup路径下创建mysql-backup.sh脚本，内容如下：#!/bin/bash#以下配置信息请自己修改mysql_user="USER"#MySQL备份用户mysql_password="PASSWORD"#MyS
mysql备份大虾别跑 linux 数据库 mysql adb android
1.新建备份目录mkdir-p/data/mysql_dump/#查找mysql配置位置find/-name"my.cnf"find/-name"mysql.sock"find/-name"mysqldump"2.定时任务#每天凌晨备份一次echo"0000***root/data/mysql_bak.sh">>/etc/crontabcat>/data/mysql_bak.sh/data/mys
sql文件导入：ERROR : (2006, ‘MySQL server has gone away’...) EelBarb mysql 数据库运维
前言mysql备份、恢复亦或迁移，对运维工作者来说，都是一项无法推脱而又不得不做的工作。这里我将就mysql导入sql文件时报【ERROR:(2006,‘MySQLserverhasgoneaway’...)】这一问题进行解决。分析及解决从字面上看，这玩意儿的意思就是【数据库服务丢了，或者断开连接了】为什么呢？十有八九是客户端与mysql服务端之间的通讯发生了问题，导致服务端拒绝或被动断开了与客户
数据库（MySQL的备份和恢复）陳浩难数据库 mysql
目录1.1MySQL日志管理1.1.1MySQL日志类型1.1.2错误日志错误日志中主要记录的几种日志错误日志的定义1.1.3通用查询日志1.1.4慢查询日志和慢查询相关的变量设置1.1.5二进制日志二进制日志是记录执行的语句还是执行后的数据日志滚动1.2MySQL备份1.2.1备份类型1.2.2备份内容1.2.3常见的备份工具MySQL自带的工具其他工具1.1MySQL日志管理在数据库保存数据的
MySQL备份总结 chaodaibing mysql 数据库
物理备份通常物理备份是保障数据库备份最有效的方法，优于逻辑备份，且其对数据库本身性能的损耗相较于逻辑备份较低。MySQL的物理备份通常我们使用Percona公司出品的基于MySQL的服务器的开源热备份实用程序。其使用方法如下：#下载MySQL8.0https://www.percona.com/downloads/Percona-XtraBackup-LATESTMySQL5.7https://w
图解MySQL逻辑备份的实现流程云数据库技术数据库 mysql sql
1.摘要数据作为一家公司的重要资产，其重要程度不言而喻。数据库为数据提供存取服务，担任着重要的角色，如果因数据误删、服务器故障、病毒入侵等原因导致数据丢失或服务不可用，会对公司造成重大损失，所以数据库备份是数据系统中最为重要的一环。MySQL备份按照类型分为逻辑备份、物理备份、快照备份，本文将通过图文方式对常见的逻辑备份工具的一致性备份流程进行说明，来进一步了解逻辑备份的整个流程是怎么实现的。2.
【持续更新】Linux下常用的命令脚本布丁萨玛 linux adb android
mysql备份数据库mysqldump-u用户名-p密码--databases数据库名称>备份文件.sql备份全部数据库#!/bin/bash#MySQL用户名和密码MYSQL_USER="root"MYSQL_PASSWORD="XMhmyh2019."#备份保存路径BACKUP_DIR="/usr/mysqlbackup"#获取数据库列表DATABASES=$(mysql-u$MYSQL_US
windows系统Mysql备份脚本弗锐土豆 mysql db mysql 备份乱码 mysqldump windows
一.背景用的windowsserver2019服务器，mysql8.0.34，还是应该每天备份一下。以前做了很多次，主要是带了2个徒弟，还是要写出来。二.备份脚本chcp936setdate_tmp=%date:~0,10%setdatetime=%date_tmp:/=%%time:~0,2%%time:~3,2%%time:~6,2%setexecuteback=mysqldump-uroot
mysql数据备份还原（全量备份）思旭� mysql
还原mysql备份数据：备份：mysqldump-uusername-ppassword--all-databases>/backups/mysql_db1.sql还原：1.登录到MySQL服务器:mysql-uusername-ppassword2.选择要还原的数据库(如果备份中包含多个数据库的话):USEdatabase_name;3.执行还原命令:source/path/to/backup/
07.MySql的备份与恢复 Juvenile少年 mysql学习 mysql 数据库运维 sql dba
MySQL的备份与恢复一、MySQL的备份与恢复概述1、为什么进行备份与恢复2、MySQL备份与恢复的分类2.1根据数据备份策略进行分类2.2根据备份的方式和恢复的过程进行分类3、MySQL常见的备份与恢复3.1逻辑备份：3.2物理备份：二、MySQL备份与恢复的具体过程1、逻辑备份的具体过程：2、物理备份的具体过程：一、MySQL的备份与恢复概述1、为什么进行备份与恢复进行备份与恢复是数据库管理
《MySQL系列-InnoDB引擎07》MySQL备份与恢复 DATA数据猿 MySQL mysql 数据库
文章目录第七章备份与恢复1备份与恢复概述2冷备3逻辑备份3.1mysqldump3.2select...intooutfile3.3逻辑备份的恢复3.4loaddatainfile3.5mysqlimport4二进制日志备份与恢复5热备5.1ibbakup5.2XtraBackup6快照备份7复制7.1复制的工作原理7.2快照+复制的备份架构第七章备份与恢复为保证在服务器宕机、磁盘损坏、RAID卡
Mysql备份工具innobackupex简单操作及参数说明虎眼豆丁数据库 mysql 数据库 Xtrabackup innobackupex
Mysql备份工具innobackupex简单操作及参数说明Mysql备份工具innobackupex简单操作及参数说明简述简单操作全量备份全量恢复增量备份增量恢复操作过程如下增量回复Xtrabackup常用参数innobackupex参数--defaults-file=[MY.CNF]--databases=#--include=REGEXP--tables-file=FILE--apply-l
mysql备份与还原 gurlan
一、备份常用操作基本命令1、备份命令mysqldump格式格式：mysqldump-h主机名-P端口-u用户名-p密码–database数据库名>文件名.sql2、备份MySQL数据库为带删除表的格式备份MySQL数据库为带删除表的格式，能够让该备份覆盖已有数据库而不需要手动删除原有数据库。mysqldump--add-drop-table-uusername-ppassword-database
MySQL备份我是好人BING MySQL mysql 数据库
为什么要备份？保证重要的数据不丢失。数据转移MySQL数据库备份的方式拷贝物理文件。在Sqlyog这种可视化工具中手动导出。在想要导出的表或者库中，右键，选择备份或导出。使用命令行导出mysqldump命令进行。--导出mysqldump-h主机-u用户名-p密码数据库表名>物理磁盘位置/文件名mysqldump-h主机-u用户名-p密码数据库表名1表名2表名3>物理磁盘位置/文件名mysqldu
MYSQL无法用指令备份，出现异常孤独白鲸 mysql 数据库
mysql备份指令：mysqldump-u账号-p密码--databases数据库名>backupfile.sql出现错误如下：mysqldump:[Warning]Usingapasswordonthecommandlineinterfacecanbeinsecure.mysqldump:Goterror:2026:SSLconnectionerror:unknownerrornumberwhe
《MySQL系列-部署维护》通过表的.frm和.idb文件备份MySQL表 DATA数据猿 MySQL Linux mysql 数据库 bootstrap
MySQL备份表(.frm,.idb文件)目的:利用表的.frm和.idb文件备份MySQL表一、找到目标表的.frm和.idb文件‍♀1.在服务器上找到对应的文件，如果不清楚MySQL的数据路径在哪，可以参考如下:[root@zxy_master/]#find/-iname'bootstrap.frm'/var/lib/mysql/bigdata/bootstrap.frm‍♀2.找到/var/
java责任链模式 3213213333332132 java 责任链模式村民告县长
责任链模式，通常就是一个请求从最低级开始往上层层的请求，当在某一层满足条件时，请求将被处理，当请求到最高层仍未满足时，则请求不会被处理。就是一个请求在这个链条的责任范围内，会被相应的处理，如果超出链条的责任范围外，请求不会被相应的处理。下面代码模拟这样的效果：创建一个政府抽象类,方便所有的具体政府部门继承它。 package 责任链模式; /** *
linux、mysql、nginx、tomcat 性能参数优化 ronin47
一、linux 系统内核参数 /etc/sysctl.conf文件常用参数 net.core.netdev_max_backlog = 32768 #允许送到队列的数据包的最大数目 net.core.rmem_max = 8388608 #SOCKET读缓存区大小 net.core.wmem_max = 8388608 #SOCKET写缓存区大
php命令行界面 dcj3sjt126com PHP cli
常用选项 php -v php -i PHP安装的有关信息 php -h 访问帮助文件 php -m 列出编译到当前PHP安装的所有模块执行一段代码 php -r 'echo "hello, world!";' php -r 'echo "Hello, World!\n";' php -r '$ts = filemtime("
Filter&Session 171815164 session
Filter HttpServletRequest requ = (HttpServletRequest) req; HttpSession session = requ.getSession(); if (session.getAttribute("admin") == null) { PrintWriter out = res.ge
连接池与Spring,Hibernate结合 g21121 Hibernate
前几篇关于Java连接池的介绍都是基于Java应用的，而我们常用的场景是与Spring和ORM框架结合，下面就利用实例学习一下这方面的配置。 1.下载相关内容： &nb
[简单]mybatis判断数字类型 53873039oycg mybatis
昨天同事反馈mybatis保存不了int类型的属性,一直报错，错误信息如下: Caused by: java.lang.NumberFormatException: For input string: "null" at sun.mis
项目启动时或者启动后ava.lang.OutOfMemoryError: PermGen space 程序员是怎么炼成的 eclipse jvm tomcat catalina.sh eclipse.ini
在启动比较大的项目时，因为存在大量的jsp页面，所以在编译的时候会生成很多的.class文件，.class文件是都会被加载到jvm的方法区中，如果要加载的class文件很多，就会出现方法区溢出异常 java.lang.OutOfMemoryError: PermGen space. 解决办法是点击eclipse里的tomcat，在
我的crm小结 aijuans crm
各种原因吧，crm今天才完了。主要是接触了几个新技术： Struts2、poi、ibatis这几个都是以前的项目中用过的。 Jsf、tapestry是这次新接触的，都是界面层的框架，用起来也不难。思路和struts不太一样，传说比较简单方便。不过个人感觉还是struts用着顺手啊，当然springmvc也很顺手，不知道是因为习惯还是什么。jsf和tapestry应用的时候需要知道他们的标签、主
spring里配置使用hibernate的二级缓存几步 antonyup_2006 java spring Hibernate xml cache
．在spring的配置文件中 applicationContent.xml，hibernate部分加入 xml 代码 <prop key="hibernate.cache.provider_class">org.hibernate.cache.EhCacheProvider</prop> <prop key="hi
JAVA基础面试题百合不是茶抽象实现接口 String类接口继承抽象类继承实体类自定义异常
/* * 栈（stack）：主要保存基本类型（或者叫内置类型）（char、byte、short、 *int、long、 float、double、boolean）和对象的引用，数据可以共享，速度仅次于 * 寄存器（register），快于堆。堆（heap）：用于存储对象。 */ &
让sqlmap文件 "继承" 起来 bijian1013 java ibatis sqlmap
多个项目中使用ibatis , 和数据库表对应的 sqlmap文件（增删改查等基本语句)，dao, pojo 都是由工具自动生成的, 现在将这些自动生成的文件放在一个单独的工程中，其它项目工程中通过jar包来引用，并通过"继承"为基础的sqlmap文件，dao,pojo 添加新的方法来满足项
精通Oracle10编程SQL(13)开发触发器 bijian1013 oracle 数据库 plsql
/* *开发触发器 */ --得到日期是周几 select to_char(sysdate+4,'DY','nls_date_language=AMERICAN') from dual; select to_char(sysdate,'DY','nls_date_language=AMERICAN') from dual; --建立BEFORE语句触发器 CREATE O
【EhCache三】EhCache查询 bit1129 ehcache
本文介绍EhCache查询缓存中数据，EhCache提供了类似Hibernate的查询API，可以按照给定的条件进行查询。要对EhCache进行查询，需要在ehcache.xml中设定要查询的属性数据准备 @Before public void setUp() { //加载EhCache配置文件 Inpu
CXF框架入门实例白糖_ spring Web 框架 webservice servlet
CXF是apache旗下的开源框架，由Celtix + XFire这两门经典的框架合成，是一套非常流行的web service框架。它提供了JAX-WS的全面支持，并且可以根据实际项目的需要，采用代码优先（Code First）或者 WSDL 优先（WSDL First）来轻松地实现 Web Services 的发布和使用，同时它能与spring进行完美结合。在apache cxf官网提供
angular.equals boyitech AngularJS AngularJS API AnguarJS 中文API angular.equals
angular.equals 描述: 比较两个值或者两个对象是不是相等。还支持值的类型，正则表达式和数组的比较。两个值或对象被认为是相等的前提条件是以下的情况至少能满足一项：两个值或者对象能通过=== （恒等）的比较两个值或者对象是同样类型，并且他们的属性都能通过angular
java-腾讯暑期实习生-输入一个数组A[1,2,...n]，求输入B，使得数组B中的第i个数字B[i]=A[0]*A[1]*...*A[i-1]*A[i+1] bylijinnan java
这道题的具体思路请参看何海涛的微博：http://weibo.com/zhedahht import java.math.BigInteger; import java.util.Arrays; public class CreateBFromATencent { /** * 题目：输入一个数组A[1,2,...n]，求输入B，使得数组B中的第i个数字B[i]=A
FastDFS 的安装和配置修订版 Chen.H linux fastDFS 分布式文件系统
FastDFS Home:http://code.google.com/p/fastdfs/ 1. 安装 http://code.google.com/p/fastdfs/wiki/Setup http://hi.baidu.com/leolance/blog/item/3c273327978ae55f93580703.html 安装libevent (对libevent的版本要求为1.4.
[强人工智能]拓扑扫描与自适应构造器 comsci 人工智能
当我们面对一个有限拓扑网络的时候,在对已知的拓扑结构进行分析之后,发现在连通点之后,还存在若干个子网络,且这些网络的结构是未知的,数据库中并未存在这些网络的拓扑结构数据....这个时候,我们该怎么办呢? 那么,现在我们必须设计新的模块和代码包来处理上面的问题
oracle merge into的用法 daizj oracle sql merget into
Oracle中merge into的使用 http://blog.csdn.net/yuzhic/article/details/1896878 http://blog.csdn.net/macle2010/article/details/5980965 该命令使用一条语句从一个或者多个数据源中完成对表的更新和插入数据. ORACLE 9i 中，使用此命令必须同时指定UPDATE 和INSE
不适合使用Hadoop的场景 datamachine hadoop
转自：http://dev.yesky.com/296/35381296.shtml。　　Hadoop通常被认定是能够帮助你解决所有问题的唯一方案。当人们提到“大数据”或是“数据分析”等相关问题的时候，会听到脱口而出的回答：Hadoop! 实际上Hadoop被设计和建造出来，是用来解决一系列特定问题的。对某些问题来说，Hadoop至多算是一个不好的选择，对另一些问题来说，选择Ha
YII findAll的用法 dcj3sjt126com yii
看文档比较糊涂，其实挺简单的： $predictions=Prediction::model()->findAll("uid=:uid",array(":uid"=>10)); 第一个参数是选择条件：”uid=10″。其中:uid是一个占位符，在后面的array(“:uid”=>10)对齐进行了赋值；更完善的查询需要
vim 常用 NERDTree 快捷键 dcj3sjt126com vim
下面给大家整理了一些vim NERDTree的常用快捷键了，这里几乎包括了所有的快捷键了，希望文章对各位会带来帮助。切换工作台和目录 ctrl + w + h 光标 focus 左侧树形目录ctrl + w + l 光标 focus 右侧文件显示窗口ctrl + w + w 光标自动在左右侧窗口切换ctrl + w + r 移动当前窗口的布局位置 o 在已有窗口中打开文件、目录或书签，并跳
Java把目录下的文件打印出来蕃薯耀列出目录下的文件文件夹下面的文件目录下的文件
Java把目录下的文件打印出来 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 蕃薯耀 2015年7月11日 11:02:
linux远程桌面----VNCServer与rdesktop hanqunfeng Desktop
windows远程桌面到linux，需要在linux上安装vncserver，并开启vnc服务，同时需要在windows下使用vnc-viewer访问Linux。vncserver同时支持linux远程桌面到linux。 linux远程桌面到windows，需要在linux上安装rdesktop，同时开启windows的远程桌面访问。下面分别介绍，以windo
guava中的join和split功能 jackyrong java
guava库中，包含了很好的join和split的功能，例子如下： 1）将LIST转换为使用字符串连接的字符串 List<String> names = Lists.newArrayList("John", "Jane", "Adam", "Tom");
Web开发技术十年发展历程 lampcy android Web 浏览器 html5
回顾web开发技术这十年发展历程： Ajax 03年的时候我上六年级，那时候网吧刚在小县城的角落萌生。传奇，大话西游第一代网游一时风靡。我抱着试一试的心态给了网吧老板两块钱想申请个号玩玩，然后接下来的一个小时我一直在，注，册，账，号。彼时网吧用的512k的带宽，注册的时候，填了一堆信息，提交，页面跳转，嘣，”您填写的信息有误，请重填”。然后跳转回注册页面，以此循环。我现在时常想，如果当时a
架构师之mima-----------------mina的非NIO控制IOBuffer(说得比较好) nannan408 buffer
1.前言。如题。 2.代码。 IoService IoService是一个接口，有两种实现：IoAcceptor和IoConnector；其中IoAcceptor是针对Server端的实现，IoConnector是针对Client端的实现；IoService的职责包括： 1、监听器管理 2、IoHandler 3、IoSession
ORA-00054:resource busy and acquire with NOWAIT specified Everyday都不同 oracle session Lock
[Oracle] 今天对一个数据量很大的表进行操作时，出现如题所示的异常。此时表明数据库的事务处于“忙”的状态，而且被lock了，所以必须先关闭占用的session。 step1，查看被lock的session： select t2.username, t2.sid, t2.serial#, t2.logon_time from v$locked_obj
javascript学习笔记 tntxia JavaScript
javascript里面有6种基本类型的值:number、string、boolean、object、function和undefined。number：就是数字值，包括整数、小数、NaN、正负无穷。string:字符串类型、单双引号引起来的内容。boolean:true、false object:表示所有的javascript对象，不用多说function:我们熟悉的方法，也就是
Java enum的用法详解 xieke90 enum 枚举
Java中枚举实现的分析：示例： public static enum SEVERITY{ INFO,WARN,ERROR } enum很像特殊的class，实际上enum声明定义的类型就是一个类。而这些类都是类库中Enum类的子类 (java.l