mylvmbackup-discuss team mailing list archive

["Boehm, Matthew" <mboehm@xxxxxxxxxxxxx>]

Oh I see what you are saying now. Sorry, no coffee yet. I have no idea
what InnoDb will do when doing recovery on a system that had
file-per-table flag but doesn't have it now. Experimentation/proof is
needed that it won't affect those of us that are not using
file-per-table.

-Matthew

-----Original Message-----
From: Tim Stoop [mailto:tim.stoop@xxxxxxxxx] 
Sent: Monday, February 02, 2009 11:08 AM
To: Boehm, Matthew
Cc: mylvmbackup-discuss@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Mylvmbackup-discuss] Adding --innodb-file-per-table

Isn't it needed for a setup that has that? Will it recover logs for
tables that are in a separate file?

On Mon, Feb 2, 2009 at 3:22 PM, Boehm, Matthew <mboehm@xxxxxxxxxxxxx>
wrote:
> Why would you want that though? Like you said, it wouldnt affect
anything,
> so why add it as a new option if it isnt needed?
>
> Matthew Boehm
> C: 832-253-8258
> W: mboehm@xxxxxxxxxxxxx
> P: matthew@xxxxxxxxxxxxxxxx
>
> Sent from my iPhone
>
> On Feb 2, 2009, at 6:45 AM, "Tim Stoop" <tim.stoop@xxxxxxxxx> wrote:
>
>> Hi all,
>>
>> I was wondering what could go wrong when I should add
>> "--innodb-file-per-table" to the mysqld commandline for recovering
>> from the InnoDB logs. This would be line 600 in 0.11. As far as I can
>> see, it keeps everything in tact, only create the actual file per
>> table if a new table is created or an ALTER TABLE is run on an
>> existing table. Since both operations shouldn't happen with
>> mylvmbackup, I think it would be safe to just add that option per
>> default?
>>
>> Or am I overlooking something here?
>>
>> --
>> Gegroet,
>> Tim
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~mylvmbackup-discuss
>> Post to     : mylvmbackup-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~mylvmbackup-discuss
>> More help   : https://help.launchpad.net/ListHelp
>



-- 
Gegroet,
Tim