ZRM for MySQL Cluster Edition, released during MySQL users conference last month, provides non-blocking backup and recovery for MySQL cluster databases. In addition to backup and recovery for MySQL clusters, the cluster edition also supports online backup and recovery of other MySQL storage engines such as MyISAM, InnoDB. Most applications using MySQL Clusters also store data in other storage engines. The Cluster edition provides a common user interface for backing and recovering applications that use multiple MySQL storage engines.
Archive for May, 2007
Red Hat Exchange went live minutes ago. We at Zmanda are thrilled to be one of the RHX launch partners: Alfresco, CentricCRM, Compiere, EnterpriseDB, Groundwork, Jaspersoft, Jive, MySQL, Pentaho, Scalix, SugarCRM, Zenoss, Zimbra and Zmanda. Congratulations to Matt Mattox and rest of RHX team at Red Hat.
The Amanda core team is pleased to announce the release of Amanda 2.5.2.
Thanks to everyone who reported bugs in the beta release and submitted patches.
Amanda 2.5.2 packages for Linux and Windows are available in Zmanda downloads page.
Amanda 2.5.2 feature list, documentation and man pages are available in Amanda wiki.
If you have Amanda questions or in general, backup/recovery questions, please use Amanda forums. Amanda developers and users provide answers when possible.
If you are interested in Enterprise version of Amanda, take a look at Zmanda Network (free registration) or contact email@example.com
The MySQL User’s Conference provides very fertile environment for new ideas. For example, last year we came to the conference with a conviction to build a MySQL agent for our Amanda Enterprise backup and recovery software. However, after talking to many MySQL users about their backup needs we got convinced that stand-alone solution optimized for MySQL DBAs was a better way to go, and that is how Zmanda Recovery Manager for MySQL was conceived.
This year we received a lot of insightful feedback and suggestions from MySQL users and our customers. 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 DBAs 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.
Our engineering is already looking how to implement these and many other ideas. Tell us about your backup requirements for MySQL by posting on our forums