PDA

View Full Version : ZRM - Failing to backup



vdharan
October 14th, 2013, 06:33 AM
Dear Members,

I have created a backup set by the name dr_gec and trying to backup table1 and table2 of the DB dbgec. When I run mysql-zrm-backup, the log says that Backup failed. But inside the backup folder there is a backup.sql file.

Please suggest me where Iam going wrong.

Thanks and Regards,
vdharan


-----------------
root@srv [/etc/mysql-zrm/dr_gec]# mysql-zrm-backup --backup-set dr_gec
backup:INFO: ZRM for MySQL Community Edition - version 3.0
dr_gec:backup:INFO: START OF BACKUP
dr_gec:backup:INFO: PHASE START: Initialization
dr_gec:backup:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
dr_gec:backup:WARNING: Binary logging is off.
dr_gec:backup:INFO: backup-set=dr_gec
dr_gec:backup:INFO: backup-date=20131014195043
dr_gec:backup:INFO: mysql-server-os=Linux/Unix
dr_gec:backup:INFO: backup-type=regular
dr_gec:backup:INFO: host=localhost
dr_gec:backup:INFO: backup-date-epoch=1381760443
dr_gec:backup:INFO: retention-policy=3D
dr_gec:backup:INFO: mysql-zrm-version=ZRM for MySQL Community Edition - version 3.0
dr_gec:backup:INFO: mysql-version=5.5.33-31.1-log
dr_gec:backup:INFO: backup-directory=/backup/lemsbackup/zrm/dr_gec/20131014195043
dr_gec:backup:INFO: backup-level=0
dr_gec:backup:INFO: backup-mode=logical
dr_gec:backup:INFO: PHASE END: Initialization
dr_gec:backup:INFO: PHASE START: Running pre backup plugin
dr_gec:backup:INFO: PHASE END: Running pre backup plugin
dr_gec:backup:INFO: PHASE START: Flushing logs
Warning: Using unique option prefix pass instead of password is deprecated and will be removed in a future release. Please use the full name instead.
dr_gec:backup:INFO: PHASE END: Flushing logs
dr_gec:backup:INFO: PHASE START: Creating logical backup
dr_gec:backup:INFO: Command exit status is : 0
dr_gec:backup:ERROR: Output of command: 'command is : bash -c 'mysqldump --opt --extended-insert --create-options --default-character-set=utf8 --single-transaction dbgec table1 table2 > "/backup/lemsbackup/zrm/dr_gec/20131014195043/backup.sql" 2>>/tmp/L1nGOi1K84;echo ${PIPESTATUS[@]} > /tmp/SfD34vkFZy 2>>/tmp/L1nGOi1K84'' is {
Warning: Using unique option prefix pass instead of password is deprecated and will be removed in a future release. Please use the full name instead.
}
dr_gec:backup:ERROR: Output of command: 'pipe exit status' is {
0
}
dr_gec:backup:ERROR: mysqldump did not succeed.
dr_gec:backup:INFO: PHASE START: Cleanup
dr_gec:backup:INFO: backup-status=Backup failed
dr_gec:backup:INFO: Backup failed
dr_gec:backup:INFO: PHASE END: Cleanup
dr_gec:backup:INFO: END OF BACKUP
----------------

pelacables
November 6th, 2013, 02:53 AM
Hi,

I think your're having more or less the same issue as I.
the dump generates a warning :
"Warning: Using unique option prefix pass instead of password is deprecated and will be removed in a future release. Please use the full name instead"
and zrm saves it in ERROR file (temporary /tmp/L1nGOi1K84), then the code checks for content in that file:

line 1852 /usr/bin/mysql-zrm-backup :

if(( $r > 0 ) || (-s $CMDERR)) {

the file exists but the content is not an error (notice that pipe exit ssttau is 0 which means dump finished fine).

you have 3 options:
1.-) fix the warning
2.-) fix the code (instead of -s something that checks the content of the file)
3.-) if(( $r > 0 ) || (-s $CMDERR)) { -> if( $r > 0 ) {

HTH,
Arnau