Backups/recovery procedures for MySQL are very simple, and efficient.
The approach I take, is to
- Implement a replicated dual master
- Flush mysql db logs
- Use mysqldump <db> | gzip -c > <db>.sql.gz at a quiet time
- Copy mysql logs
This is essentially, the same process one would use with oracle.
----- Original Message -----
Sent: Thursday, July 31, 2003 10:24 PM
Subject: Backup conventions
> Hi, I'm a new user of MySQL on Linux.
> I have been an Oracle DBA; and know that anyone familiar with Oracle takes
> backup procedures very seriously....
> Anyone have recommendations for nightly backup procedures for MySQL
> (transactional) databases? The literature seems a little ambiguous on
> I did 'turn on' the general, binary and error logs. Does anyone shut down
> the MySQL daemon regularly? Anyone use mysqldump, or do folks simply use
> file system backup? We have tons of databases and tons of tables, so I'm
> not really considering the lock/flush procedure on tables...
> Any suggestions?
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> The information in this e-mail and any attached files is confidential.
> It is intended solely for the use of the addressee.
> Any unauthorised disclosure or use is prohibited.
> If you are not the intended recipient of the message,
> please notify the sender immediately and do not disclose the contents
> to any other person, use it for any purpose, or store or copy the
> information in any medium.
> This message has been scanned for viruses and dangerous content by
> MailScanner, http://www.mailscanner.info, and is believed to be clean.
This message has been scanned for viruses and dangerous content by
MailScanner, http://www.mailscanner.info, and is believed to be clean.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql