Converse agora com nosso suporte
Chat com o suporte

NetVault Plug-in for MySQL 12.0 - User Guide

Introducing NetVault Backup Plug-in for MySQL Installing and removing the plug-in Configuring the plug-in Backing up data Restoring data Working with native MySQL replication Using the plug-in in a Failover Cluster environment Troubleshooting

Examples of backup sequences for MySQL Standard/Community

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.
Restoring this type of backup sequence is more time-consuming. For example, if recovery is performed on Tuesday, only Sunday’s Full Backup and Monday’s Incremental Backup must be restored; whereas, if recovery is performed on Thursday, Sunday’s Full Backup followed by Monday’s, Tuesday’s, and Wednesday’s Incremental Backups must be restored. Even though the backups are quicker, the restores can take longer due to the additional intervention that is required to run multiple restore jobs.
•
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.
Regardless of the time to which recovery is necessary, the same number of restore jobs is required. For example, if recovery is performed on Tuesday, Sunday’s Full Backup and Monday’s Differential Backup must be restored; whereas, if recovery is performed on Thursday, Sunday’s Full Backup followed Wednesday’s Differential Backup must be restored. Even though subsequent Differential Backups increase not only in size but in duration, restores are quicker due to the fewer restore jobs that must be run.

Performing a backup

A backup using Plug‑in for MySQL includes the steps outlined in the following topics.

•
Selecting data for a backup
•
Setting backup options
•
Finalizing and submitting the job

Selecting data for a backup

You must use sets — Backup Selection Set, Backup Options Set, Schedule Set, Target Set, and Advanced Options Set — to create a backup job.

Backup Selection Sets are essential for Incremental and Differential Backups. Create the Backup Selection Set during a Full Backup, and use it for Full, Incremental, and Differential Backups. The backup job reports an error if you do not use a Selection Set for the Incremental or Differential Backup. For more information, see the Quest NetVault Backup Administrator’s Guide.

 
* 
TIP: To use an existing set, click Create Backup Job, and select the set from the Selections list.
1
In the Navigation pane, click Create Backup Job.
You can also start the wizard from the Guided Configuration link. In the Navigation pane, click Guided Configuration. On the NetVault Configuration Wizard page, click Create backup jobs.
2
In Job Name, specify a name for the job.
Assign a descriptive name that lets you easily identify the job when monitoring its progress or restoring data. The job name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Linux, the name can have a maximum of 200 characters. On Windows, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.
3
Next to the Selections list, click Create New.
4
In the list of plug-ins, open Plug‑in for MySQL to display the MySQL Servers.
5
Select the applicable data:
•
To include all MySQL databases in the selected instance in the backup job, select the All Databases node.
•
For a more detailed selection, open the All Databases node to display the individual databases. In addition, you can open each individual database to display its individual tables, which can be selected as applicable for inclusion in a backup job.
•
To explicitly omit items from a backup, select a parent-level item, and click the applicable child-level item to replace the green check mark with a red “X” (cross), which marks it as omitted.
 
* 
IMPORTANT: If you select a detailed set of data for backup with the MySQL Standard/Community option, select Individual Database/Table Copy Only as the backup type on the Backup Options tab. If any other form of backup is selected, that is, Full, Incremental, or Differential Backup, detailed selections are ignored, and the entire database is backed up. For MySQL 5.5 and later, stored procedures, functions, and triggers are automatically backed up with Full and Individual Database/Table Copy Only backups for the MySQL Standard/Community option.

For MySQL 5.5 and later, the “information_schema” database is displayed in the selection tree but it is not available for selection. This issue occurs because all the data contained in this database is generated dynamically, and does not exist in any permanent sense. Therefore, the plug-in automatically excludes the information_schema database from all backups.
6
Click Save, enter a name in the Create New Set dialog box, and click Save.
The name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Linux, the name can have a maximum of 200 characters. On Windows, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.

Setting backup options

The next step involves creating the Backup Options Set or selecting an existing one. The settings available on the Backup Options tab depend on whether you use the MySQL Standard/Community or MySQL Enterprise Backup option.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação