Chat now with support
Chat with Support

NetVault Plug-in for MySQL 12.2.1 - Release Notes

System requirements

Before installing Plug‑in for MySQL 12.2.1, 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

 
* 
CAUTION: This release uses only version 8.0 of MySQL Enterprise Backup and MySQL Enterprise Server. If you upgrade to this release, it will not be compatible with previous versions of MySQL.
•
Plug‑in for MySQL 12.2.1 requires NetVault Backup 11.4.5 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, 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 11.4.5 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.

Product licensing

To obtain the license key for your NetVault Backup Server environment, determine the NetVault Machine ID of your main NetVault Backup Server. Also identify the machine IDs of any clients running application plug-ins, such as Oracle, MySQL, PostgreSQL, SQL Server, and Exchange.

You can use the NetVault Configuration Wizard to install the product license keys. Alternatively, you can install the license keys from the Manage Clients page.

•
Obtaining a machine ID
•
Installing a license key using the configuration wizard
•
Installing a license key from the Manage Clients page

Obtaining a machine ID

1
Start the NetVault Backup WebUI.
2
In the Navigation pane, click Manage Clients.
3
In the NetVault Backup Clients list, select the applicable machine, and click Manage.
4
On the View Client page, note the machine ID exactly as it is displayed in the Client Summary table.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating