On 4/12/06, Tim Lucia <[EMAIL PROTECTED]> wrote:
> Would you not lock tables on the slave? The idea of catching it up implies
> this is way it is done. Catching up means once replication can proceed once
> the tables are unlocked (on the slave).
>
> At least that is the way I read it...
On the s
Would you not lock tables on the slave? The idea of catching it up implies
this is way it is done. Catching up means once replication can proceed once
the tables are unlocked (on the slave).
At least that is the way I read it...
Tim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[E
d have the data be as portable as
necessary.
Just my $0.02.
J.R.
-Original Message-
From: Dana Diederich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 9:15 AM
To: Greg 'groggy' Lehey; Jim
Cc: mysql@lists.mysql.com
Subject: RE: mySQL Backups
We use a dedicated rep
ggy' Lehey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 4:05 AM
To: Jim
Cc: mysql@lists.mysql.com
Subject: Re: mySQL Backups
On Tuesday, 11 April 2006 at 18:40:23 +1000, Jim wrote:
>
> What is the standard procedure for mySQL backups.
> We need to backup at least once a d
On Tuesday, 11 April 2006 at 18:40:23 +1000, Jim wrote:
>
> What is the standard procedure for mySQL backups.
> We need to backup at least once a day on a windows OS.
> Is there a SQL Server Job Agent type solution?
At the moment it's a mess. We're working on cleaning up the mess, and
you should
Jim wrote:
Hi All,
What is the standard procedure for mySQL backups.
We need to backup at least once a day on a windows OS.
Is there a SQL Server Job Agent type solution?
mysql has an implemented mysqldumper.
You could use that.
Ther are also some php dumper scripts and perl scripts
