• |
Quest NetVault Backup (NetVault Backup) Plug‑in for MySQL (Plug‑in for MySQL) 12.0 is a minor release, with enhanced features and functionality. For complete product documentation, visit https://support.quest.com/technical-documents.
Updated the plug-in to complete Incremental and Differential Backup jobs with a status of “Backup Completed with warnings” in environments that use the MIXED Binary Log Format. If your environment uses this format, it might prevent Binary Log entries from being replayed during a Point-in-Time (PIT) Recovery. For more information, see the Quest NetVault Backup Plug‑in for MySQL User’s Guide |
|
Added an Entire Databases Copy Backup option, which you can use to back up a database in its entirety instead of backing up individual tables. |
|
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. |
|
Workaround: To avoid potential issues, do not use the following characters in database names: $ ^ = @ # % + |
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 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 |
|||||
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. |
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: 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 behavior reflects current MEB (mysqlbackup utility) behavior, which might change in a future release (post-3.8.1). |
|
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center