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

NetVault Plug-in for MySQL 11.4 - Release Notes

Resolved issues

The following is a list of issues addressed in this release.
 
Table 2. General resolved issues
Resolved issue
Issue ID

Corrected an issue that displayed the Lock All Tables with Read Access During Backup to Prevent Loss of Transactions option as selected even when the option did not apply to the task. If the option does not apply to the task, it is displayed as disabled.

DNMYSQL-310

Known issues

The following is a list of issues, including issues attributed to third-party products, known to exist at the time of release.
 
Table 3. General known issues
Known issue
Issue ID

The plug-in name has been changed to use the “Plug-in for <product>” naming convention, that is, Plug‑in for MySQL. If you upgrade the plug-in for a system that is managed by NetVault Backup Server 9.2, a consequence of the name change is that savesets created with the upgraded plug-in are not displayed in the NVBU Restore window when the Selection Method is set to Plugin; only savesets created with an earlier version are displayed.

Workaround for NetVault Backup Server 9.2: On the Selections tab of the NVBU Restore window, select Job in the Selection Method list to view savesets or backups created with a previous version or the upgraded plug-in.

This issue was corrected in NetVault Backup 10.0.

NVBU-8267 (23470)

Due to MySQL bug 69953, performing a restore to MySQL Server 5.5 or 5.6 fails to drop the existing slow_log table in the mysql database if MySQL logging is enabled. Therefore, the restore also fails to restore the same table. If the slow_log table is critical to your environment, re-create the slow_log table manually after the restore job completes. This issue is corrected in MySQL 5.7.

DNMYSQL-319 (30852)

Because backup data is streamed from the MySQL Server directly to the NetVault Backup Media Manager, use of special characters in database names might be interpreted as a sequence command, which affects the integrity of the backup data.

Workaround: To avoid potential issues, do not use the following characters in database names: $ ^ = @ # % +

DNMYSQL-379

 
Table 4. MySQL Standard/Community known issues
Known issue
Issue ID

Default setting of lower_case_table_names system variable affects MySQL behavior on Mac OS X: The inconsistent behavior of case-sensitivity of MySQL on Mac OS X platforms affects the ability of the plug-in to restore backups. To ensure that you accommodate this inconsistency, be aware of the following when using the plug-in with Mac OS X:

•
If the lower_case_table_names system variable is set to 1, Incremental Restores work correctly for databases that were created using lowercase, uppercase, or mixed-case names. Also, the database names are displayed in the NetVault Backup Console using lowercase letters regardless of how the actual names were created.
•
If the lower_case_table_names system variable is set to 2, the default setting on Mac OS X, Incremental Restores only work correctly for databases that were created using lowercase names. Also, the database names are displayed in the NetVault Backup Console using the same format with which they were created.

If you change the value of the lower_case_table_names system variable, stop and restart the MySQL Server to ensure that the change is implemented. For more information about this MySQL-related issue, see: http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html

DNMYSQL-133 (18430, MYG‑235)

Selecting Enable MySQL Replication but not configuring replication causes backups to fail: If you select the Enable MySQL Replication check box on the Configure dialog box but do not configure replication, backups fail. To correct this issue, either clear the Enable MySQL Replication check box on the Configure dialog box or set up replication and run the backup job again.

DNMYSQL-241 (21629)

 
Table 5. MySQL Enterprise Backup (MEB) known issues
Known issue
Issue ID

Under certain conditions, all InnoDB tables are backed up: All InnoDB tables in a MySQL instance are backed up if either of the following conditions is met:

1
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.
2
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 behavior reflects current MEB (mysqlbackup utility) behavior, which might change in a future release (post-3.8.1).

DNMYSQL-275 (22383)

The plug-in does not support use of versions 3.12 and 4.0 of the MEB-based method in a clustered environment. You can only use these versions in a standalone environment.

DNMYSQL-363 (32199)

System requirements

Before installing Plug‑in for MySQL 11.4, ensure that your system meets the requirements outlined in the Quest NetVault Backup Compatibility Guide available at https://support.quest.com/technical-documents.

Upgrade and compatibility

•
Plug‑in for MySQL 11.4 requires NetVault Backup 10.0 or later. For complete supported-platform information, see the Quest NetVault Backup Compatibility Guide.
•
Upgrades and new installs of MySQL: As explained in bug 68807 for MySQL, http://bugs.mysql.com/bug.php?id=68807, mysql_install_db ignores /etc/my.cnf in MySQL 5.6. Because MySQL 5.6 creates InnoDB statistic tables (slave_master_info, mysql/slave_relay_log_info, innodb_index_stats, innodb_table_stats, and slave_worker_info) and adds them to the installation directory (basedir) of MySQL, you might encounter a conflict with the innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend option contained in the “my.cnf” file. The file_path option places the InnoDB files one directory level higher than the basedir, which can cause the following error to is displayed in the MySQL error log:
"[Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal
data dictionary of InnoDB though the .frm file for the table exists. See
http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you
can resolve the problem."
Until you address this error, the plug-in cannot browse the main MySQL database, and the following error is displayed: "Failed to fetch row from query result: showtable status like 'innodb\_index\_stats'"
It can also cause backup jobs to stop responding.
Because this option originated from a recommended sample “my.cnf” file for an earlier version of MySQL, this issue usually occurs on upgrades or new installs that retained the earlier version of the “my.cnf” file. Quest recommends that you do not use the file_path option on new installations and that you move the ibdata files to basedir for upgrades. For assistance, contact MySQL Support. (22367)
•
Upgrades from NetVault Backup Server from 9.2: If you upgrade your NetVault Backup Server from 9.2 to 10.x or later, the settings you configured for error conditions encountered by the Plug‑in for MySQL are returned to their defaults. If you modified the settings for error conditions encountered by the plug-in, Quest recommends that you reinstall the plug-in, reconfigure its settings, and re-create MySQL backup jobs.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级