The role of data stored in MySQL database in today’s world is already known - it powers business and mission critical apps. Protecting this data is of utmost important to any enterprise. Before you actually have a backup in place, that are some very important things to think about the backup implementation. Like for instance, how soon would you want your data recovered after a user or system error? This article provides an indepth analysis about the basics of what needs to be considered while planning a Backup and Recovery solution for your MySQL database.
Archive for August, 2007
Zmanda’s MySQL Backup and Recovery Solution is the only comprehensive backup solution that addresses the unique needs of MySQL databases — such as multiple database storage engines. Zmanda Recovery Manager (ZRM) for MySQL now features graphical tools to simplify the process of protecting MySQL data.
This free presentation from experts in open-source backup and recovery of MySQL will demonstrate Zmanda Management Console for ZRM , which is a web based service integrated with Zmanda Network. It provides management and visualization tools for defining all backup activities of a MySQL DBA:
- what to backup, e.g. all databases or just the selected tables
- where to store the backup images
- when to perform backups, e.g. schedule daily, weekly or monthly full and incremental backups
Chander Kant, CEO and Co-Founder of Zmanda
Paddy Sreenivasan,VP of Engineering and Co-Founder of Zmanda
Zmanda Management Console for MySQL Backup web presentation.
Wednesday, August 22, 2007, 10:00 am PDT, 1:00 pm EDT, 17:00 GMT
The presentation will be approximately 45 minutes long followed by Q&A.
One of the candidates for a marketing position (btw, we are looking for a very technical marketing talent, drop me a line at dj at zmanda dot com) asked me if Zmanda wants to change the world. The way I see it, our job is just opposite to changing the world. We want to keep the world the way it was. If your hardware dies or a user drops a table, we give you the ability to go back in time and to recover your file with Amanda Enterprise or your MySQL database with Zmanda Recovery Manager (ZRM).
How do we actually accomplish going back in time? Are we talking here about super-expensive and complicated Continuous Data Protection (CDP) technologies? Our solution delivers the same result, but without the cost and complexity of CDP. ZRM incremental backups result in a copy of the MySQL binary log being flushed to disk. This log can be used to restore the database to its original condition in any point in time between two valid backups. Wouldn’t it be wonderful if you could go back in time and pinpoint the exact time or the transaction to which you want to restore your database? We provided this capability via the command line interface before, but the recently released ZRM 2.0 makes it very easy to identify the Recovery Point Objective, right in the Management Console, by way of the Database Events Analyzer.
The Database Event Analyzer allows you to select a binary log and view its contents. The date and time of all database activities and events are shown as individual records. You can easily scroll through the entries. Of course, there may be tens of thousands of entries or more in the log. Using Google-like search syntax you can easily query for events and actions to help you locate specific items to identify activity that impacted or even damaged your database. Your Recovery Point Objective could be very specific — down to the transaction level. You can even set the Recovery Point right from the log analyzer making going back in time and recovering the database very simple.
Here is a short (7 minutes) demo of Zmanda Management Console for MySQL backup.