holland-coredev team mailing list archive

[Andrew Garner <1251766@xxxxxxxxxxxxxxxxxx>]

Notably, we should guide users to instead use holland's exclude-invalid-
views option instead, which is somewhat more robust and does a better
job of recording the original view definition.   There are still likely
cases where a "best effort" backup may be desired, however.

-- 
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/1251766

Title:
  holland-mysqldump and --force

Status in Holland Backup Framework:
  New

Bug description:
  holland-mysqldump does not support mysqldump --force today.  holland
  checks the exit status of msyqldump and if this is not zero, it
  assumes a failed, useless backup.   Often mysqldump --force is
  suggested as a workaround for dealing with invalid views, but this
  will potentially skip over more serious errors as well.

  Holland should probably have a mode where it will honor --force and
  ignore mysqldump's exit status.   Possibly we can verify the dump by
  some combination of:

  * checking for a final -- Dump completed line (assume a user didn't add a custom --skip-dump-date option)
  * parsing the errors mysqldump emits on stderr to discern their seriousness
  * validating gzip or other compression command exited fine otherwise (i.e. no EPIPE errors).

To manage notifications about this bug go to:
https://bugs.launchpad.net/holland-backup/+bug/1251766/+subscriptions