Didn't read your last item before I fired my last message off. If mysqldump locks the
table before it dumps then it is interupting service. If I have a high number of
transactions they're blocked until the lock is released.
Dave
On Wed, Aug 29, 2001 at 10:52:26AM -0800, Joshua J. Kugler wrote:
> 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-----
>
> On Wednesday 29 August 2001 10:52, David Turner wrote:
> > The way I am planning on doing it is setting up another server that I
> > replicated to and backing that server up. I would like to hear how other
> > people are backing up servers without interupting service.
> >
> > Dave
> >
> > On Wed, Aug 29, 2001 at 12:50:06PM -0600, Matthew Walker wrote:
> > > What's the best way of doing a hot backup on a database? Our server is
> > > set up in such a way that it's not a simple matter to shut down
> > > apache/mysql and do the backup then. So, is it safe to just copy the
> > > mysql directories, or is there some recommended procedure for this?
>
> --
> Joshua Kugler, Information Services Director
> Associated Students of the University of Alaska Fairbanks
> [EMAIL PROTECTED], 907-474-7601
---------------------------------------------------------------------
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
