Veritas NetBackup™ for MariaDB Administrator's Guide

Last Published:
Product(s): NetBackup (8.3)

Troubleshooting errors when using NetBackup for MariaDB

General guidelines to resolve problems

Table: General steps to resolve problemslists the general steps that help you resolve problems you may encounter while using NetBackup for MariaDB Agent.

Table: General steps to resolve problems

Steps

Action

Description

Step1

Remember the error message

Error messages are usually the vehicles for telling you something went wrong. If you do not see an error on the command line, but still suspect a problem, check the logs and the reports. These can provide an error message that directly points to the problem. The logs and reports are essential troubleshooting tools.

Step 2

Identify what you were doing when the problem occurred.

Ask the following questions:

  • What operation was tried?

  • What method did you use?

  • What type of server platform and operating system was involved?

  • If your site uses both master server and media server, was it a master server or a media server?

  • If a client was involved, what type of client was it?

  • Have you performed the operation successfully in the past? If so, what is different now?

  • What is the service pack level?

  • Do you use operating system software with the latest fixes supplied, especially those required for use with NetBackup?

  • Is your device firmware at a level, or higher than the level, at which it has been tested according to the posted device compatibility lists?

Step 3

Record all information.

Capture potentially valuable information:

  • The NetBackup logs.

  • The logs specific to NetBackup for MariaDB logs.

  • The logs specific to NetBackup XBSA .

Step 4

Correct the problem.

After you define the problem, use the information to correct it.

Step 5

Contact Technical Support

If you cannot solve the troubleshooting, contact the Technical support.

Troubleshooting errors using logs

To troubleshoot the errors, you can refer to the NetBackup logs, NetBackup for MariaDB Agent logs, and the NetBackup XBSA logs. These 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

You must enable the bprd and the bpcd log files. For more information, see the NetBackup Troubleshooting Guide

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

  • install_path\nbmariadb.log

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

  • <NetBackup_install_path>/netbackup/logs/exten_client

Troubleshooting NetBackup errors

For troubleshooting NetBackup errors, see Veritas NetBackup Troubleshooting Guide and the Veritas NetBackup Commands Reference Guide

Troubleshooting NetBackup for MariaDB Agent errors

Table: Troubleshooting NetBackup for MariaDB errors lists the errors and the solutions to troubleshoot the problems while running the operations.

Table: Troubleshooting NetBackup for MariaDB errors

Problems

Description

Solution

The nbmariadb backup fails with the following error:

Unable to load mariadb library

You may encounter this problem when the nbmariadb.conf file is not updated with the following:

  • MARIADB_LIB_INSTALL_PATH

  • MARIADB_LIB_INSTALL_PATH does not point to libmariadb.so.<n> library version.

Verify the following and then run the backup again:

  • Add or update the MariaDB library file location in the nbmariadb.conf file.

  • Ensure that the MARIADB_LIB_INSTALL_PATH is set to the correct path. It should point to libmariadb library version.

  • (Linux) Create a symbolic link libmariadb.so that points to the libmariadb.so.<n> library version.

The nbmariadb backup fails with the following error:

Unable to connect to the database

The nbmariadb backup fails when the nbmariadb.conf file is updated with invalid username or port number.

To add the appropriate database user name and port number

  • Configure the appropriate database user name and port number in the nbmariadb.conf file or provide the parameters from the nbmariadbcommand line.

    For more information, See The nbmariadb.conf configuration file.

The nbmariadb backup fails with the following error:

Unable to load xbsa.dll

The nbmariadb backup fails if the environment variable path is not updated with NetBackup bin directory.

To run a nbmariadb backup

  • Update the environment variable path with NetBackup_install_path/bin.

The nbmariadb backup fails with the following error:

XBSA initiation failed

The nbmariadb backup fails if the nbmariadb.conf file is not updated with the required parameters.

To run the nbmariadb backup

  • Configure the valid master server name, policy name, schedule type in the nbmariadb.conf file or from the command line.

  • Verify if there are communication errors between the nbmariadb agent and the NetBackup master server.

    For more information see the NetBackup Administration guide.

(Windows)VSS snapshot creation failed

The nbmariadb backup may fail when the user does not have the privileges to run the nbmariadb operations.

Run cmd.exe in Administrator mode.

The nbmariadb restore operation does not restore any data from the target NetBackup client.

The nbmariadb restore fails if the nbmariadb.conf file is not updated with the NetBackup client name and the target directory.

For a successful restore

  • Verify that the target directory is valid and empty.

  • Initiate the restore from the NetBackup source client.

  • Set the NetBackup client name and target directory parameters in the nbmariadb.conf file.

The nbmariadb backup fails with the following error:

(Linux) Error creating LVM snapshot

The nbmariadb backup may fail when the volume group does not have sufficient space for the snapshot.

To verify the space in the volume group

To verify the space in the volume group

  1. To view the space in the volume, run the following command:

    $vgs

    The command displays the volume group details.

  2. Update the nbmariadb.conf file with the appropriate snapshot size. The snapshot should be equivalent to or more than the instance size.

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 nbmariadb 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.

Note:

The nbmariadb created LVM snapshot names are prefixed with mariadbsnap

To remove the snapshots

  1. To list the existing snapshot, run the following command:

    $lvs

    The command displays the snapshot details.

  2. To remove the snapshots, run the following command:

    $ lvremove -f <volume_group>/<snapshot_name>

The nbmariadb backup fails with the following error:

"Failed to load MariaDB Library"

You may encounter this problem when the nbmariadb.conf file is not updated with the following:

  • MariaDB library file location.

  • The MARIADB_LIB_INSTALL_PATH does not point to libmariadb.so.<n>

Verify the following and then run the backup again:

The nbmariadb backup on Linux (LVM), fails with the following error:

Error unmounting the snapshot-Device or resource busy

OR

Error removing the snapshot-mariadbsnap_<timestamp>

The nbmariadb backup fails during an attempt to unmount the snapshot, the device, or when you remove the existing snapshots.

To unmount the snapshot

  1. To list all mounted file systems run the following command:

    $ mount-l

  2. 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 pgsqlsnap.

  3. To remove the mount directory run the following command:

    $rm -rf <mount_directory>

  4. To remove the snapshot manually run the following command:

    1vremove -f <volume_group>/<snapshot_name>

Even after a successful restore, the MariaDB 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 MariaDB.

For example, if you back up a file from MariaDB version 10.2.x, then you must restore the file to a computer with MariaDB version 10.2.x.

  • Verify that the MariaDB agent and NetBackup are of same version for successful restore operations.

  • Verify that the MariaDB version from the backed up data is same as the MariaDB version on the computer where you want to restore the data.

The nbmariadb.conf file is missing after installing the agent on RHEL or SUSE

Starting from NetBackup 8.2, the nbmariadb.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/NBMariaDBAgent/.

If the nbmariadb.conf file does not exist, you can create the file by running the backup utility command without any options. For example, run the ./nbmariadb command. This command creates the default nbmariadb.conf file.