We are pleased to announce the release of Zmanda Recovery Manager (ZRM) Community Edition 3.0 (Beta). This release features support for parallel logical backups as an additional full backup method, which is made possible by integrating with the mydumper open source project.  This backup method represents a faster, scalable way to backup large databases.  The mysqldump (single threaded logical backup) support is still available for backing up stored procedures/routines.  ZRM Community Edition allows you to create multiple backup sets with different backup methods and policies; so, now you can do MySQL database backups with mydumper, as well as mysqldump in the same server.

We have also made many additional improvements and bug fixes since our earlier 2.2 release. We currently

Normal 0 false false false EN-US X-NONE X-NONE

As we continue to see MySQL being implemented in bigger and more challenging environments, we are working to ensure Zmanda Recovery Manager for MySQL (ZRM) matches this growth and provides a comprehensive, scalable backup management solution for MySQL that can easily integrate into any network backup infrastructure.

The latest release of ZRM for MySQL is a significant next step, bringing disk space and network usage optimization and enhanced backup reporting, along with simplified management to help configure backups quickly and intelligently.   Additionally, ZRM for MySQL 3.5 now supports backup of MySQL Enterprise Edition, MySQL Community Edition, SkySQL, MariaDB, and MySQL databases running on latest versions of Red Hat Enterprise Linux, CentOS, Debian,

As MySQL continues to grow (as a technology and as an ecosystem) the need and importance of creating and deploying robust MySQL backup solutions grows as well. In many circles Zmanda is known as “The MySQL Backup Company”. While we provide backup of a wide variety of environments, we gladly take the label of backing up the most popular open source database in the world, especially as we kick off our presence at the 2012 MySQL Conference.

Here are some of the updates to our MySQL backup technologies that we are announcing at the conference:

Announcing Zmanda Recovery Manager 3.4

We have updated the popular Zmanda Recovery Manager (ZRM) for MySQL product for scalability.

We are adding support for Asia Pacific (Tokyo) Region in Zmanda Cloud Backup (ZCB). This is the fifth worldwide location supported by ZCB.

This support provides faster uploads for ZCB users in Japan. Throughput will be significantly higher because of less hops along the way and very high bandwidth connections typically available in Japan. Overall processing will be faster because of lower latency (expected to be single digit millisecond latency for most end users in Japan).

Cloud Backup to Three Continents Now Includes Japan

This support enables users to ensure that their data does not leave Japan, e.g. if required for

Setting up of a good backup and recovery strategy is crucial for any serious MySQL implementation. This strategy can vary from site to site based on various factors including size of the database, rate of change, security needs, retention and other compliance policy etc. In general, it is also required from MySQL DBAs to have least possible impact on usability and performance of the database at the time of backup - i.e MySQL and its dependent applications should remain hot during backup.

Join MySQL backup experts from Zmanda for two webinars dedicated to hot backup of MySQL:

MySQL Backup Essentials: In this webinar, we will go over best practices for backing up live MySQL databases. We will also cover Zmanda Recovery Manager (ZRM) for MySQL product

If you are coming to this year’s Oracle OpenWorld 2010, please do visit us at Booth #3824.

We will have our backup solution experts at the show to discuss any of your database or infrastructure backup needs.

When it comes to backing up various products offered by Oracle, we have several solutions:

• Amanda Enterprise: Backup solution for Oracle Enterprise Linux and Solaris based systems.
• Zmanda Oracle Agent: Backs up live Oracle databases to Amanda backup server - which can store backup archives on disks, tapes, or storage clouds.
• Zmanda Cloud

An increasing number of large MySQL applications, e.g. social networking and SaaS back-ends, use a distributed MySQL architecture. MySQL data is distributed logically or heuristically on multiple, and in some cases thousands of, real or virtual servers. Backing up such large and dynamic environments presents its own complexities.

In this blog, we will use the cluster terminology - but we do not imply that NDB Cluster storage engine is being used for MySQL. Most implementations use InnoDB for data and MyISAM for dictionary. Typical architecture for such applications uses Database Sharding - i.e. shared-nothing partitioning of data across similarly configured nodes.

