Troubleshooting errors for the NetBackup for MySQL Agent

To troubleshoot the errors, you can refer to the NetBackup logs.

The NetBackup primary server 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 client are located at:

install_path\netbackup\logs\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 NetBackup Troubleshooting Guide and the 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 library path is not provided in the nbmysql command using the "-l" switch or the library path is provided but it does not contain `libmysql.so` (Linux) or `libmysql.dll` (Windows).	Verify the following and then run the backup again: Ensure that you provide the correct mysql library path, which contains the `libmysql.so` (Linux) or `libmysql.dll` (Windows) file. (Linux) If `libmysql.so` is not available, create a symbolic link named `libmysql.so` that points to `libmysql.so.<n>`. (Windows) If `libmysql.dll` is not available under bin directory of the mysql installation location, it may be available under lib directory.
The nbysql backup fails with the following error message: Unable to connect to the database	The mysql backup fails when the nbmysql command is run with invalid database user name, port number, or password.	Provide the database user name using the "-u" switch of the nbmysql command. Provide the database port number using the "-portnum" switch of nbmysql command. Provide the database password using the `my.cnf` (Linux) or `my.ini` (Windows) file. See Authenticating the MySQL environment password.
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 required parameters are not specified on the command line.	To run the NetBackup backup successfully: Configure the valid primary server name, policy name, schedule type from the command line. For more information, Verify if there are communication errors between the agent and the NetBackup primary server. For more information see the NetBackup Administrator's Guide Volume I.
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 Provide 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 NetBackup client name is not updated.	Add or update the NetBackup client name. For more information,
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 version from the backed up data is same as the MySQL version on the computer where you want to restore the data.

Troubleshooting errors for the NetBackup for MySQL Agent

Feedback

Feedback