1 / 21

Radically Simple Backup & Recovery for Live MySQL

Radically Simple Backup & Recovery for Live MySQL. Chander Kant CEO Zmanda www.zmanda.com. MySQL Partner of the Year !. Customer Facing Data (CFD). As important as CRM and Financial Data For many companies loss of CFD implies catastrophe Lost revenues, lost customers and lost reputation

nonnie
Download Presentation

Radically Simple Backup & Recovery for Live MySQL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Radically Simple Backup & Recovery for Live MySQL Chander Kant CEO Zmanda www.zmanda.com MySQL Partner of the Year !

  2. Customer Facing Data (CFD) • As important as CRM and Financial Data • For many companies loss of CFD implies catastrophe • Lost revenues, lost customers and lost reputation • Today’s Data Protection Challenge • Break neck rate of change • MySQL is the database of choice for CFD • Metadata is very vital as well

  3. Backup: Most important task for a MySQL DBA • There is no quicker way to get fired than to lose business data • Backup & recovery – the first step to data protection

  4. “Oops!” “I forgot to add a “where” clause and emptied the entire thing!” “I am the one who wrote the backup script so I went to grab the backup for yesterday. Yup, you know it. There wasn’t one. The backup stopped working back on July 3rd! Ouch.” “Hi, I lost MySQL server and I didn’t do backups. What can I do?” “… the server on which my blog is being hosted was being changed and for some reason during the importing the MySQL databases disappeared ” “Does the backup through MySQL Administrator have to be saved in a certain way to allow migration to a new box?” “Lesson learned – always backup regularly!”

  5. Top considerations for a MySQL backup solution • Performance • Impact of the Backup Window • How fast your restore needs to be? (RTO) • How precise your restore needs to be? (RPO) • Scale Up • 10GB -> 100GB -> 1TB -> ?? • Organic growth Longer retention • Scale Out • Wiki, Forums, Web registration database, Sugar, Alfresco, ….. • Multiple locations • Security • Aren’t you backing up your crown jewels?

  6. Backup needs to match MySQL’s flexibility • Today & Future • MyISAM, InnoDB, Falcon … • Replication • Slave pauses replication -> Backup on slave -> Resume replication • MySQL Cluster • Restores should hide all the complexity

  7. Our design philosophy "Any darn fool can make something complex; it takes a genius to make something simple.“ - Albert Einstein

  8. As easy as: What, Where, When and How

  9. Anytime. Anywhere.

  10. Zmanda Recovery Manager (ZRM) for MySQL • Recover database easily to any point-in-time • Centralized global backup management • Schedule full and incremental, logical or raw, backups of MySQL database • Perform backup that is the best match for the specific MySQL configuration • Blazing fast snapshot-based backup • Reporting and Monitoring • Continuous Data Protection (CDP) for MySQL http://www.mysql.com/zrm

  11. Remote storage grid as a destination for backups • Keep copy of data off-site yet online with storage grid, e.g. Amazon S3 • Pay for only what you use (bandwidth and disk capacity) • Backup data is always available, anytime, anywhere • You can have the risk profile of Amazon “We think users should seriously consider adopting such hybrid [backup & online storage] approaches to provide layered, efficient data protection.” - John Webster, Analyst, Illuminata

  12. Infrastructure for scalability Scenario: • 100+GB of database growing into Terabytes • 24x7 application (i.e. no backup window) • Active OLTP workload • Need ability to restore to specific database event Solution: • Storage Snapshot + MySQL Logs + Automated Point-and-Click Restore

  13. Solaris 10 x86 • ZFS Snapshot • MySQL Enterprise 5.0 • ZRM 2.1 • Raw copy speed 500 GB/hr • Solaris 10 x86 • MySQL Enterprise 5.0 • ZFS Snapshots • ZRM 2.1 • Raw copy speed 500 GB/hr

  14. Snapshots – key considerations • Snapshots scale extremely well as database size grows • Need to be used carefully to ensure data consistency • Need to be integrated with log-based incremental backups

  15. Storage Snapshots • ZFS • NetApp • VxFS • LVM (Linux) • VSS (Windows)

  16. Recovery: Radically Simple. Precise. Click ! Restored ! 1 2

  17. Zmanda: Open Source Backup • Amanda: Most vibrant Open Source Backup community • More than 500,000 deployments • Open Formats + Open Standards + Open Source • Locking up your backup data in proprietary formats comes with a *huge* cost and pain • Zmanda Recovery Manager for MySQL extends our leadership in open source backup to the most popular open source database in the world Zmanda: Radically Simple Backup for Customer Facing Data

  18. Protected By Zmanda Manufacturing & Services Federal & Government Web and Media Research & Education Telecom and ISV

  19. Amazon Mechanical Turk: Protected by Zmanda • mturk.com • On-demand scalable 24x7 workforce • Zmanda Recovery Manager provides backup for more than a dozen fleets of MySQL Servers • Backs up data to Amazon S3!

  20. Snapshot Camera Raffle … and the winner is !!!

  21. Date with Amanda! 

More Related