In most sharded environments, high availability is built-in - i.e. the cluster can continue to answer the queries and commit the transactions of all users in face of a node failure. This is typically accomplished either by

If you are running your MySQL databases on the Amazon EC2 compute cloud, Zmanda Recovery Manager (ZRM) for MySQL can perform fast full backups of these databases by using Elastic Block Store (EBS) Snapshots. ZRM takes only a momentary read lock on the MySQL database during the creation of the snapshot, in order to ensure consistency of the backed up database archive. MySQL Backups using Amazon EBS snapshots are differential backups, meaning that only the blocks that have changed since your last full backup (via EBS snapshot) will be saved. For example, if you have a database with 100 GBs of data, but only 5 GBs of data has changed since your last snapshot, only the 5 additional GBs of snapshot data will be stored back to Amazon S3 during the current full backup run.

ZRM automatically

Last week we had a lively panel discussion moderated by Dave Nielsen, founder of CloudCamp, with leading experts in cloud computing on the panel: Chander Kant (CEO, Zmanda) & Michael Crandell (CEO, RightScale). Chander and Michael shared their insights into how their customers are using cloud computing and achieving new levels of reliability and recoverability. Here is a video archive of the panel. 

This panel discusses how you can migrate your apps and data to the cloud in a way that’s affordable and reliable and how to integrate the cloud into your IT strategy. Also hear about real-world examples of companies using the cloud for data backup and recovery and understand the hurdles to moving to the cloud, and how you can overcome them.

Today we increased price for the Amanda Enterprise Backup Server. The new price for our Standard subscription level is $500 per year. Our online store is a place to quickly checkout prices for all our products on a single page. This price increase was done in conjunction with release of Amanda Enterprise 3.0, which represents several man years of R&D on the backup server, including advanced media management such as D2D2T. Our subscription provides access to software and enterprise-class support.

Amanda Enterprise is used by businesses of all shapes and sizes. But a typical scenario is the following:

• Backup Server on Linux
• One tape library with one or two tape drives. Or VTL on a NAS device.
• A mix of Linux &

One of the questions that comes up often in the Backup world is “Why can’t I just write a script to do this myself!?”. Well, as a do-it-yourselfer myself, the answer is “Absolutely, a customized backup script can be written, and in fact, the first version of it won’t be that complicated to develop either”. However, a home-grown backup script can quickly become tedious to enhance and maintain.

Lets look at the progression of events following a decision made by a system administrator or a DBA to develop their own backup scripts. Lets take the example of Joe, a MySQL Database Administrator at an e-commerce company SuperWidgets:

1. January: SuperWidgets has been around for one year, and sales of their super widgets have been increasing. The CEO of SuperWidgets, Mary, has faced serious consequences of

Today Sun announced the Sun Cloud, including its Sun Cloud Storage Service at CommunityOne East in New York. We announced our partnership with Sun on integrating all our three products: Amanda Enterprise, Zmanda Recovery Manager (ZRM) for MySQL and Zmanda Cloud Backup with Sun Cloud. In near future, our customers will be able to chose between Sun Cloud Storage or Amazon S3 as the destination of their backup archives. Also, users running critical application on the Sun Cloud Compute Service will be able to protect their data using Zmanda’s products.

Of particular interest to us is

In my previous blog on Cloud Backup, I wrote about the solutions we offer to backup to the Storage Cloud (e.g. Amazon S3). In this blog I will talk about backup of cloud, i.e. backup of your applications running on a Compute Cloud (e.g. Amazon EC2).

Let’s say you are migrating some on-premises applications (e.g. a customer facing enterprise app), which are currently being backed up to a tape library, to the cloud (fig 1).

Clouds don’t have a notion of a local tape library. So, your current backup solution will likely not work after this migration.

So, where do you backup? Note that Compute Cloud vendors do not offer automatic backups. While they may offer storage

This week Zmanda was invited to participate in the launch of OpenSolaris 2008.11. In his interview Chander Kant, CEO of Zmanda, explained why OpenSolaris is a big step forward from backup and recovery perspective both as a data source for backup and as a repository for backup images.

