holland-coredev team mailing list archive
-
holland-coredev team
-
Mailing list archive
-
Message #00256
[Bug 962441] Re: holland-xtrabackup dry run does not check for innobackup parse error
holland-xtrabackup runs xtrabackup with --defaults-file=${holland-
defaults} --help to verify the defaults file will be usable by
xtrabackup. Further, xtrabackup upstream has finally merged a fix for
--innobackup=force in recent versions.
** Changed in: holland-backup
Milestone: 1.1.0a3 => 1.0.8
** Changed in: holland-backup
Status: New => Fix Released
--
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/962441
Title:
holland-xtrabackup dry run does not check for innobackup parse error
Status in Holland Backup Framework:
Fix Released
Bug description:
Currently if you have innodb=force in my.cnf, xtrabackup will fail:
https://bugs.launchpad.net/bugs/528752
If you have this option in my.cnf, a dry run will indicate a backup
should succeed and it will later fail with xtrabackup: ambiguous
option '--innodb=force'
During --dry-run, we should run if xtrabackup --help --verbose or some
similar quick check that there are no errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/holland-backup/+bug/962441/+subscriptions
References