MySQL Backup Fails with "Failed to backup 'XXXXXXX' table 'XXXXXXXXXXX' for database 'XXXXXXXXXXX (4046068)

MySQL Backup Fails with "Failed to backup 'XXXXXXX' table 'XXXXXXXXXXX' for database 'XXXXXXXXXXX' ".

Depending on backup configuration, NetVault Backup plugin for MySQL requires access to exclusively lock the tables for backup. This makes sure that the table is completely consistant during backup.
The plugin is like a wrapper around mysqldump, sending the dump data to NetVault controlled devices and database. If locking is enabled, the table locking is performed by something similar to:
# mysqldump --lock-tables

http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html#option_mysqldump_lock-tables

There are two resolutions:

1. Uncheck the "Lock All Tables with Read Access During Backup" option in the Backup Options configuration tab. This will remove the --lock-tables from the dump command. The big problem with this path is that the database can be updated during backup so the backup will not be consistent.
2. Make sure that the user configured to run backups in the NetVault MySQL plugin configuration can lock the tables. There are 2 common issues that prevent the user locking the tables:

• user does not have LOCK_TABLE privilege - http://dev.mysql.com/doc/refman/5.1/en/privileges-provided.html#priv_lock-tables
• another application or process has an exclusive lock on the table preventing NetVault from accessing it.