holland-coredev team mailing list archive

[Andrew Garner <1187012@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

holland 1.0.8+ enables apply-logs by default and attempts to run through
innobackupex --apply-logs at the end of a backup.  This is automatically
disabled if streaming or compression is detected (where we can't
trivially apply logs).   However, this is also broken in the case of
incremental backups - where someone sets --incremental* options in the
config's additional-options.

So I suppose we should try to detect this situation by either checking
for --incremental there, just as we check for --compress, or perhaps go
back to not running apply-logs automatically.

** Affects: holland-backup
     Importance: Undecided
         Status: New

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

Title:
  xtrabackup incrementals and apply-logs

Status in Holland Backup Framework:
  New

Bug description:
  holland 1.0.8+ enables apply-logs by default and attempts to run
  through innobackupex --apply-logs at the end of a backup.  This is
  automatically disabled if streaming or compression is detected (where
  we can't trivially apply logs).   However, this is also broken in the
  case of incremental backups - where someone sets --incremental*
  options in the config's additional-options.

  So I suppose we should try to detect this situation by either checking
  for --incremental there, just as we check for --compress, or perhaps
  go back to not running apply-logs automatically.

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