List:General Discussion« Previous MessageNext Message »
From:Martin Ramsch Date:July 13 1999 12:10pm
Subject:Re: Approach to database backup??
View as plain text  
On Di, 1999-07-13 14:26:19 +0300, Sinisa Milivojevic wrote:
>  > > One of the most elegant backup strategy would be to lock all tables
>  > > for read. This will wait until all other threads finish their updating 
>  > > of all tables, and will put them in waitings for other new
>  > > writes.Then, in the same thread, mysqldump should be run, with -e and
>  > > -q options, piped optionally through gzip stream to backup
>  > > device. Then UNLOCK of the tables should be performed.
[...]
> After reviewing what I wrote, I concluded that LOCKS are NOT
> necessay. You can run mysqldump so that it does all the locking /
> unlocking.

   mysqldump --opt ...

should do all the work.  It this what you meant?

Running "mysqldump --help" says that "--opt" is the same as "--quick
--add-drop-table --add-locks --extended-insert --lock-tables", the
latter doing the locking necessary for data consistency.

Ciao,
  Martin
-- 
Martin Ramsch <m.ramsch@stripped> <URL: http://home.pages.de/~ramsch/ >
PGP KeyID=0xE8EF4F75 FiPr=52 44 5E F3 B0 B1 38 26  E4 EC 80 58 7B 31 3A D7
Thread
Approach to database backup??Joel Fowler12 Jul
  • Approach to database backup??sinisa13 Jul
    • Re: Approach to database backup??Ed Carp13 Jul
      • Re: Approach to database backup??sinisa13 Jul
        • Re: Approach to database backup??Martin Ramsch13 Jul
        • Re: Approach to database backup??Ed Carp13 Jul
          • Re: Approach to database backup??Paul DuBois13 Jul
          • Re: Approach to database backup??Ronald Beck13 Jul