On Thu, Jul 08, 2004 at 01:17:04PM +0300, John wrote: > Ok, can mysqlhotcopy create a dump? That is what i want. like mysqldump (in > my case the mysql server is absoloutely inactive during the whole night, > therefore i don't case about speed or locking the tables :) )
mysqlhotcopy creates a copy of the database that's usable as a database. For example we copy database Foo to Foo_copy (and the previous Foo_copy becomes Foo_copy_old) each night. The copies are then archived to tape. We can then run queries on Foo_copy and Foo_copy_old if we want. Tim. > ----- Original Message ----- > From: "Tim Bunce" <[EMAIL PROTECTED]> > To: "John" <[EMAIL PROTECTED]> > Cc: "DBI-Users" <[EMAIL PROTECTED]> > Sent: Thursday, July 08, 2004 11:59 AM > Subject: Re: Automating database full backup > > > > On Thu, Jul 08, 2004 at 10:05:32AM +0300, John wrote: > > > Well, If we are talking about mysql utilites, then mysqldump is an > excellent > > > tool for me and what i wan to do. > > > > It works fine, but is much slower than mysqlhotcopy, which is a problem > > when you want to take a hot backup of a production system. > > > > > But I cannot put the mysqldump in a shell script (a cron then) because > it is > > > quite interactive when it promtes you set a password (root, or whatever > > > else). > > > > > > Thus, i thought about perl and its impressive capabilities. > > > > > > Do you know how could i overcome this mysqldump interactivity through i > > > shell script? > > > > All parameters can be given on the command line, including the password. > > (That will make the password visible to anyone who can run "ps" but there > > are ways round that if that's a concern.) > > > > Tim. > > > > > ----- Original Message ----- > > > From: "Tim Bunce" <[EMAIL PROTECTED]> > > > To: "Hardy Merrill" <[EMAIL PROTECTED]> > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > > Sent: Wednesday, July 07, 2004 9:09 PM > > > Subject: Re: Automating database full backup > > > > > > > > > > On Wed, Jul 07, 2004 at 01:41:19PM -0400, Hardy Merrill wrote: > > > > > A bit OT here, but I'm curious - does mysqlhotcopy allow you to do a > > > > > backup without shutting down MySQL? > > > > > > > > Yes, hence "hot" copy. > > > > > > > > > http://dev.mysql.com/doc/mysql/en/mysqlhotcopy.html > > > > > > > > [Umm, ought to ask them to acknowledge that I wrote and contributed > it.] > > > > > > > > > I know this is over-simplifying, but couldn't automating MySQL > backups > > > > > with mysqlhotcopy be as simple as adding a MySQL user with read(?) > privs > > > > > to the database(s) to be backed up, and then putting a > "mysqlhotcopy" > > > > > command with all the necessary options into a cron job or windows > > > > > scheduler? > > > > > > > > Yes. (Though I don't know about windows.) > > > > > > > > Tim. > > > > > > > > > Hardy > > > > > > > > > > >>> Tim Bunce <[EMAIL PROTECTED]> 07/07/04 01:30PM >>> > > > > > I believe mysql also ships with mysqlhotcopy (which I wrote) > > > > > you may find it useful. > > > > > > > > > > Tim. > > > > > > > > > > On Wed, Jul 07, 2004 at 10:05:42AM -0400, Hardy Merrill wrote: > > > > > > I quick search on google for "automate mysql backup perl dbi" > > > > > > > > > > > > revealed this as one of the 1st 5 links: > > > > > > http://www.csc.liv.ac.uk/~u2pj/SQL_Perl.htm > > > > > > > > > > > > Check out "RW MySQL Dump" - looks to me like it might be just what > > > > > > you're looking for. Or if you still want to do it yourself, just > > > > > > reading its description might put you on the right track. > > > > > > > > > > > > You'll get more help here if you actually try to help yourself > first > > > > > - > > > > > > at least make an effort to find some information *before* you ask > > > > > for > > > > > > help. > > > > > > > > > > > > Hardy Merrill > > > > > > > > > > > > >>> "John" <[EMAIL PROTECTED]> 07/07/04 09:52AM >>> > > > > > > I want to automate a mysql backup > > > > > > > > > > > > Can this be done via perl and how? > > > > > > > > > > > > > >
