First of all, I'd like to point to the documentation =]
http://www.mysql.com/doc/B/a/Backup.html
The other option not mentioned there but that another list member
suggested is the best way to backup a live database. The above two
methods work, but with larger databases, having the tables locked for
more than a few seconds while you back them up can cause timeouts.
Having a second machine with replication lets you back up the database
without this concern, and also gives you the benefit of having a server
to replace your primary server should it fail. Also note that if your
second server (replica) will never see production, then it can get by
with significantly lower machine requirements than any production server
since it won't be serving any queries or such. HTH
> -----Original Message-----
> From: Joshua J. Kugler [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 29, 2001 11:52 AM
> To: David Turner; Matthew Walker
> Cc: MySQL Mailling List
> Subject: Re: Hot Backups
>
>
> I'm doing a mysqldump and then backing up the resulting text
> file. Works
> fine, doesn't interupt anything, and doesn't have any
> problems with a live
> server. IIRC, mysqldump locks a table before it dumps, so
> there won't be any
> funny records. Or course, mysqldump could catch the database
> in the middle
> of a multi-table backup. But so can any live backup system.
>
> j----- k-----
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
