holland-coredev team mailing list archive

[Andrew Garner <1236595@xxxxxxxxxxxxxxxxxx>]

** Changed in: holland-backup
     Assignee: (unassigned) => Andrew Garner (muzazzi)

** Changed in: holland-backup
       Status: New => Confirmed

** Changed in: holland-backup
   Importance: Undecided => Critical

** Changed in: holland-backup
    Milestone: None => 1.0.12

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

Title:
  xtrabackup datadir not defined

Status in Holland Backup Framework:
  Confirmed

Bug description:
  When using mysqld multi and using xtrabackup, xtrabackup will fail by
  default since datadir is probably only defined in the [mysqld1]
  secton, but it's reading the [mysqld] section.  I have seen this be a
  minor headache in several cases now and require manual configuration.

  This can be fixed by using additional-options = --defaults-
  group=mysqld1 in the holland.conf, but the datadir information is
  pretty readily available to us.

  holland could write a [mysqld] section to the generated my.cnf and
  grab @@datadir directly from the running instance.  That my.cnf format
  would look like:

  [mysqld]
  datadir = @@datadir

  !include ${global my.cnf from holland's global-defaults}
  !include ${defaults-files from [mysql:client] section (e.g. /root/.my.cnf)}

  This will help avoid false failures - and if the datadir really is
  defined, it will override holland's settings anyway via the !include
  (so holland isn't masking user requested options).

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