Backup Troubleshooting - MySQL iDataAgent

Backup Restore  
Table of Contents

MSQL0001: MySQL instance creation fails

Symptom 1

Invalid username and password error is displayed while configuring the MySQL instance. MySQL commands fail with 'GCC_4.2.0' not found (required by /usr/lib64/libstdc++.so.6) error.

Error Code 87:1
Invalid MySQL User Name and Password.

Cause

The instance creation fails if the libgcc_s.so.1 library included with the SnapProtect software is not compatible with the newer operating system version that it is installed on.

Resolution

Use the following commands to rename /opt/snapprotect/Base/libgcc_s.so.1:

# cd /opt/snapprotect/Base
# mv /opt/snapprotect/Base/libgcc_s.so.1 /opt/SnapProtect/Base/libgcc_s.so.1.old
# snapprotect restart

Create the instance again.

Symptom 2

MySQL instance creation fails when using older MySQL 5.5.x versions or earlier and displays the following error message.

Port wrong error

Cause

The instance creation fails because the Mysqladmin utility crashes as the -defaults- file does not have the required .ini or .cnf file extensions.

Resolution

Upgrade the MySQL 5.5.x version to the latest available version.

Create the instance again.

MSQL0003: MySQL backup operation fails with lost connection error

MySQL backup operation fails and displays the following error message.

Backup fail with: Mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table.

Cause 1

The backup operation fails if the value that is set for max_allowed_packet variable is insufficient to allow the transfer of packets.

Resolution 1

Set the value for the max_allowed_packet variable as 1GB in the MySQL server.

However, you can set a different value for the client by configuring the value for sAdvancedBackupOptions.

The value set on the client is given priority over the one set on MySQL server.

Cause 2

The backup operation fails if the value set for connect_timeout variable is low. The timeout variable refers to the number of seconds that the MySQL server waits for a connect packet before responding with a bad handshake.

Resolution 2

Increase the value for the connect_timeout variable on the MySQL server to 100.

Cause 3

The backup operation fails if the memory size required to dump the BLOB (Binary Large Object) is less. The memory size depends on the RAM usage of the server.

Resolution 3

Increase the memory size.

MSQL0004: MySQL backup operation fails after upgrading the SnapProtect software from version 9 to the current version

MySQL backup operation fails with the following error message.

Please use mysql_upgrade to fix this error. (1558)

Cause

After upgrading the software from version 9 to the current version, the backup operation fails due to the addition of "--routines" flag with mysqldump utility. Earlier versions of the software did not support "--routines" flag with mysqldump utility.

The following entries appear in the backup log file:

/opt/simpana/iDataAgent/jobResults/2/386/pipe711274_18320 out = err = mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'dci_gateway': Column count of mysql.proc is wrong. Expected 20, found 16. Created with MySQL 50152, now running 50169. Please use mysql_upgrade to fix this error. (1558)

Resolution

Run the following command to fix this issue.

mysql_upgrade -uroot -p

MSQL0005: First, full or log-only backup operation fails

MySQL backup operation fails with the following error message.

3932 123c 06/28 13:56:17 1085 mysqlLogBackup:ArchiveLogs() - log file(D:\MySQL\MySQL Server 5.6\data\UC-MYSQL-01-bin.000014) is missing, So converting the log backup to full backup

Cause 1

The backup operation fails after changing the instance properties. Same or different directories may be used for data (datadir) and log file (log data directory) generation. This problem occurs when different directories are set, but the user provides the same datadir path for generating log files.

For example,

Windows:

datadir = D:\MySQL\MySQL Server 5.6\data

Log Data Directory = D:\MySQL\MySQL Server 5.6\binlog\UC-MYSQL-01-bin.log

UNIX:

datadir = /var/lib/mysql

Log Data Directory = /var/log/mysql

Here, different paths are set for data and log file generation. If the user specifies datadir path for Log Data Directory in the instance properties from the CommCell Console, the error is generated.

Resolution 1

From the CommCell Console, change the path for Log Data Directory in the instance properties.

Cause 2

The backup operation fails if the MySQL server has binary logging enabled with number of days set for expire_log_days. The backup operation fails to back up the log files as they are expired and were deleted from the server (base on the number of days set for expire_log_days).

For example,

In my.ini or my.cnf file, if the number of days set for expire_log_days is 10, then the logs expire after 10 days. If there is a backup operation, then it will fail as there are no logs to back up.

Resolution 2

Use any one of the following methods to resolve this issue:

  • Increase the number of days set for expire_log_days to a value that is adequate to back up the log files.
  • Do not set a value for expire_log_days.

MSQL0007: MySQL backup operation fails if the physical node is uninstalled from the cluster group and then reinstalled

Cause

MySQL backup operation fails because the reinstalled physical node is not added automatically to the cluster group.

Resolution

To run the backup operation successfully, follow these steps to manually add the node and force a synchronization.

  1. From the CommCell Browser, right-click the <Cluster Group Client> node, and then click Properties.
  2. In the Client Computer Properties dialog box, click Advanced.
  3. Click the Cluster Group Configuration tab.
  4. Select the reinstalled physical node from the Available list and click Add > to add it to the Selected list.
  5. Select the Force Sync Configuration on Remote Nodes check box.
  6. Click OK.
  7. Run the backup operation.

Completed with one or more errors

Backup jobs from MySQL iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

  • If the subclient contains multiple databases, and some of the database backups encounter errors and other database backups run successfully.

  • If the subclient contains multiple databases, and some databases in the subclient are corrupted or removed from the database server.

Error Code [19:1109] Backup goes into pending state with MySQL error

A backup operation for MySQL databases goes into pending state with the following error in the MySqlBackup.log file:

ERROR 1524 (HY000): Plugin '*2304CA809SD20C634G898FCE11C167F21663318A' is not loaded ret = -1

You can also see the following error in the error log of MySQL Server:

The plugin '*2304CA907AD20C629F898FCE11C167F21663318A' used to authenticate user 'MySQL.Backup'@'%' is not loaded.

Cause

A wrong value is set for the plug-in on the MySQL Server.

Resolution

To set the correct value for MySQL plug-in, from the MySQL Server, run the following command:

update mysql.user set plugin=<plugin_value> where user=<username>

For example:

update mysql.user set plugin='mysql_native_password' where user='user1'