Zmanda Recovery Manager for MySQL: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
== What is Zmanda Recovery Manager for MySQL ==
'''Please see [[Zmanda Recovery Manager for MySQL Users Manual]] for release 1.1.3 and later releases
'''


Zmanda Recovery Manager for MySQL (MySQL ZRM) is a flexible and robust backup and recovery solution for MySQL server. It also provides users the capability to schedule and get report on the backup of MySQL Databases.
Zmanda Recovery Manager for MySQL (MySQL ZRM) is a flexible and robust backup and recovery solution for MySQL server. It also provides users the capability to schedule and get reports on the backup of MySQL Databases. MySQL ZRM has plugin interfaces that allow ZRM to be customized to the IT environment.


== [[What does MySQL ZRM run on?]] ==
MySQL ZRM supports backups of MySQL databases residing on the local server as well as remote servers. It does backup to  direct attach or SAN attached disk storage or NAS/SAN storage appliances. Following diagram shows a server running MySQL ZRM backing up 2 MySQL servers with multiple MySQL databases and the local MySQL server.


== [[I have questions/suggestions/bug fixes. How do I contact other users/developers? ]]==


== [[What can MySQL ZRM do?]] ==
[[Image:MySQL_ZRM.png|center]]


== [[What will be implemented in future releases?]] ==


== [[How do you install MySQL ZRM?]] ==
This manual discusses installation, configuration, backup, recovery and reporting features of MySQL ZRM.  This document was prepared for ZRM for MySQL release 1.1.3


== [[Do I need to make changes to MySQL database configuration?]] ==
# [[What does MySQL ZRM run on?]]
 
# [[I have questions/suggestions/bug fixes. How do I contact other users/developers? ]]
== [[How do I configure MySQL ZRM?]] ==
# [[What can MySQL ZRM do?]]
 
# [[What will be implemented in future releases?]]
== [[Finally, Can I do MySQL backups?]]==
# [[How do you install MySQL ZRM?]]
 
# [[Quick start example]]
== [[What information can be obtained from a backup report?]] ==
# [[Do I need to make changes to MySQL database configuration?]]
 
# [[How do I configure MySQL ZRM?]]
== [[How do I recover data when there is a failure or data loss?]] ==
# [[Finally, Can I do MySQL backups?]]
 
# [[Backups failed. What do I do?]]
== How did the MySQL ZRM do the job? ==
# [[Backup compression and encryption]]
 
# [[What information can be obtained from a backup report?]]
=== Did I use the correct method to backup? ===
# [[How do I recover data when there is a failure or data loss?]]
 
# [[How did the MySQL ZRM do the job?]]
The [[mysql-zrm-reporter]] tool provide backup statistics about the MySQL backup run.  It is a good idea to review the ''backup-time'', ''read-locks-time'', ''flush-logs-time'' and ''backup-size'' to determine whether the method used by MySQL ZRM is appropriate for the backup set.  The predefined ''backup-performance-info'' report is a useful tool to tune backup process or switch to a different backup method.
# [[How to create custom plugins for MySQL ZRM?]]
 
# [[How do I tune MySQL backup performance?]]
An example command displaying backup size and backup time for a backup set ''backupSet2'':
 
# mysql-zrm-reporter  --fields backup-date,backup-level,backup-size,backup-time \
  --where backup-set=backupSet2
***************************************************************************
    backup-set  backup-date    backup-level backup-size    backup-time
****************************************************************************
    backupSet2  20060829140723  0            58MB            15 seconds.
    backupSet2  20060829140819  0            59MB            26 seconds.
    backupSet2  20060829141001  0            78MB            40 seconds.
 
Using [[mysql-zrm-reporter]] tool, you can figure out what backup method was used to do the backup (''backup-method-info'' report). You can override the backup method by setting backup parameters - ''replication'', ''logical-backup'', ''lvm-snapshot'' in MySQL ZRM configuration for the backup set.
 
=== Can I make backups more efficient? ===
 
The time taken to do a backup (backup window) and backup image size depends on various factors:
 
* Backup method used for each database - logical backups, raw backups, lvm snapshot, MySQL replication
* Backup level for the backup set
* Size of the database
* Database activity - read-only, read/write ratio
* Database transaction rates
* Recovery requirements - how often do you recover data? What is the reason for data recovery?
 
Use [[mysql-zrm-reporter]] tool and mysql-zrm logs to analyze the backups. The ''backup-performance-info'' report is a good starting point to analyze the bottlenecks in the backup strategy. It is possible to change all the MySQL backup parameters using the configuration file.  Often, it takes multiple backup runs to arrive at a good parameters for a backup set.
 
Example: Backup performance report
 
# /usr/bin/mysql-zrm-reporter --where backup-set=backupSet1 --show backup-performance-info
backup_set  backup_date    backup_level backup_size backup_time  read_locks_time  flush_logs_time
-------------------------------------------------------------------------------------------------
backupSet1  20060909100021 0            4.26 MB    00:00:06    00:00:03        00:00:00
backupSet1  20060909100123 0            4.26 MB    00:00:03    00:00:02        00:00:00
backupSet1  20060909100300 0            4.26 MB    00:00:03    00:00:02        00:00:00

Latest revision as of 22:33, 30 January 2007

Please see Zmanda Recovery Manager for MySQL Users Manual for release 1.1.3 and later releases

Zmanda Recovery Manager for MySQL (MySQL ZRM) is a flexible and robust backup and recovery solution for MySQL server. It also provides users the capability to schedule and get reports on the backup of MySQL Databases. MySQL ZRM has plugin interfaces that allow ZRM to be customized to the IT environment.

MySQL ZRM supports backups of MySQL databases residing on the local server as well as remote servers. It does backup to direct attach or SAN attached disk storage or NAS/SAN storage appliances. Following diagram shows a server running MySQL ZRM backing up 2 MySQL servers with multiple MySQL databases and the local MySQL server.



This manual discusses installation, configuration, backup, recovery and reporting features of MySQL ZRM. This document was prepared for ZRM for MySQL release 1.1.3

  1. What does MySQL ZRM run on?
  2. I have questions/suggestions/bug fixes. How do I contact other users/developers?
  3. What can MySQL ZRM do?
  4. What will be implemented in future releases?
  5. How do you install MySQL ZRM?
  6. Quick start example
  7. Do I need to make changes to MySQL database configuration?
  8. How do I configure MySQL ZRM?
  9. Finally, Can I do MySQL backups?
  10. Backups failed. What do I do?
  11. Backup compression and encryption
  12. What information can be obtained from a backup report?
  13. How do I recover data when there is a failure or data loss?
  14. How did the MySQL ZRM do the job?
  15. How to create custom plugins for MySQL ZRM?
  16. How do I tune MySQL backup performance?
Retrieved from ‘http://wiki.zmanda.com/index.php?title=Zmanda_Recovery_Manager_for_MySQL&oldid=3981’