Troubleshooting errors for the NetBackup for MySQL Agent

To troubleshoot problems, you can refer to the logs that are specific to NetBackup for MySQL Agent, NetBackup XBSA, or set the verbose logging levels in the nbmysql.conf file. The logs are located at the following locations:

The NetBackup logs are located at:

install_path\NetBackup\logs\bprd
install_path\NetBackup\logs\bpcd
install_path\NetBackup\logs\user_ops\dbext\logs

The logs that are specific to NetBackup for MySQL Agent is located at:

install_path\nbmysql.log

The logs that are specific to NetBackup XBSA is located at:

<NetBackup_install_path>/netbackup/logs/exten_client.

Preliminary steps

Verify the following, before you troubleshoot the problems:

All the prerequisites are completed.
All the computers have compatible operating system versions.
The debug logs and reports are verified for errors.

Troubleshooting NetBackup problems

For troubleshooting NetBackup problems, refer to the Veritas NetBackup Troubleshooting Guide and the Veritas NetBackup Commands Reference Guide.

Troubleshooting NetBackup for MySQL operations

Table: Troubleshooting NetBackup for MySQL backups and restores

Problems	Description	Solution
The nbmysql backup fails with the following error: An error has occurred during backup	The nbmysql backup may fail for any of the following reasons: The NetBackup media server or client runs on NetBackup 8.0 or earlier versions. The check box for Enable in secure communication with NetBackup8.0 and earlier hosts is disabled The NetBackup host ID certificate that exists on the MySQL client is invalid.	For a successful backup, complete any of the following: Upgrade the media server or client to use NetBackup 8.1 or later versions. In NetBackup Administration Console, under Security Management > Global Security Settings, select the Enable in secure communication with NetBackup 8.0 and earlier hosts check box. Verify the NetBackup host ID certificate. You can manually obtain the host ID certificate. For more information, see www.veritas.com/support/en_US/article.000127129
The nbmysql agent fails to initiate any operation.	The MySQL agent displays an error that is related to absence of the `I18N` file. You may encounter this problem when you launch the agent.	When the agent fails to initiate operations due to absence of the `I18N` file, copy the language file in the agent installer location and then run the operations.
The nbmysql backup fails with the following error: Unable to load MySQL library	You may encounter this problem when the `nbmysql.conf` file is not updated with the following: The MySQL library file location. The MYSQL_LIB_INSTALL_PATH does not point to `libmysqlclient.so.<n>`	Verify the following and then run the backup again: Add or update the MySQL library file location in the `nbmysql.conf` file. For more information, See The nbmysql configuration file. Ensure that the MYSQL_LIB_INSTALL_PATH is set to the absolute path of the symbolic link. Create a symbolic link `libmysqlclient.so` that points to the `libmysqlclient.so.<n>` version. For more information, See Post-installation requirements for NetBackup for MySQL Agent .
The nbysql backup fails with the following error message: Unable to connect to the database	The nbmysql backup fails if the `nbmysql.conf` includes an invalid database user name and the port number.	To add the appropriate database user name and port number Configure the appropriate database user name and port number in the `nbmysql.conf` file or provide the appropriate options with the nbmysqlcommand. For more information, See The nbmysql configuration file. If the backup fails again, verify if the MySQL services are running.
The nbmysql backup fails with the following error: Unable to load xbsa.dll	The nbmysql backup fails if the environment variable path is not updated with NetBackup bin directory.	To run a MySQL backup successfully Update the environment variable path with `NetBackup_install_path/bin`.
The nbmysql backup fails with the following error: XBSA initiation failed	The nbmysql backup fails if the `nbmysql.conf` file is not updated with the required parameters.	To run the NetBackup backup successfully Configure the valid master server name, policy name, schedule type in the `nbmysql.conf` file or from the command line. For more information, See The nbmysql configuration file. Verify if there are communication errors between the agent and the NetBackup master server. For more information see the NetBackup Administration guide.
The nbmysql backup on Linux (LVM), fails with the following error: Error unmounting the snapshot-Device or resource busy OR Error removing the snapshot-mysqlsnap_<timestamp> Note: <timestamp> is the LVM snapshot time	The nbmysql backup fails during an attempt to unmount the snapshot, the device, or when you remove the existing snapshots.	To unmount the snapshot List all mounted file systems using the following command: $ mount-l If the snapshot still exists, create a mount directory using the following command: $mount<mount_directory> Note: This directory is created in `/mnt/<snapshot_name>`. The prefix names for snapshot are `mysqlsnap`. To remove the mount directory run the following command: $rm -rf <mount_directory> To remove the snapshot manually run the following command: 1vremove -f <volume_group>/<snapshot_name>
Error messages after a successful backup: <volume_group>/<snapshot_name> Read failure after 0 of 4096 at 29393616896: input or output error. OR <volume_group>/<snapshot_name>: read failure after 0 of 4096 at 4096: input or output error.	The nbmysql backup gives these errors when the volume group contains the snapshots. You can list the snapshots and then remove them before you run the backup again.	To remove the snapshots Run the following command to list the existing snapshots:: $lvs The command displays the snapshot details. Run the following command to delete the snapshots: $ lvremove -f <volume_group>/<snapshot_name>
The nbmysql backup fails with the following error: (Linux)Error creating LVM snapshot	The nbmysql backup may fail when the volume group does not have sufficient space for the snapshot.	To verify the space in the volume group Run the following command to view the volume group details: $vgs Update the `nbmysql.conf` file with the appropriate snapshot size. Verify that the snapshot is equivalent to or more than the instance size.
(Windows)VSS snapshot creation failed	The nbmysql backup may fail when the user does not have the privileges to run the nbmysql operations.	Run cmd.exe in Administrator mode.
The nbmysql restore operation does not restore any data from the target NetBackup client.	The nbmysql restore fails if the `nbmysql.conf` file is not updated with the NetBackup client name.	Add or update the NetBackup client name in the `nbmysql.conf` file. For more information, See The nbmysql configuration file.
The nbmysql restore is unsuccessful when you trigger from the target client.	The nbmysql restore fails if the target directory is invalid or not empty for restores. The restore may also fail, when you initiate a redirected restore from the NetBackup target client instead of the NetBackup source client.	For a successful restore Verify that the target directory is a valid and empty. Initiate the restore from the NetBackup source client.
Exception error during backups and restores.	The nbmysql restores and backups fail, if the disk space is not sufficient for the restore and backups.	Verify that the disk space is larger than the MySQL database and then initiate backups or restores. Note: Approximately 50% of space more than the MySQL database is required for restores and backups.
Even after a successful restore, the MySQL services, failed to start.	The restore operation is successful, only when you restore the backup on a machine that has the same minor version of MySQL. For example, if you back up a file from MySQL version 5.5.x, then you must restore the file to a computer with MySQL version 5.5.x.	Verify that the MySQL agent and NetBackup are of same version for successful restore operations. Verify that the MySQL version from the backed up data is same as the MySQL version on the computer where you want to restore the data.
The `nbmysql.conf` file is missing after installing the agent on RHEL or SUSE	Starting from NetBackup 8.2, the `nbmysql.conf` file is not created by default when you install the agent on RHEL or SUSE. The existing configuration file is prevented from getting overwritten as the RPM installer simply overwrites any existing files in the destination directory `/usr/NBMySQLAgent/.`	If the `nbmysql.conf` file does not exist, you can create the file by running the backup utility command without any options. For example, `./nbmysql`. This command creates the default `nbmysql.conf` file.

Troubleshooting errors for the NetBackup for MySQL Agent

Feedback

Feedback