Yep.
----- Original Message -----
From: "Jeff McKeon" <[EMAIL PROTECTED]>
To: "Jeremiah Gowdy" <[EMAIL PROTECTED]>; <mysql@lists.mysql.com>
Sent: Friday, June 03, 2005 12:11 PM
Subject: RE: mysqlhotcopy
Am I right in assuming that while mysqlhotcopy is running, nobody else
can write to or update the DB?
Jeff
-----Original Message-----
From: Jeremiah Gowdy [mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 2:24 PM
To: Jeff McKeon; mysql@lists.mysql.com
Subject: Re: mysqlhotcopy
I run 24/7 applications also. Use mysqlhotcopy to do exactly
what you're
doing by hand now. Run mysqlhotcopy on a slave server. It
does exactly
what you think. Lock and flush the tables, tarball them, and
unlock them.
No shutdown required.
----- Original Message -----
From: "Jeff McKeon" <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Friday, June 03, 2005 11:11 AM
Subject: mysqlhotcopy
Hello,
Anyone here run mysqlhotcopy? I've read the docs on it but
they are basicly just a howto and don't go too in depth.
I've got a DB that is the back end to a 24/7 application. I
ususally do backups from a replicated db by shutting down the
Replicated DB then doing a tar are all the db files, then
starting the db when done. Does mysqlhotcopy allow you to
take a full snapshot of the db without needing to shut it
down? What happens to read writes and updates while
mysqlhotcopy is running?
Any info or experiences anyone has would be greatly appreciated.
Thanks,
Jeff
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
