For the MySQL Enterprise Backup option, the plug-in runs the mysqlbackup command once for all selected database objects to achieve the following types of backup: Full, Incremental, and TTS.
In a Full Backup for the MySQL Enterprise Backup option, the plug-in uses the mysqlbackup utility or applicable NetVault Backup script to back up every selected database object included in the instance. Full Backups are the foundation of any backup strategy because they provide the starting point for almost every restore scenario. Full Backups generated with the plug-in can be used to restore an entire instance, individual or multiple databases, and individual or multiple tables.
If you perform a TTS Backup, the plug-in issues a Full Backup and adds the “--use-tts” MySQL option.
If you intend to generate TTS Backups, be aware of the following limitations:
• |
Only tables that were created with the innodb_file_per_table option enabled are included in the backup. |
For more limitations on the use of the “--use-tts” option, see https://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/backup-partial-options.html.
For the Mariadb-backup method, the plug-in runs the Mariadb-backup command once for all selected database objects to achieve the following types of backup: Full, and Incremental..
In a Full Backup for the Mariadb-backup option, the plug-in uses the Mariadb-backup utility or applicable NetVault script to back up every selected database object included in the instance. Full Backups are the foundation of any backup strategy because they provide the starting point for almost every restore scenario. Full Backups generated with the plug-in can be used to restore an entire MariaDB instance.
The following provides examples of the various sequences.
• |
Full Backups only: When requirements guarantee data protection up to the previous day and daily read-only access is permissible, for example, after regular business hours, performing only Full Backups daily should be sufficient. While DBAs are only guaranteed to be able to recover the database up to the point of the last Full Backup, they can perform a PIT Recovery using the Binary Logs that currently exist on the MySQL Server. |
• |
Full and Incremental Backups: When requirements guarantee data protection up to the previous day, but read-only access to the target MySQL Instance is only permissible at intermittent times — for example, after regular business, on only a weekly or biweekly basis — and backup time should be as fast as possible, Full Backups coupled with Incremental Backups is the best combination. For example, Full Backups are performed every Sunday night at 11:00 P.M., while Incremental Backups are performed Monday through Saturday at 11:00 P.M. Each Incremental Backup includes the Binary Logs that were generated since the previous night’s backup, whether it be the Sunday evening Full Backup or one of the Incremental Backups. |
• |
Full and Differential Backups: When requirements guarantee data protection up to the previous day, but read-only access to the target MySQL Instance is only permissible at intermittent times — for example, after regular business hours, on only a weekly or biweekly basis — and restore time should be as fast as possible, Full Backups coupled with Differential Backups is the best combination. For example, Full Backups are performed every Sunday night at 11:00 P.M., while Differential Backups are performed Monday through Saturday at 11:00 P.M. Each Differential Backup includes the Binary Logs that were generated since the last Full Backup. As noted earlier, this process requires more overall backup time. |
A backup using Plug‑in for MySQL includes the steps outlined in the following topics.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center