Archive for the ‘LAMP’ Category

Sun/MySQL to resell Zmanda Recovery Manager for MySQL

Tuesday, March 18th, 2008

Today Sun and Zmanda announced our agreement to deliver a comprehensive, global data backup and recovery solution for MySQL Enterprise subscribers. Starting April 1st, MySQL Enterprise customers will be able to purchase ZRM for MySQL directly from Sun worldwide.

I think Zack’s comment in the press release captures the rationale for the deal:

“Protecting corporate data through effective backup and recovery is one of the most crucial tasks for a database administrator, and it can be a complex undertaking — especially for today’s large Web-scale applications,” said Zack Urlocker, VP of products, Sun Microsystems database group. “MySQL users have told us that global backup and recovery is very important to them, and we are thrilled that we can now offer ZRM for MySQL as an easy-to-use solution for protecting all of their MySQL data.”

Of course, at Zmanda we are thrilled as well. Sun’s sales channels will give us the opportunity to make MySQL Backups radically simple for ever increasing MySQL installations around the world.

Here is the full press release (sun.com)

Zmanda Recovery Manager 2.1 - Keep those MySQL Databases Zipping

Thursday, February 28th, 2008

Today we announced a significant enhancement to our Zmanda Recovery Manager (ZRM) for MySQL product. Here are major highlights of this new version (2.1):

End-to-end support for Solaris: We have had increasing number of requests from customers for supporting Solaris. While we always protected MySQL databases running on Solaris, we needed customers to run the ZRM core engine on a Linux box. Now we are able to run the ZRM core engine on Solaris itself. So a pure Solaris shop can use ZRM without getting a Linux server. The coinciding of this support with MySQL’s acquisition by Sun was not a planned thing :)

mysql snapshotEnhanced Snapshot support: One of the coolest features of ZRM is to be able to take advantage of underlying storage infrastructure whenever possible. Since version 1.0 of ZRM we have provided support for backing up MySQL using LVM on Linux. Now we are adding support for four major snapshot options: Windows Volume Shadow Services (VSS) snapshot, Network Appliance SnapManager, Veritas VxFS and Solaris ZFS. If your storage infrastructure supports any of these snapshot options, this will be the fastest way to backup your MySQL database - with zero impact on the application using the database. In fact, on Windows platform, ZRM 2.1 enables for the first time the capability of taking a fast raw backup of MySQL (using VSS). BTW, a crucial feature here is how ZRM uses snapshots for Restore. When a DBA requests a point-in-time restore, ZRM is intelligent enough to collate snapshot-based full backups with log-based incremental backups, to deliver the MySQL database in the precise state at requested point-in-time.

Global Management of MySQL databases: One key behavior we observe about MySQL databases is that they tend to propagate rapidly within organizations. Here at Zmanda, I can easily count close to 10 production MySQL databases, both inside and outside our firewall. Maintaining backups of multiple MySQL databases at a single repository tremendously reduces the complexity for DBAs. While we always had some form of remote backup capability, with ZRM 2.1 we now support centralized backup across all storage engines and across all operating systems. Our web based Zmanda Management Console allows this centralized management from anywhere, including from an iPhone!

Our goal is to make backup of live MySQL databases radically simple - enabling you to focus on your business applications.

Congratulations to Sun and MySQL

Wednesday, January 16th, 2008

Congratulations to Marten and team on Sun’s acquisition of MySQL today! This is a billion dollar stamp of approval on the importance of the LAMP stack. This also gives another strong backing to the business model which involves giving one’s software away for free to up to 99+% of users!

This announcement comes at an interesting time for Zmanda. Just last week we announced support for the Solaris platform for our Amanda Enterprise product line. With our industry leading MySQL backup solution, we now have full coverage of operating systems and database software from the new Sun!

A great day for open source software and business of open source software!

Amanda at IBM Partnerworld

Friday, April 27th, 2007

If you are visiting IBM Partnerworld in St. Louis next week, be sure to stop by at the “Blades in SMB” ped #309 in the IBM Systems and Technology Group Solutions Village. Amanda backup software will be in action on a IBM BladeCenter server system. From ibm.com:

Combining Linux with System x or BladeCenter servers makes it easier to build a flexible, cost-effective, secure IT environment to help stretch your IT budget and confidently execute your business objectives - even as conditions change.

Data Protection for the LAMP Economy

Monday, April 23rd, 2007

The value of data stored in LAMP applications is increasing at an exponential pace. Indeed, the LAMP stack fuels an economy of its own - with its own currency, lingo and players. While e-commerce is the clear and present evidence of the LAMP powered economy, the currency for this economy is by no means just monetary. Value is manifested in many factors other than financial gains: personal reputation and legacy, karma points, creativity etc. The LAMP stack fires up innovation by enabling new ideas - you can quickly and cost-effectively prototype a concept which other’s may find bizarre.

User generated content (UGC) is one key currency of the LAMP stack. UGC, even votes (ok, diggs) on other’s UGC store tangible and lasting value. While naming “You”, a proxy for UGC, the Time’s Person of the Year 2006, The Time magazine said: “It’s a story about community and collaboration on a scale never seen before. It’s about the many wresting power from the few and helping one another for nothing and how that will not only change the world, but also change the way the world changes.” With current trends UGC (most of which is stored in LAMP stacks) will continue to pack in increasing value for companies and communities around the world.