The advanced snapshot capabilities of ZFS enables fast and scalable backups for today’s most demanding workloads for servers and easy to use data protection for workstations. For example, the new Time Slider feature in OpenSolaris provides an automatic way to backup your data on the local disk with intuitive browsing and recovering of files from snapshots using the GNOME file manager. That is great, but what if you loose your local disk?

We released  ZRM for MySQL 2.1 Community Edition  today.  ZRM 2.1 includes the ability to treat snapshots as backup images. ZRM has supported backup of MySQL databases using storage snapshots using a plugin interface.  LVM (Logical Volume Manager) and Solaris ZFS snapshots are supported plugins in the ZRM Community Edition.
MySQL administrator can perform regular backups (backup images are stored in the ZRM server) or quick backups (snapshots acting as backup images). Quick backups have smaller backup windows and do not consume network bandwidth.  When MySQL database is stored on one or more ZFS filesystems, users can do multiple quick backups in a day (even once every hour) and convert one quick backup

In past few quarters Zmanda has been growing at a break-neck pace. This has transformed us in many different ways. In the past 12 months, we have almost quadrupled our customer base (which is now in 40 countries!), introduced our third product line (Zmanda Internet Backup) and built new relationships with some of the leading IT infrastructure providers in the world.

These changes merit a fresh introduction. Some of you have openly wondered about who we are. Well, here is your chance to hear directly from us. Join us for a webinar on December 17th at 10AM (Pacific Time), titled:

Today Sun announced the new 7000 line (aka Amber Road) of open storage appliances. Amber Road runs OpenSolaris and ZFS on industry-standard x86 hardware and includes innovative management software developed by Sun’s FISHworks (Fully Integrated Software and Hardware) group.

Our engineers worked along with Sun’s technologists on Amber Road in Sun’s labs for past few weeks, and today we are announcing support for Amber Road with both of our products Amanda Enterprise and Zmanda Recovery Manager for MySQL.

Amber Road is another example of innovation and value created by combination of open source and open systems. Combine  Amber Road with Zmanda’s open source backup products

Today we released version 3.0 of Zmanda Recovery Manger for MySQL. Here are the highlights of the release.

The new version of ZRM supports Zmanda Management Console (ZMC) running on 32- and 64-bit Ubuntu and Debian. We received quite a few requests for providing such support in the past.

In addition to Linux and Solaris, the ZRM server can now run on Windows. We supported logical and VSS-based backup for MySQL on Windows for a long time, but sometimes it was a challenge to introduce ZRM running on Linux/Solaris to all-Windows shops. Based on feedback from customers, prospects and from our partner MySQL, we have developed the version of ZRM that can protect MySQL in all-Windows environments.

We expanded the number of supported snapshot technologies by adding EMC CLARiiON SnapView to the list. This mid-range storage array

This month’s (September 2008) edition of Linux Journal has an in-depth review of Zmanda Recovery Manager for MySQL (written by Alolita Sharma a veteran of Open Source). Oh, and we made it on the cover as well! If you are browsing Magazines section of your local bookstore, do look us up..

Today Sun announced release of X4540 Open Storage server (a.k.a Thor). We were fortunate to get early access to Thor to certify Amanda Enterprise and Zmanda Recovery Manager (ZRM) for MySQL. Both solutions are optimized for backing up to disk, are already certified with Solaris 10, and leverage capabilities of ZFS. So it made perfect sense to certify them on Thor, effectively creating a high-performance and yet relatively inexpensive backup appliance.

The unit we were using is powered by 8 CPUs operating at 2300 MHz and provides 48 SATA drives with total capacity close to 50TB in 4U enclosure. That is good packing; a typical EMC unit with so much capacity will take the whole rack.

Here are my slides used for presentation at Red Hat Summit in Boston last week:

Zmanda: Open Source Backup (.odp open office format, 1.7MB)

The Red Hat Summit started today here in Boston. Based on the evening reception today, it is shaping up to be a pretty good show. I will be speaking at the show on Thursday, June 19, 2008 at 11:30 AM eastern time. I will discuss current state of open source backup as well as where things are headed. We also have a booth located towards the right side of the exhibit floor (by small meeting rooms). We are demonstrating Amanda as well as ZRM for MySQL. Do stop by if you are coming to the show!
adobe cs2 download photo shop Download Adobe Acrobat 7 MAC
oem software adobe
After

