PDA

View Full Version : New ideas for backup of MySQL with ZRM



DJ
May 2nd, 2007, 05:31 PM
During MySQL Users Conference we received a lot of insightful feedback and suggestions from DBAs and our customers how to improve ZRM. Special thanks to MySQL engineering and product management for providing their perspective. Here are the major takeaways for us, the MySQL backup guys:
Back up the MySQL server configuration files when you do backup of the database -- that will simplify recovery to a different server or to the same server back in time.
Provide verification of backups - users have backups, but not so many users test their backups.
Predictive reporting will help. For example, based on historical data, alert the user that in 2 months he will start missing his backup window.
MySQL log analyzer to identify points of interest from backup & recovery perspective, e.g. pinpoint when a user dropped a table.
Auditing of MySQL backup operations, for example, alert the DBA that 2 of his recently installed MySQL servers don't have any backups
Bare metal recovery of MySQL server and databases

Please tell us what functionality would you like to see in ZRM for MySQL.
-------
Dmitri Joukovski from Zmanda

motin
May 22nd, 2007, 01:28 AM
All of the above ideas look rock solid to me!

My personal priority-rating of the above features:
1. Provide verification of backups - users have backups, but not so many users test their backups.
2. Back up the MySQL server configuration files when you do backup of the database -- that will simplify recovery to a different server or to the same server back in time.
3. MySQL log analyzer to identify points of interest from backup & recovery perspective, e.g. pinpoint when a user dropped a table.
4. Predictive reporting will help. For example, based on historical data, alert the user that in 2 months he will start missing his backup window.
5. Bare metal recovery of MySQL server and databases
6. Auditing of MySQL backup operations, for example, alert the DBA that 2 of his recently installed MySQL servers don't have any backups

I'd like to add:
* Safe easy restoration ("for dummies") - The possibility to perform point in time restoration of a single database (from a full backup) to a different database name - that is a restoration that doesn't overwrite the original database and does not shut down the mysql server.

Preferably, the command should be able to be performed on both incremental backup sets and logical ones and require two parameters: A database name and a time stamp, and result in the creation of a new database named database_TIMESTAMP alongside the existing databases containing the database information from the timestamp (or as close as possible if the backup set doesn't make use of binary logs) without ever having to overwrite the existing database nor shut down the mysql server.

I am working on writing a script for this (http://forums.zmanda.com/showthread.php?t=589), but am starting to believe that ZRM needs to implement this feature natively to make it possible.

alitvak
July 4th, 2007, 06:24 AM
One suggestion that is probably really easy to do would be to let user set backup all tables in database xyz except tables a1, a2, a3. It really would save me some time and trouble even though it sounds really simple.

paddy
July 6th, 2007, 11:07 AM
One suggestion that is probably really easy to do would be to let user set backup all tables in database xyz except tables a1, a2, a3. It really would save me some time and trouble even though it sounds really simple.


This functionality will be available as part of Zmanda Management Console (http://www.zmanda.com/blogs/?p=61)

Paddy