NetVault Plug-in for MySQL 12.2.1

Quest NetVault Backup (NetVault Backup) Plug‑in for MySQL (Plug‑in for MySQL) 12.2.1 is a minor release, with enhanced features and functionality designed specifically for users of MySQL 8.0 and later. For complete product documentation, visit https://support.quest.com/technical-documents.


	NOTE: Plug‑in for MySQL 12.2.1 is compatible only with MySQL 8.0 and later, and is available only for Linux servers. NOTE: Plug‑in for MySQL 12.2.1 is available only for 64-bit Linux distributions. For other platforms, use Plug‑in for MySQL 12.2.

Enhancements

The following is a list of enhancements implemented in NetVault Backup Plug‑in for MySQL 12.2.1.

Table 1. General enhancements
Enhancement	Issue ID
Added support for MySQL authentication plug-ins that implement the following SHA-256 hashing methods: sha256_password and caching_sha2_password.	DNMYSQL-418, DNMYSQL-434
Added support for MySQL Commercial Server 8.0.	DNMYSQL-431
Added supported for MySQL Enterprise Backup (MEB) 8.0.	DNMYSQL-432

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 2. General known issues

Known issue

Issue ID

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

In MySQL replication environments, backup job fails if the master info log or relay info log are written to tables instead of files.

Workaround: To prevent a backup job failure, create empty master.info and relay-log.info files in the index log path directory. To create the empty logs, run the following commands under mysql user:

$ touch /var/lib/mysql/relay-log.info

$ touch /var/lib/mysql/master.info

DNMYSQL-439

Due to a difference in required libraries, NetVault Backup Plug‑in for MySQL may not run on Red Hat Enterprise Linux (RHEL) 8.0.

Workaround: If libnsl.so.1 does not exist, create a symbolic link to libnsl.so.2 using the following commands for 64-bit libnsl.so:

•

To check if libnsl.so.1 exists, use:

# ls -al /usr/lib64/libnsl.so.1

•

To create a symbolic link, use:

# ln -s /usr/lib64/libnsl.so.2 /usr/lib64/libnsl.so.1

DNMYSQL-442

Table 3. 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 4. 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:

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 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)