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

NetVault Plug-in for MySQL 13.2 - Release Notes

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

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

DNMYSQL-461

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

DNMYSQL-478

Due to a difference in required libraries, NetVault 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

DNMYSQL-497

An error NetVault.Backup.Core.NVObjectDeserializeException occurs when attempting to open large binary log context containing snippet of mysqldump output.

DNMYSQL-456

When you start restoring, restoring a view, routine, trigger, event, procedure, etc. might fail, if participating tables (and views) have not yet restored.

DNMYSQL-464

While setting up Plug-in for MySQL it is required that the NetVault Server and NetVault Client are set with the same locale.

DNMYSQL-479

Plug-in for MySQL does not support the UTF8MB4 Character Set.

DNMYSQL-496

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

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)

Lock & Copy Table Files backup method for MyISAM Backup Method, does not work for MySQL 8 onward, as the plug-in attempts to access .from the metadata files that are no longer present in MySQL 8.x

DNMYSQL-475

 
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 the MEB-based method in a clustered environment. You can only use the MEB-based method in a standalone environment.

DNMYSQL-363 (32199)

System requirements

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

Upgrade and compatibility

 
* 
CAUTION: This release supports MySQL Server version 8, MySQL Enterprise Backup version 8, and MariaDB Server versions 10 and 11. If you upgrade to this release, it will not be compatible with previous versions of MySQL Server, and MariaDB Server.
•
Plug‑in for MySQL 13.2 requires NetVault 13.0 or later. For complete supported-platform information, see the Quest NetVault Compatibility Guide.
•
Upgrades from NetVault Backup Server from 9.2: If you upgrade your NetVault Backup Server from 9.2 to 13.0 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 file for your NetVault Server environment, determine the NetVault Machine ID of your main NetVault 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 License Management page to install the product license files.

•
Obtaining a machine ID
•
Installing a license file
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택