\\
{page-title}{excerpt}Zmanda adds a GUI to: mysqldump, Binlogs, and LVM Snapshots{excerpt}
[Zmanda|http://www.zmanda.com] the commercial effort behind the open source [Amanda|http://www.amanda.org/] Unix tape backup software make a backup product called [Zmanda Recovery Manager (ZRM) for MySQL|http://www.zmanda.com/zrm-mysql-enterprise.html].
Zmanda Recovery Manager (ZRM) 3.0 highlights the following features in their advertisements:
\\
# [Continuous Data Protection for Your MySQL Database|http://www.zmanda.com/zrm-mysql-enterprise.html#2]
Deep integration between ZRM, underlying storage and MySQL binary logs enables you to perform highly efficient CDP with almost instantaneous point-in-time recovery
# [Backup Live MySQL Databases Without Impacting Applications |http://www.zmanda.com/zrm-mysql-enterprise.html#3]\\
Perform hot backup of live MySQL by taking advantage of Linux LVM, Microsoft VSS, Solaris ZFS, Symantec VxFS, NetApp SnapManager, and EMC SnapView technologies.
# [Perform One-Click Point-In-Time Recovery|http://www.zmanda.com/zrm-mysql-enterprise.html#4]
ZRM provides unified point-in-time recovery for any type of backup method used
\\
h3. How Does Zmanda Recovery Manager (ZRM) Actually Work?
Zmanda Recovery Manager (ZRM) is a perl-based web utility used to manage the open source Amanda application. ZRM uses a variety of methods to extract data from MySQL and they are configurable at backup time. ZRM adds a GUI to all of the Legacy MySQL backup techniques and provides online backup using Online Volume Snapshots (e.g. LVM).
h4. *mysqldump & mysqlhotcopy*
Zmanda Recovery Manager (ZRM) uses [mysqldump|mysqldump] and [mysqlhotcopy][mysqlhotcopy|mysqlhotcopy]as an option.
[According to Zmanda|http://www.zmanda.com/backup-mysql.html]: "_Backups are done via_ *{_}mysqldump{_}{*}_, various snapshots,_{*}{_}mysqlhotcopy{_}* _or MySQL replication_."
\\
h4. Zmanda (ZRM) Online MySQL Backup
Zmanda Recovery Manager (ZRM) uses the [Volume Snapshot method|MySQL Volume Snapshot for Backup] for providing [Online backups of MySQL|TP:Categories of MySQL Backup Software] on Linux and Unix where available.
Zmanda Online Backup Availability
| *Linux MySQL Online Backups* \\ | Requires MySQL Data be Stored on an LVM Logical Volume and have Dedicated LVM Snapshot Storage \\ |
| *Windows MySQL Online Backups* \\ | No Not Available \\ |
| *Unix MySQL Online Backups* \\ | Requires Veritas File System for Snapshots \\ |
| *Network Attached Storage Online Bakcups* \\ | Supports Volume Snapshots using EMC Clarion and NetApp filers \\ |
h4. Zmanda Recovery Manager (ZRM) "Continuous Data Protection" for MySQL
Zmanda advertises a [continuous data protection offering for MySQL|http://www.zmanda.com/zmanda-announce-zrm22.html].
Zmanda use of the term "Continuous Data Protection" is very misleading. Zmanda does Not offer Continuous Data Protection ® for MySQL in any way like R1Soft or other CDP software vendors. Zmanda uses the term "Continuous Data Protection" to market it'sMySQL backups software. In the [Zmanda press release announcing Zmanda CDP,|http://www.zmanda.com/zmanda-announce-zrm22.html] Zmanda _seems_ to define it's implmentation of CDP as [Online Volume Snapshots,|MySQL Volume Snapshot for Backup] then goes on to elaborate about their use of [MySQL binary logs for backup and restore|TP:Binary Log Backups].
\\
*How Does Zmanda "CDP" for MySQL Work?*
We know very clearly Zmanda can do an Online backup of MySQL using Linux LVM, Veritas File System Snapshots, and the snapshot capability of Network Attached STorage devices like NetAPP and EMC. We also know Zmanda can copy MySQL binary logs or provide a GUI for [ibbackup|InnoDB ibbackup] (sold separately by Innobase). How this translates to Continuous Data Protection is unclear.
Continuous Data Protections is typically defined as either True CDP where SAN replication is used for 1-second playback and resolution OR a method of computing Deltas between scheduled backups in a near-COntinuous fashion using a device driver to track low level disk (Block Level) changes. Another attribute of Continuous Data Protection is the idea of Virtual Full Backup where each backup appears as a Full Backup even though only deltas are stored.
For more information on Continuous Data Protection see:
* [TP:Computing Deltas - near-Continuous (CDP)]
* [TP:Categories of Backup Software]
* [TP:Block Based Backup Technology]
* [TP:Backup Method - Virtual Full Backup]
* Wikipedia's Article's on CDP: [http://en.wikipedia.org/wiki/Near_Continuous_Backup], [http://en.wikipedia.org/wiki/Continuous_Data_Protection]\\
\\
| {color:#cc0000}Category{color}\\ | [Online|TP:Categories of MySQL Backup Software] IF LVM or other Volume Snapshots Available \\ |
| Archive Type | Disk or Tape \\ |
| MySQL Storage Engines Supported | All \\ |
| Supported O/S | All \\ |
| Binlog Backup & Restore | {color:#00cc00}Yes{color} \\ |
| {color:#000000}Zero Business Interruption (Online Backups){color} | {color:#000000}Yes{color} IF LVM or other Volume Snapshots Available |
| {color:#000000}Granular (Table Level) Restore{color} \\ | {color:#00cc00}Yes{color} |
| {color:#000000}Easy to Use Graphical User Interface{color} \\ | {color:#00cc00}Yes{color} |
| Complete Server Protection (Backup All Data or just MySQL?) \\ | {color:#00cc00}Yes with tar or dump{color} |
| Backup Type \\ | [Incremental|TP:Backup Method - Full Backup]\\ |
| {color:#cc3300}Backup Window Length{color} \\ | {color:#cc3300}Long{color} (does not interrupt MySQL IF LVM or ibbackup is used) \\ |
| {color:#cc3300}Server Disk I/O and Load Impact{color} \\ | {color:#cc3300}Heavy{color} \\ |
\\
{page-title}{excerpt}Zmanda adds a GUI to: mysqldump, Binlogs, and LVM Snapshots{excerpt}
[Zmanda|http://www.zmanda.com] the commercial effort behind the open source [Amanda|http://www.amanda.org/] Unix tape backup software make a backup product called [Zmanda Recovery Manager (ZRM) for MySQL|http://www.zmanda.com/zrm-mysql-enterprise.html].
Zmanda Recovery Manager (ZRM) 3.0 highlights the following features in their advertisements:
\\
# [Continuous Data Protection for Your MySQL Database|http://www.zmanda.com/zrm-mysql-enterprise.html#2]
Deep integration between ZRM, underlying storage and MySQL binary logs enables you to perform highly efficient CDP with almost instantaneous point-in-time recovery
# [Backup Live MySQL Databases Without Impacting Applications |http://www.zmanda.com/zrm-mysql-enterprise.html#3]\\
Perform hot backup of live MySQL by taking advantage of Linux LVM, Microsoft VSS, Solaris ZFS, Symantec VxFS, NetApp SnapManager, and EMC SnapView technologies.
# [Perform One-Click Point-In-Time Recovery|http://www.zmanda.com/zrm-mysql-enterprise.html#4]
ZRM provides unified point-in-time recovery for any type of backup method used
\\
h3. How Does Zmanda Recovery Manager (ZRM) Actually Work?
Zmanda Recovery Manager (ZRM) is a perl-based web utility used to manage the open source Amanda application. ZRM uses a variety of methods to extract data from MySQL and they are configurable at backup time. ZRM adds a GUI to all of the Legacy MySQL backup techniques and provides online backup using Online Volume Snapshots (e.g. LVM).
h4. *mysqldump & mysqlhotcopy*
Zmanda Recovery Manager (ZRM) uses [mysqldump|mysqldump] and [mysqlhotcopy][mysqlhotcopy|mysqlhotcopy]as an option.
[According to Zmanda|http://www.zmanda.com/backup-mysql.html]: "_Backups are done via_ *{_}mysqldump{_}{*}_, various snapshots,_{*}{_}mysqlhotcopy{_}* _or MySQL replication_."
\\
h4. Zmanda (ZRM) Online MySQL Backup
Zmanda Recovery Manager (ZRM) uses the [Volume Snapshot method|MySQL Volume Snapshot for Backup] for providing [Online backups of MySQL|TP:Categories of MySQL Backup Software] on Linux and Unix where available.
Zmanda Online Backup Availability
| *Linux MySQL Online Backups* \\ | Requires MySQL Data be Stored on an LVM Logical Volume and have Dedicated LVM Snapshot Storage \\ |
| *Windows MySQL Online Backups* \\ | No Not Available \\ |
| *Unix MySQL Online Backups* \\ | Requires Veritas File System for Snapshots \\ |
| *Network Attached Storage Online Bakcups* \\ | Supports Volume Snapshots using EMC Clarion and NetApp filers \\ |
h4. Zmanda Recovery Manager (ZRM) "Continuous Data Protection" for MySQL
Zmanda advertises a [continuous data protection offering for MySQL|http://www.zmanda.com/zmanda-announce-zrm22.html].
Zmanda use of the term "Continuous Data Protection" is very misleading. Zmanda does Not offer Continuous Data Protection ® for MySQL in any way like R1Soft or other CDP software vendors. Zmanda uses the term "Continuous Data Protection" to market it'sMySQL backups software. In the [Zmanda press release announcing Zmanda CDP,|http://www.zmanda.com/zmanda-announce-zrm22.html] Zmanda _seems_ to define it's implmentation of CDP as [Online Volume Snapshots,|MySQL Volume Snapshot for Backup] then goes on to elaborate about their use of [MySQL binary logs for backup and restore|TP:Binary Log Backups].
\\
*How Does Zmanda "CDP" for MySQL Work?*
We know very clearly Zmanda can do an Online backup of MySQL using Linux LVM, Veritas File System Snapshots, and the snapshot capability of Network Attached STorage devices like NetAPP and EMC. We also know Zmanda can copy MySQL binary logs or provide a GUI for [ibbackup|InnoDB ibbackup] (sold separately by Innobase). How this translates to Continuous Data Protection is unclear.
Continuous Data Protections is typically defined as either True CDP where SAN replication is used for 1-second playback and resolution OR a method of computing Deltas between scheduled backups in a near-COntinuous fashion using a device driver to track low level disk (Block Level) changes. Another attribute of Continuous Data Protection is the idea of Virtual Full Backup where each backup appears as a Full Backup even though only deltas are stored.
For more information on Continuous Data Protection see:
* [TP:Computing Deltas - near-Continuous (CDP)]
* [TP:Categories of Backup Software]
* [TP:Block Based Backup Technology]
* [TP:Backup Method - Virtual Full Backup]
* Wikipedia's Article's on CDP: [http://en.wikipedia.org/wiki/Near_Continuous_Backup], [http://en.wikipedia.org/wiki/Continuous_Data_Protection]\\
\\
| {color:#cc0000}Category{color}\\ | [Online|TP:Categories of MySQL Backup Software] IF LVM or other Volume Snapshots Available \\ |
| Archive Type | Disk or Tape \\ |
| MySQL Storage Engines Supported | All \\ |
| Supported O/S | All \\ |
| Binlog Backup & Restore | {color:#00cc00}Yes{color} \\ |
| {color:#000000}Zero Business Interruption (Online Backups){color} | {color:#000000}Yes{color} IF LVM or other Volume Snapshots Available |
| {color:#000000}Granular (Table Level) Restore{color} \\ | {color:#00cc00}Yes{color} |
| {color:#000000}Easy to Use Graphical User Interface{color} \\ | {color:#00cc00}Yes{color} |
| Complete Server Protection (Backup All Data or just MySQL?) \\ | {color:#00cc00}Yes with tar or dump{color} |
| Backup Type \\ | [Incremental|TP:Backup Method - Full Backup]\\ |
| {color:#cc3300}Backup Window Length{color} \\ | {color:#cc3300}Long{color} (does not interrupt MySQL IF LVM or ibbackup is used) \\ |
| {color:#cc3300}Server Disk I/O and Load Impact{color} \\ | {color:#cc3300}Heavy{color} \\ |
\\