> > Jim,
> >
> > I didn't word my question quite right because I was only guessing at
> > what a LVM snapshot was. Moreover, what you're saying is all correct.
> > However, I was not suggesting that the snapshot be kept around once the
> > backup is made.
> >
> > Let's go to article "What is a
George Herson said:
> James G. Sack (jim) wrote:
>
>>On Mon, 2005-09-19 at 13:14 -0400, George Herson wrote:
>>
>>
>>>James G. Sack (jim) wrote:
>>>
>>>
>>>
On Mon, 2005-09-19 at 12:15 -0400, George Herson wrote:
>Dear Jim,
>
>Re: your post at http://lists.mysql.
James G. Sack (jim) wrote:
On Mon, 2005-09-19 at 13:14 -0400, George Herson wrote:
James G. Sack (jim) wrote:
On Mon, 2005-09-19 at 12:15 -0400, George Herson wrote:
Dear Jim,
Re: your post at http://lists.mysql.com/mysql/189058, why bothe
On Mon, 2005-09-19 at 13:14 -0400, George Herson wrote:
> James G. Sack (jim) wrote:
>
> >On Mon, 2005-09-19 at 12:15 -0400, George Herson wrote:
> >
> >
> >>Dear Jim,
> >>
> >>Re: your post at http://lists.mysql.com/mysql/189058, why bother
> >>creating the mysqldump if you already have the sn
James G. Sack (jim) wrote:
On Mon, 2005-09-19 at 12:15 -0400, George Herson wrote:
Dear Jim,
Re: your post at http://lists.mysql.com/mysql/189058, why bother
creating the mysqldump if you already have the snapshot? Why not just
backup the snapshot?
[...]
The output of mysqldump *i
On Mon, 2005-09-19 at 12:15 -0400, George Herson wrote:
> Dear Jim,
>
> Re: your post at http://lists.mysql.com/mysql/189058, why bother
> creating the mysqldump if you already have the snapshot? Why not just
> backup the snapshot?
>
> (I'd have hit reply online but didn't see a Reply button a
quoting Alan Williamson <[EMAIL PROTECTED]> ..
>> This recipe is intended to minimize the impact on ongoing database
>> operations by inhibiting writes only during a relatively speedy
>> operation (creating a snapshot). The long dump operation can ...
>
>This seems to be a rather long winded way o
> This recipe is intended to minimize the impact on ongoing database
> operations by inhibiting writes only during a relatively speedy
> operation (creating a snapshot). The long dump operation can ...
This seems to be a rather long winded way of doing this. Why not
replicate the database and th
Hello.
A few months ago you've been writing about issues with InnoDB
when using a similar recipe. Please, share your experience of
how you've solved that problems.
"James G. Sack (jim)" <[EMAIL PROTECTED]> wrote:
> This recipe is intended to minimize the impact on ongoing database
> ope
This recipe is intended to minimize the impact on ongoing database
operations by inhibiting writes only during a relatively speedy
operation (creating a snapshot). The long dump operation can then be
performed on the (stable) snapshot, without interfering with ongoing use
of the live database.
1.
10 matches
Mail list logo