List:Backup« Previous MessageNext Message »
From:Ingo Strüwing Date:May 3 2010 2:46pm
Subject:innobackup deficiencies w.r.t. MTR testing
View as plain text  
Hi team,

please note that I collected these deficiencies of innobackup with
respect to mysql-test-run testing by now:

1. innobackup does not allow its caller to select the target directory.
It allows to select a backup directory, but inside of it, it creates a
new directory with a name made of date and time with seconds precision.
It is impossible to predict the name of that directory. One can have a
unique backup dir per test run and take its only entry as the target
directory. Or one can grep the directory name from innobackup's output.
An include file for this purpose is in the works.

2. innobackup does not allow its caller to specify the path, where the
'mysql' utility is located. It just calls 'mysql' and expect it to be
located in the PATH. mysqltest can set environment variables, but it
cannot read them (AFAIK). This means, one cannot add a path to the PATH
variable (and it would barely be portable to Windows). The only option
seems to be to call innobackup indirectly from a (perl) script, which
sets up PATH. Such script could the also handle the problem (1) above.
I'm going to develop such script unless someone wants to take over (or
has solved it already).

Ingo Strüwing, Database Group
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschäftsführer: Jürgen Kunz                     HRB München 161028
innobackup deficiencies w.r.t. MTR testingIngo Strüwing3 May
  • Re: innobackup deficiencies w.r.t. MTR testingHema3 May
  • Re: innobackup deficiencies w.r.t. MTR testingIngo Strüwing4 May