Chatee ahora con Soporte
Chat con el soporte

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

1
In the Navigation Pane, click Create Backup Job, and click Create New next to the Selections list.
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)

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.
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.
6
Click Apply to save the settings.

Backing up data

Backing up data – an overview

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.
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:
If you intend to use the MySQL Enterprise Backup option, review the following guidelines and information:
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.
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.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación