MySQL backup fails because database can not be locked - "Failed to lock the database instance bef (4046210)

Backups may fail with an error like:
"Failed to lock the database instance before Backup"

MySQL database seems to be locked for writing during backup.

Data may not be inserted into or updated in MySQL ISAM (MyISAM) tables while a backup is running.

1) It is a requirement of MySQL databases implemented with MyISAM tables that the database be locked during backup. This is essential to ensure a consistent backup. NetVault's MySQL plugin is simply adhering to this MySQL requirement.

2) The privileges for the root@localhost user have changed. To test this, deselect the "Local Table" option on the backup options screen and re-run the job, this will result in a different error if privileges are implicated such as:
"SUPER privileges must be available" (the individual privilege required may differ).

1) If tables are locked by another process there is no resolution for this issue if MyISAM tables are used. However, customers may wish to consider replicating the MySQL database/s, then take a backup of the slave instance.

2) If the privileges for the root@localhost user have changed, check that the privilege SUPER (or other indicated privilege) is allocated to the root@localhost user. If not - then reset this privilege.

BakBone SFDC Solution Number: 00000647