MySQL Quickpolls might be insightful for people who develop products and services for MySQL. Recently I was looking again at “How do you backup your production database” poll. To interpret the results, I wanted to know who are the people answering that and other Quickpolls. Are they the DBAs responsible for running MySQL in production or the developers writing applications that use MySQL? For a backup guy like me knowing that makes a difference.

Every Quickpoll gets a time stamp when opened and tells how many people answered the poll. It occurred to me that the normalized number of people (MySQL polls run for different periods of time) answering each poll could give me some insight. The graph below shows the daily number of people answering each poll in the last 24 months.

For many MySQL implementations scalability is a crucial requirement. Scaling on various dimensions: Size, Performance, Cost and DBA-Stress-Level.

While several factors impact the scalability of the database, underlying storage probably has the highest impact. You need to make sure that the storage will fill up the buffers fast enough to keep queries happy, and acknowledge the writes fast enough to keep transactions happy. You need to make sure that you can keep growing the available storage as your database grows - MySQL databases are particularly prone to collect more and more data. You also need to make sure that maintenance tasks such as backup, cloning, and application testing will scale gracefully with the size of your database.

Storage systems from NetApp are a great choice when designing for MySQL scalability. Administrators can expand

Storage Snapshots are excellent tools in arsenal of a system administrator to create quick and consistent backups of their databases and applications. Snapshot is a “picture” of a filesystem at a point-in-time. In most modern snapshot implementations, this “picture” is not a full copy of the data, but rather a set of pointers to the data.

Here is a list of current industry leading snapshot technologies:

• LVM Snapshots: Snapshot capability built into the Linux Volume Manager (LVM) - the default option on a Linux system.

• ZFS Snapshots: Snapshot capability built into the ZFS filesystem on Solaris and OpenSolaris

• NetApp SnapShots: A feature of the WAFL® (Write Anywhere File Layout) filesystem

• Windows VSS: Volume Shadow Copy Service from Microsoft

MySQL databases are increasingly used by high volume, high transaction applications
that support businesses running full throttle 24-hours a day, seven days a week.
Backup and recovery operations need to be conducted in such as way that is non-disruptive
to users and applications. The latest release of Zmanda Recovery Manager (ZRM) 2.2 provides
Continuous Data Protection (CDP) as well as instant point-in-time recovery for MySQL.
In this webinar, we will demonstrate the latest ZRM enhancements so that you can use ZRM
to build a robust, flexible, and easy to use backup and recovery solution.

When: Thursday May 29, 2008, 10:00am Pacific / 1:00pm Eastern

Ask any DBA what are his top priorities for backup of MySQL. Chances are that hot backup and recovery to a specific point-in-time (or transaction) will be on top of everybody?s list.

The recovery to any point-in-time has been always an ultimate goal for data protection. Traditional backup solutions allow recovering only to a point in time when the last backup took place, e.g. last night. A lot of new data could be created and lost since that last backup. That is why in the last several years many vendors have been working on Continuous Data Protection (CDP).

Storage Networking Industry Association (SNIA) defines Continuous Data Protection (CDP) as “a class of mechanisms that continuously capture or track data modifications enabling recovery to previous points in time”.

Final slides from keynote delivered this morning at the MySQL user conference. Topic was protecting live MySQL databases.

(Slides render well in both OpenOffice and PowerPoint)

You have to have been living under a rock, if you did not know that today is the first day of MySQL Users’ Conference and Expo. We at Zmanda are so proud and privileged to have been awarded the “Partner of The Year”. The award is very meaningful to our vision of Simplified, Easy to use, commercial Open Source Backup and Recovery. We appreciate the award and are committed to making the life of the MySQL DBA hassle free. We have had a ton of visitors from all walks of MySQL user community talk to us today. Its fascinating to talk to customer and prospects on how they leverage the power of MySQL. To learn more about how Zmanda provides the Best in Class Backup and Recovery solution for MySQL, you can attend Zmanda’s sessions at the MySQL Conference & Expo include:
What: “Radically Simple