List:General Discussion« Previous MessageNext Message »
From:mark carson Date:June 7 2011 6:07am
Subject:Re: Doubt regarding Mysqlsump
View as plain text  
Hi

We use the --single-transaction switch thinking it does less locking or waiting
for a required table lock. You then get a snapshot without stopping.

Subject should have included the word 'hot'? Looking forward to other suggestions.

Mark

On 2011/06/07 08:00, Adarsh Sharma wrote:
> Dear all,
> 
> Is it possible to take backups of a table or complete database without stopping
> the application that continuously inserts and select data from the tables.
> 
> For taking complete backup of a database I follow the below steps :-
> 
> 1. First stop the application that insert & modifies tables.
> 2. Mysqldump command to backup the tables.
> 3. After complete backup , start the application.
> 
> I know Mysql-Replication helps a lot to solve this issue but I have not any
> extra server to configure it.
> 
> So , Can I solve this issue without Replication so that I don't need to stop my
> application & I must have consistent backups too.
> 
> Please note that size of databases may be more than 100GB
> 
> 
> Thanks
> 

-- 
Mark Carson
Managing
Integrated Product Intelligence CC (CK95/35630/23)
EMail : mcarson@stripped/ (secondary:mcarson@stripped)
Physical Address : 34 Spanish Galliard, Mooikloof, Pretoria, South Africa
snailmail : P.O. Box 36095 Menlo Park 0102, South Africa
Tel. +27 12 996 1193/1815 Fax : +27 86 672 7012 Cell : +27 83 260 8515


This e-mail may contain PRIVILEGED AND/OR CONFIDENTIAL INFORMATION intended
only for use of the addressee. If you are not the addressee, or the person
responsible for delivering it to the person addressed, you may not copy or
deliver this to anyone else. If you received this e-mail by mistake, please
do not make use of it, nor disclose it's contents to anyone. Thank you for
notifying us immediately by return e-mail or telephone. INFORMATION PROVIDED
IN THIS ELECTRONIC MAIL IS PROVIDED "AS IS" WITHOUT WARRANTY REPRESENTATION
OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO CONDITIONS OR OTHER TERMS OF MERCHANTABILITY AND/OR FITNESS FOR A
PARTICULAR PURPOSE. THE USER ASSUMES THE ENTIRE RISK AS TO THE ACCURACY AND
THE USE OF THIS DOCUMENT.

Thread
Doubt regarding MysqlsumpAdarsh Sharma7 Jun
  • Re: Doubt regarding MysqlsumpClaudio Nanni7 Jun
    • Re: Doubt regarding MysqlsumpJohan De Meersman7 Jun
      • Re: Doubt regarding MysqlsumpAdarsh Sharma7 Jun
        • Re: Doubt regarding MysqlsumpJohan De Meersman7 Jun
          • Re: Doubt regarding MysqlsumpKaren Abgarian9 Jun
            • Re: Doubt regarding MysqlsumpJohan De Meersman9 Jun
              • Re: Doubt regarding MysqlsumpKaren Abgarian9 Jun
              • RE: Doubt regarding MysqlsumpJerry Schwartz9 Jun
                • RE: Doubt regarding MysqlsumpWm Mussatto9 Jun
                  • MySQL loses password?Tim Thorburn12 Jun
                    • Re: MySQL loses password?Johan De Meersman12 Jun
                      • Re: MySQL loses password?Tim Thorburn12 Jun
                        • Re: MySQL loses password?Claudio Nanni12 Jun
                          • Re: MySQL loses password?Tim Thorburn13 Jun
                            • Re: MySQL loses password?Claudio Nanni13 Jun
                            • Re: MySQL loses password?Andrew Moore13 Jun
  • Re: Doubt regarding MysqlsumpNilnandan Joshi7 Jun
    • Re: Doubt regarding MysqlsumpAdarsh Sharma7 Jun
  • Re: Doubt regarding Mysqlsumpmark carson7 Jun