Since the cost of deploying applications on the LAMP stack tends to be very low, sometimes their importance to the enterprise may not be perceived accurately. The LAMP stack moves the value of IT infrastructure to business data and applications, which is exactly where it should be (instead of costly underlying technology). The importance of protecting LAMP data can easily be gauged by looking at all LAMP based applications that you rely on. Whether you are using a vBulletin or phpBB based forum for your users, or SugarCRM for your sales force, or Mediawiki for your corporate wiki - loss of data in any of these instances will result in at least lost productivity, if not lost revenue and reputation.

The LAMP economy comes with its own set of challenges and hazards, e.g. crowdhacking, comment storms etc. Dealing with these challenges is especially challenging for IT managers since it is extremely hard to get scheduled downtime on LAMP applications which power a busy website. In addition, such an environment has its own requirements as far as point of time where data should be recovered to (aka Recovery Point Objective). For example, owner of a web based forum may want to recover their data to a point just before a rogue user created a login and started vandalizing the forum.

Several dynamics make data protection for LAMP based applications a more challenging problem than traditional environments. For one, the data stored within LAMP stacks in many cases does not have any physical record. E.g. nobody keeps a printout of all threads in a forum. So, if LAMP data is lost and cannot be recovered, you would simply need to live without that data - there is no way to recreate it from any physical records.

Data in LAMP applications is stored both in MySQL databases and filesystems (typically configuration data). LAMP applications have a tendency to scale out instead of scaling up. One application may be spread across multiple servers (either in form of MySQL Cluster, or simply independent aspects of application distributed on independent LAMP stacks). The application administrator has to take into account multiple servers and locations of their LAMP data while putting together a backup strategy. In such an environment, creating a point-in-time consistent backup is a challenging task.

Frequently, LAMP based applications are hosted at a service provider’s site, instead of a captive data center. This provides additional challenges (and opportunities) for data protection. You will need to carefully plan how the recovery for the whole stack and application will take place at a different location from your hosting provider (e.g. in a hurricane Katrina like situation). In many cases, administrators will need to backup their LAMP data remotely using a secure communication protocol. An interesting alternative here is to use a remote storage grid (e.g. Amazon S3 service) to do the backup of the LAMP applications. Why bother with local tape hardware (and all the idiosyncrasies of tapes), when your data is remote anyway.

It is imperative that today’s IT managers assess the value of data stored in their LAMP stack based applications. They need to architect a backup solution for their LAMP applications based on the impact on application performance, application availability, type of failures to recover from, and the cost of implementing the solution. Administrators need to pay attention to the data in all layers of the LAMP application in order to get a consistent data backup for the whole LAMP application stack.

Zmanda is at an interesting place when it comes to the LAMP stack. We use the LAMP stack in our own products - the new Zmanda Management Console is developed on it, and we are focused on making it simple to protect the value of LAMP application data. Our open source projects extensively use wiki and forums for community collaboration and communication. Our products provide data protection for the entire LAMP stack. Amanda is the leading backup solution for a network of Linux filesystems. Our Zmanda Recover Manager for MySQL product is one of the most popular solutions to backup MySQL databases.

Adspace Mall DisplayOne extensive user of the LAMP stack is Adspace Networks - the largest in-mall digital audio/visual network in the United States. LAMP data is not just displayed on a small browser window - Adspace shows its customer’s advertising artwork on sixty inch plasma displays mounted in 8 foot tall enclosures! Using Adspace’s LAMP based applications, retailers can create new campaigns and upload advertising artwork - which then shows up on the huge screens. LAMP stack enabled Adspace to create and deploy this application in a very aggressive timeframe. Wide availability of LAMP consultants and hosting providers was seen as a big plus while deciding the application framework. Adspace needed a solution which could backup their data more frequently than the traditional nightly backup (due to high value of the customer data). While their applications are deployed at a remote hosting site, they wanted to keep the backup data on their own site. Adspace deployed Zmanda Recovery Manager for MySQL to backup their LAMP data. This solution enabled them to create a consolidated backup solution with point-in-time recovery capability, without having to spend time and expertise in building and architecting a LAMP backup solution.

While Google and Yahoo are the most likely destinations if you want to search for something, if you want to discover stuff one of the coolest destinations is StumbleUpon. StumbleUpon is helping more than 2.1 million users discover and share interesting websites. “Collaborative Opinions” is the currency that StumbleUpon trades in. LAMP stack stores this extremely valuable data of users, their preferences and friends, and all the websites they discover. StumbleUpon stumbled upon Zmanda’s LAMP backup solutions when they were looking to reduce the time and complexity of backing up this data, which is increasing by the minute. The rapid growth of their data mandated incremental backup of their database - full backup every time was just too time-consuming. Today they use Zmanda Recovery Manager for MySQL to backup their database and manage the backed up archives. StumbleUpon implemented Zmanda’s backup solution for its simplicity and effectiveness for their exact needs.

Protecting the LAMP Stack