지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Plug-in for MySQL 4.4 - User Guide

Introducing Dell™ 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-inin a Failover Cluster environment Troubleshooting About Dell

Updating the configuration of an existing instance

After an instance of MySQL has been successfully configured and added to the plug-in for use, you can edit its configuration options by performing the following steps:
1
In the Navigation Pane, click Create Backup Job, and click Create New next to the Selections list.
2
In the selection tree, open the applicable client node.
3
Open the Plug‑in for MySQL node, and select the applicable instance.
4
From the Actions list, select Configure.
The Configure dialog appears with all previous settings revealed, allowing you to make any necessary modifications.
 
 
*IMPORTANT: In the Edit version, the MySQL Instance Name field is dimmed. This field is for information only and displays the name of the selected instance.

Setting default actions for error conditions (optional)

MySQL backup jobs typically include multiple storage engines, databases, and/or tables. Occasionally during the execution of a backup job, an unsupported storage engine will be encountered or a database/table will be inaccessible, which prevents one or more items from being backed up successfully, while the remaining items selected in the backup job are backed up. A MySQL DBA needs to determine what action should be taken when these conditions are encountered:
•
Should the backup job complete with warnings, complete without warnings, or fail?
•
Should the backup of items that completed successfully be retained or discarded?
The plug-in lets you set default options for backup and restore jobs. You can override these options on a per-job basis.
To configure default settings
1
In the Navigation pane, click Change Settings.
2
On the Configuration page, click Server Settings or Client Settings, as applicable.
3
If you selected Client Settings, select the applicable client, and click Next.
4
On the NetVault Server Settings or Client Settings page, click Plugin Options.
In the Plug‑in for MySQL section, the following items are listed:
•
Locked Table – This occurs when a table selected for inclusion in the backup is locked by a client session other than the plug-in.
•
Manually Selected Table Unavailable – This occurs when an individual table is unavailable for backup for any reason,  such as being dropped since the backup job was defined
•
Manually Selected Database Unavailable – This occurs when an individual database is unavailable for backup for any reason, such as being dropped since the backup job was defined
•
Unsupported Storage Engine – This occurs when a table is encountered during the backup that has a type of storage engine that is not currently supported by the plug-in.
5
For each of these conditions, select one of the following settings:
•
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.” While errors are logged in the NetVault Backup binary logs, the errors are essentially ignored in the Job Status page and a backup saveset is created that includes the items that were successfully 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.
 
 
*IMPORTANT: You can override the selected default action selected at the individual backup job level.
6
Click Apply to save the settings.

Backing up data

•
Backing up data – an overview
•
Performing a backup

Backing up data – an overview

Before completing a backup, review the information in the following sections:
•
Important notes for MySQL Standard/Community
•
Important notes for MySQL Enterprise Backup
•
Defining a backup strategy
Important notes for MySQL Standard/Community
If your environment uses databases whose names contain special characters, such as hyphens (all characters except alphanumeric characters and underscores are considered special characters), be aware of the following limitations:
•
All table types except MyISAM are backed up, even if the database name contains hyphens. This is because the mysqldump command is always used for these table types.
•
If the database name contains hyphens, MyISAM tables are backed up if the MyISAM Backup Method is set to the Mysqldump option introduced in version 4.2. Note that performance of backups and restores might be negatively affected.
•
If the MyISAM Backup Method is set to use the default Lock & Copy Table Files option and the database name contains hyphens, MyISAM tables are not backed up because the plug-in bypasses MySQL commands and tries to copy the table files directly. The plug-in will log an error message indicating that the table file cannot be located, and then fail the backup job without creating a saveset.
With previous versions, the plug-in would attempt to verify the existence of the database directory, log a warning message when it failed to do so, and continue with backup of the next database. The backup would complete with warnings and create a saveset that included all other databases.
If you want to maintain the original behavior and still use the Lock & Copy Table Files option for any reason, such as less-than-optimal performance impact when using the Mysqldump option, you can manually set the ValidateDatabaseDirectory parameter to TRUE in the plug-in configuration file, “nvmysql.cfg,” as follows:
[MySql:ValidateDatabaseDirectory]
Value=TRUE
If you subsequently decide to use the new behavior instead, you can change the parameter to FALSE or remove the parameter from the “nvmysql.cfg” file.
Important notes for MySQL Enterprise Backup
If you intend to use the MySQL Enterprise Backup option, review the following guidelines and information:
•
MySQL recommends that you use InnoDB tables for critical data because the backup process is faster and the reliability and scalability features are significant. MySQL Enterprise Backup lets you back up various kinds of MySQL tables, and it is optimized for backing up InnoDB tables. This option performs a hot backup of all InnoDB tables. Because hot backups are performed while the database is running, the backup does not stop ongoing database operations. Additionally, any database changes made during the backup process are included. This is important if your environment requires that the database remains online while also supporting its growth, which impacts the time required to complete a backup.
•
When you use this option, the MyISAM table and other non-InnoDB tables are backed up last, using a warm backup. In a warm backup, the database continues to run, but the tables are set to read-only access while the backup is completed.
•
If you want to ensure that the bulk of your data is backed up during the hot-backup phase, consider making InnoDB the default storage engine for new tables and converting existing tables to use the InnoDB storage engine. (In MySQL Server 5.5 and later, InnoDB is the default.)
•
An Incremental Backup is primarily intended for InnoDB tables and non-InnoDB tables that are read-only or updated infrequently. For non-InnoDB files, the entire file is included if it changed since the last backup.
•
When using the plug-in, all InnoDB tables in a MySQL instance are backed up if either of the following conditions is met:
•
Only tables are explicitly selected for backup, and none of the tables are of type or storage engine InnoDB.
Example: You have a MySQL Instance with two databases (DB1 and DB2). Each database contains two tables: DB1 has T1_InnoDB and T1_MyISAM and DB2 has T2_InnoDB and T2_MyISAM. If you back up T1_MyISAM and T2_MyISAM, T1_InnoDB and T2_InnoDB are also backed up. If you include one of the InnoDB tables, only that InnoDB table is backed up. If you select one of the databases, only the tables in the database are backed up.
•
Some or all databases are selected for backup and all associated InnoDB tables are excluded from the backup.
Example: You have a MySQL Instance with two databases (DB1 and DB2). Each database contains two tables: DB1 has T1_InnoDB and T1_MyISAM and DB2 has T2_InnoDB and T2_MyISAM. If you back up DB1 and DB2 and exclude T1_InnoDB and T2_InnoDB, T1_InnoDB and T2_InnoDB are also backed up. If you exclude only one of the two InnoDB tables, only the other InnoDB table is backed up.
This reflects the current behavior of MySQL Enterprise Backup (mysqlbackup utility); this behavior might change in a future release (post-3.8.1) of MySQL.
•
In MySQL 5.5, the innodb_file_per_table configuration option is disabled by default. In MySQL 5.6, it is enabled by default. Any InnoDB tables that are created with the innodb_file_per_table option disabled are stored in the InnoDB system tablespace; they cannot be omitted from the backup. If you need to place an InnoDB table outside the tablespace, create it while the innodb_file_per_table option is enabled in MySQL. Each .ibd file will contain the data and indexes of only one table.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택