Veritas NetBackup™ for SQLite Administrator's Guide

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

Troubleshooting errors when using NetBackup for SQLite Agent

General guidelines to resolve problems

Table: General steps to resolve errors lists the general steps that help you resolve problems you may encounter when using the agent.

Table: General steps to resolve errors





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.


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?


Record all information.

Capture potentially valuable information:

  • The NetBackup logs.

  • The logs specific to NetBackup for SQLite logs.

  • The logs specific to NetBackup XBSA .


Correct the problem.

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


Contact Technical Support

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

Troubleshooting errors using logs

To troubleshoot the errors, you can refer to the NetBackuplogs, NetBackup for SQLite 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 the NetBackup for SQLite Agent are located at:

  • install_path\nbsqlite.log

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

  • <NetBackup_install_path>/netbackup/logs/exten_client

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

Troubleshooting NetBackup for SQLite Agent errors

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

Table: Troubleshooting NetBackup for SQlite errors




The nbsqlite backup fails with the following error:

Unable to load xbsa.dll

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

To run a nbsqlite backup successfully:

  • Update the user environment variable path with NetBackup_install_path/bin.

The nbsqlite backup fails with status code:7648

The backup may fail when the host validation fails for secure connection.

The agent may take some time to terminate the backup operation and display the job status on the nbsqlite command prompt.

Verify that you configure the valid master server name and the host name.

The nbsqlite backup fails with the following error:

XBSA initiation failed

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

To run the backup successfully

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

  • Verify for communication errors between the nbsqlite agent and the NetBackup master server. For more information see the NetBackup Administration guide.

(Windows)VSS snapshot creation failed

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

Run cmd.exe in Administrator mode.

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

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

For a successful restore

  • Initiate the restore from the NetBackup source client.

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

The nbsqlite backup fails with the following error:

(Linux) Error creating LVM snapshot

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

To verify the space in the volume group, use the following command:

  1. $vgs

    The command displays the volume group details.

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

Error messages after a successful backup:

<volume_group>/<snapshot_name> Read failure after 0 of 4096 at 29393616896: input or output error.


<volume_group>/<snapshot_name>: read failure after 0 of 4096 at 4096: input or output error.

The nbsqlite 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

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


    The command displays the snapshot details.

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

    $ lvremove -f <volume_group>/<snapshot_name>

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

Error unmounting the snapshot-Device or resource busy


Error removing the snapshot-sqlitesnap_<timestamp>

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

To unmount the snapshot

  1. List all mounted file systems using the following command:

    $ mount-l

  2. If the snapshot still exists, run the following command:



    This directory is created in /mnt/<snapshot_name>. The prefix names for snapshot is sqlitesnap.

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

    1vremove -f <volume_group>/<snapshot_name>