Capabilities of ZRM for MySQL: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(5 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
* It supports multiple backup methods depending on the storage engine used by MySQL tables. | * It supports multiple backup methods depending on the storage engine used by MySQL tables. | ||
* It has two levels of backups : full and incremental database backups. | * It has two levels of backups : full and incremental database backups. | ||
* It can use [http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html mysqldump], [http://dev.mysql.com/doc/refman/5.0/en/mysqlhotcopy.html mysqlhotcopy], | * It can use [http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html mysqldump], [http://dev.mysql.com/doc/refman/5.0/en/mysqlhotcopy.html mysqlhotcopy], snapshots(Linux LVM/Solaris ZFS) and [http://dev.mysql.com/doc/refman/5.0/en/replication.html MySQL replication] as various backup methods. | ||
* It creates consistent backup of the database irrespective of the storage engines used by the databases tables. | * It creates consistent backup of the database irrespective of the storage engines used by the databases tables. | ||
* It supports SSL authentication between the local ''ZRM for MySQL'' and remote MySQL server to allow secure backups over Internet or across firewalls. | * It supports SSL authentication between the local ''ZRM for MySQL'' and remote MySQL server to allow secure backups over Internet or across firewalls. | ||
* It can verify backed up data images. | * It can verify backed up data images. | ||
* Backup images can be compressed as well as encrypted using standard tool such as ''gzip'', ''GPG'', etc . | * Backup images can be compressed as well as encrypted using standard tool such as ''gzip'', ''GPG'', etc . | ||
* System administrator can abort backup jobs. | |||
* Treat snapshots as backup images and convert them into real backups later. | |||
* Support for pre- and post- backup plugins. | |||
* Ability to exclude databases and tables from backup using wildcards. | |||
=== Recovery Capabilities === | === Recovery Capabilities === | ||
Line 31: | Line 35: | ||
** This helps in deciding what to restore and what to keep out. | ** This helps in deciding what to restore and what to keep out. | ||
* Depending on the type of backups you have been doing, the backed up data could be recovered on to the same machine or to an entirely different machine. | * Depending on the type of backups you have been doing, the backed up data could be recovered on to the same machine or to an entirely different machine. | ||
* Support pre- and post-restore plugins. | |||
=== Reporting and Scheduling Capabilities === | === Reporting and Scheduling Capabilities === | ||
Line 39: | Line 44: | ||
* It can report any backup statistic or combination thereof. | * It can report any backup statistic or combination thereof. | ||
* It can format reports as HTML or Text . | * It can format reports as HTML or Text . | ||
* It sends email notification about the backup run status. | * It sends email notification about the backup run status. You can specify when to send emails. | ||
* It can provide backup reports as RSS feed. | * It can provide backup reports as RSS feed. | ||
Line 46: | Line 51: | ||
* ''ZRM for MySQL'' provides plugins to extend the suite. | * ''ZRM for MySQL'' provides plugins to extend the suite. | ||
* Plugins allow administrators to tailor the backup process for their environment . | * Plugins allow administrators to tailor the backup process for their environment . | ||
* It provides | * It provides templates for creating plugins easily. | ||
* Plugins can be created for: | * Plugins can be created for: | ||
** Pre-scheduler plugin | ** Pre-scheduler plugin | ||
** Pre-backup plugin | ** Pre-backup and Post-backup plugin | ||
** Post- | ** Pre-restore and Post-restore plugin | ||
** Copy plugin | ** Copy plugin | ||
** Binary log parser plugin | ** Binary log parser plugin | ||
** Snapshot plugin |
Latest revision as of 01:21, 9 January 2010
Optimize Backup and Restore Capabilities
- ZRM for MySQL understands the importance of optimizing Backup and Restore capabilities.
- It provides full flexibility to individually tailor each backup set methods, levels, schedules etc.
- It generates logs that assist in optimizing these capabilities.
- It provides filters to easily locate errant database events.
Backup Capabilities
- ZRM for MySQL can backup multiple MySQL databases that are managed by the MySQL server.
- It can backup multiple databases hosted on multiple MySQL servers.
- It can also backup tables in a single database.
- It can perform hot backups of the databases.
- It supports multiple backup methods depending on the storage engine used by MySQL tables.
- It has two levels of backups : full and incremental database backups.
- It can use mysqldump, mysqlhotcopy, snapshots(Linux LVM/Solaris ZFS) and MySQL replication as various backup methods.
- It creates consistent backup of the database irrespective of the storage engines used by the databases tables.
- It supports SSL authentication between the local ZRM for MySQL and remote MySQL server to allow secure backups over Internet or across firewalls.
- It can verify backed up data images.
- Backup images can be compressed as well as encrypted using standard tool such as gzip, GPG, etc .
- System administrator can abort backup jobs.
- Treat snapshots as backup images and convert them into real backups later.
- Support for pre- and post- backup plugins.
- Ability to exclude databases and tables from backup using wildcards.
Recovery Capabilities
- ZRM for MySQL makes it easy to recover backed up data.
- It supports the use of an backup index that stores information about each backup run.
- It has a reporting tool that can be used for browsing the index.
- It can recover full and incremental database backups.
- It does selective incremental restores based on binary log position or at a point in time . This permits recovery from database operator errors.
- Such a point could be a point in time or a point in the binary logs of the Database.
- ZRM for MySQL provides an easy way to filter in / filter out database events from the binary logs.
- This helps in deciding what to restore and what to keep out.
- Depending on the type of backups you have been doing, the backed up data could be recovered on to the same machine or to an entirely different machine.
- Support pre- and post-restore plugins.
Reporting and Scheduling Capabilities
- ZRM for MySQL can schedule backup runs immediately or in daily/weekly/monthly intervals.
- It automatically generates backup reports .
- It has predefined backup reports as well as user defined backup reports.
- It can report any backup statistic or combination thereof.
- It can format reports as HTML or Text .
- It sends email notification about the backup run status. You can specify when to send emails.
- It can provide backup reports as RSS feed.
Plugins
- ZRM for MySQL provides plugins to extend the suite.
- Plugins allow administrators to tailor the backup process for their environment .
- It provides templates for creating plugins easily.
- Plugins can be created for:
- Pre-scheduler plugin
- Pre-backup and Post-backup plugin
- Pre-restore and Post-restore plugin
- Copy plugin
- Binary log parser plugin
- Snapshot plugin