立即与支持人员聊天
与支持团队交流

NetVault Plug-in for MySQL 13.2 - User Guide

Introducing NetVault Plug-in for MySQL Installing and removing the plug-in Configuring the plug-in Backing up data Restoring data
Restoring data: an overview Restoring data Using advanced restore procedures for MySQL Standard/Community
Working with native MySQL replication Using the plug-in in a Failover Cluster environment Troubleshooting

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.

Setting backup options for MySQL Standard/Community

With the applicable items selected for backup, you can select the type of backup to perform and select a different behavior if there is a failure.

 
* 
TIP: To use an existing set, in the Plugin Options list, select the set that you want to use.
1
Next to the Plugin Options list, click Create New.
2
Select the applicable option:
 
* 
IMPORTANT: If you specified the target instance of MySQL as a “Replication Master Instance,” that is, the Enable MySQL Replication and Master Instance options were selected in the Configure dialog box for this instance, the Full, Incremental, and Differential forms of backup are unavailable for selection. For more information, see Working with native MySQL replication.
•
Full Backup for All Databases (default selection): To perform a complete backup of every database and all tables included in the current MySQL Instance, select this option. Selecting this option backs up everything, regardless of the data that you select for the Backup Selection Set.
•
Incremental Backup: To back up only the transaction logs that were generated since the last Full or Incremental Backup, select this option.
•
Differential Backup: To back up all the transaction logs that have been generated since the last Full or Incremental Backup, select this option. Each time a subsequent Differential is performed, it contains all Binary Logs generated since the original Full was performed. After the backup is finished, the Binary Logs are kept on the MySQL Instance.
 
* 
IMPORTANT: Incremental and Differential Backup jobs complete with a warning if the MIXED Binary Logging Format is used. For more information, see Using the MIXED Binary Logging Format.
 
* 
CAUTION: Because Binary Log entries might be not replayed during a PIT recovery if the MIXED Binary Logging Format is used, databases selected for recovery might not be rolled back to the selected point. For more information, see Important notes for MySQL Standard/Community and Using the MIXED Binary Logging Format.
•
Individual Database/Table Copy Only: To create a special-purpose copy of a MySQL environment that does not affect the overall backup and restore procedures for the database, for example, creating a test environment, select this option. When used, these copy backups do not affect the sequence established by a Full and Incremental or Differential MySQL backup scenario, that is, these backups have no effect on Binary Logs. This form of backup is independent of what should be established as a normal sequence of backups by using a Full and Incremental or Differential MySQL backup scenario. In addition, a copy backup cannot be used as a replacement for a Full Backup.
•
Entire Databases Copy Backup: To back up all the contents of the selected databases by creating a special-purpose copy of a MySQL environment, select this option. For example, to build a test environment, select this option. This option is similar to the Individual Database/Table Copy Only option, but this option backs up all selected databases and their corresponding tables. You can use this option only if all the tables for the selected databases are InnoDB tables. When used, these copy backups do not affect the sequence established by a Full and Incremental or Differential MySQL backup scenario, that is, these backups have no effect on Binary Logs. In addition, a copy backup cannot be used as a replacement for a Full Backup.
 
* 
IMPORTANT: You can use this option only if all the tables for the selected databases are InnoDB tables.

Selecting this option backs up the entire selected database and all corresponding tables. This occurs even if you select a specific table to back up. If you want to back up a specific table, use the Individual Database/Table Copy Only option.

•
Lock All Tables with Read Access…: If you selected Full Backup and you want to prevent the loss of transactions by locking all the databases in the instance that currently have read-only access, select this check box. When this option is selected, users are unable to insert, update, or delete data across the entire instance while the Full Backup is in progress. When this option is cleared, the plug-in locks each table during the backup process only when the table is being backed up; therefore, if the instance contains tables that are related, Quest recommends that you select this option to ensure that all tables are locked during the process.
•
Purge Binary Logs…: This option is selected by default when the plug-in is used with a standard MySQL Server configuration, Enable MySQL Replication is disabled, and Enable Point-In-Time Recovery is enabled. It is disabled when the plug-in is connected to a cluster; you must manage the purging of the Binary Logs outside of the plug-in. Quest recommends that you use this option, but you can decide how much control you want over the Binary Logs.
 
* 
IMPORTANT: In a mixed environment, where a NetVault Backup Server manages both clustered and standard MySQL Servers, do not reuse a Backup Options Set — created for a standard MySQL Server — for a MySQL-based cluster.
3
Select the applicable action for each condition; for more information, see Setting default actions for error conditions (optional).
Each of these conditions lets select an action to take for this job, even if you set default actions that are different:
•
Complete with Warnings — Saveset Retained: The job returns a status of “Backup Completed with warnings” and a backup saveset is created that includes the items that were successfully backed up.
•
Complete without Warnings — Saveset Retained: The job completes and returns a status of “Backup Completed.” The errors are logged in the NetVault Backup binary logs and ignored on the Job Status page. A backup saveset is created that includes the items that were backed up.
•
Fail — Saveset Retained: The job returns a status of “Backup Failed.” However, a backup saveset is generated that includes the items that were successfully backed up.
•
Fail — No Saveset Retained: The job returns a status of “Backup Failed” and no saveset of backed-up objects is kept. That is, even if some of the objects were successfully backed up, the saveset is discarded.
4
In the Mysqldump options box, list the command options that you want the mysqldump utility to use for the job.
The options must begin with a dash or double-dash, and they cannot contain invalid characters (; | < >).
These options are added to the mysqldump command first, followed by the options that the plug-in generates internally. Because of this order, an option that you enter here that contradicts one generated internally is overridden by the one generated by the plug-in.
Errors detected by mysqldump that cause the job to fail are embedded in the error log message in the job log.
If you previously set up MySQL Option files to accomplish this task, the options that you enter here are appended to the options specified in the Option files. If you want the plug-in to ignore existing MySQL Option files, enter --no-defaults as the first option in this box.
For information about the options supported by your version of mysqldump, see the applicable MySQL documentation.
 
* 
CAUTION: Do not use the --routines (-R) or --triggers option with this feature. Using these options interferes with backups of database tables, and while backups succeed, restores might fail. If there are stored procedures and triggers that must be backed up for a database, the plug-in generates mysqldump commands internally with the --routines and ‑‑triggers options.
5
Click Save to save the set.
6
In the Create New Set dialog box, specify a name for the set, 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 for MySQL Enterprise Backup

With the applicable items selected for backup, you can select the type of backup to perform and select a different behavior if there is a failure.

 
* 
TIP: To use an existing set, in the Plugin Options list, select the set that you want to use.
1
Next to the Plugin Options list, click Create New.
2
Select the applicable option:
•
Full Backup (default selection): To back up every database and table selected in the current MySQL Instance, select this option.
•
Incremental Backup: To back up only the data, for InnoDB tables, or complete tables, for non-InnoDB tables, changed since the last Full or Incremental Backup, select this option.
•
Transportable Tablespace (TTS) Backup: To create a partial backup that takes advantage of the MySQL TTS feature, select this option.
3
Click Save to save the set.
4
In the Create New Set dialog box, specify a name for the set, 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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级