我使用的是perl脚本,它在我的另一个盒子中工作得很好,它用来进行单独的模式备份&最后,使用将所有模式合并在一起。
我在日志中有以下信息(张贴一天日志详细信息):
--slave-info is used with --no-lock but without --safe-slave-backup. The
binlog position cannot be consistent with the backup data.
Died at /apps/mysql/scripts/mysql_backup.pl line 214.
[Fri Oct 26 04:20:01 2012] [14670]
[Fri Oct 26 04:20:01 2012] [14670] Starting individual backups
[Fri Oct 26 04:20:01 2012] [14670]
[Fri Oct 26 04:20:01 2012] [14670] Backing up proddb
[Fri Oct 26 04:20:01 2012] [14670] Creating /tmp/mysql_backup-14670.fifo
[Fri Oct 26 04:20:01 2012] [14670] Starting /usr/local/bin/zipmt -s -t 4
-c - < /tmp/mysql_backup-14670.fifo > /apps/dbbackup/proddb02.backup-
2012-10-26-042001-proddb.dmp.bz2
[Fri Oct 26 04:20:01 2012] [14670] Starting /usr/bin/innobackupex
--slave-info --no-lock --stream=tar --databases proddb ./ >
/tmp/mysql_backup-14670.fifo
[Fri Oct 26 04:20:02 2012] [14670] FAIL: /usr/bin/innobackupex
--slave-info --no-lock --stream=tar --databases proddb ./ >
/tmp/mysql_backup-14670.fifo failed 256详细信息见/app/dbbackup/backup.log。
Cause:
/usr/bin/innobackupex --slave-info --no-lock --stream=tar --databases
proddb ./ > /tmp/mysql_backup-14670.fifo failed 256即使备份失败后,/tmp中仍然存在命名管道:
ls -lrth /tmp
=============
prw-r--r--. 1 root root 0 Oct 25 04:20 mysql_backup-18215.fifo
prw-r--r--. 1 root root 0 Oct 26 04:20 mysql_backup-14670.fifo
prw-r--r--. 1 root root 0 Oct 27 04:20 mysql_backup-11278.fifo
prw-r--r--. 1 root root 0 Oct 28 04:20 mysql_backup-7163.fifo
prw-r--r--. 1 root root 0 Oct 29 04:20 mysql_backup-4191.fifo
prw-r--r--. 1 root root 0 Oct 30 04:20 mysql_backup-595.fifo知道吗,为什么备份失败了?
发布于 2012-11-08 07:54:57
尝试使用选项:-安全从备份
This is for consistent backup on the slave machines.
This option basically stops the slave SQL activity dueing the backup
of individual DBs.
You will see slave SQL thread error and initilization messages
regularly during the backup.希望这能有所帮助。请告诉我们结果..。
https://dba.stackexchange.com/questions/27890
复制相似问题