Troubleshooting

Troubleshooting#

Introduction#

Troubleshooting Restore Verification can be divided into three levels. The following sections describe each level and the recommended diagnostic steps.

Level 1: Check the job log#

If a Restore Test fails, the first place to check is the corresponding job log.

For Rule-based Verification, check the Restore Job log. For Native Bacula Verify, check the Verify Job log.

The job log usually contains information explaining why the Restore Test failed. Typical causes include the following.

1. Verification condition failed#

One or more individual verification checks may have failed.

Compare the expected value with the actual value reported by the checker. This should help you understand why the verification condition did not pass.

If the values differ because the restored data does not match what you expected, the Restore Test has fulfilled its primary purpose by detecting a data inconsistency.

If the values differ because the verification criteria were configured incorrectly, update the corresponding Verification Rules and run the test again.

2. Restore or Bacula infrastructure failed#

The failure may not be related to an individual verification condition, but instead to the restore operation or one of the Bacula components involved in the workflow.

Review all error messages in the job log and identify which Bacula component they refer to, such as:

  • Director,

  • Storage Daemon,

  • File Daemon.

Use these messages to determine whether the problem is related to backup media availability, client connectivity, storage access, restore processing, or another Bacula operation.

Level 2: Check the Audit log#

Restore Verification records its errors and warnings in the Bacularis Audit log.

Important

To troubleshoot Restore Verification effectively, make sure that the Action category is enabled in the Audit log settings. At minimum, enable the Warning and Error log types, as some Restore Verification messages are recorded there.

You can find the Audit log in the Bacularis web interface at:

[Application settings] => [Tab: Audit log]

In some cases, the job log checked in Level 1 may contain a message telling you to review the Bacularis logs.

For example:

darkstar-dir JobId 62987: BeforeJob: [ERROR] Error while starting restore test.
URL: https://192.168.1.32:9097/web/access/<token>,
HTTP Code: 200, Error: 0,
Body: {"error":5,"message":"Action failed. See logs."}

A message such as:

Action failed. See logs.

usually means that the Web Access request reached Bacularis successfully, but the requested Restore Verification action failed internally.

In such cases, check the Audit log for additional details about the failure.

Level 3: Enable debug mode#

If the information from Level 1 and Level 2 is not sufficient to identify the source of the problem, consider enabling Debug mode in Bacularis API and Bacularis Web.

More information about enabling Debug mode is available here: Troubleshooting

The most useful debug logs for Restore Verification troubleshooting are:

  • protected/Web/Logs/bacularis-web.log – web interface debug information,

  • protected/API/Logs/bacularis-api.log – API operations and communication,

  • protected/Common/Working/bacularis-bacula-console.log – Bacula console commands and responses.

Disable Debug mode after troubleshooting is complete to avoid unnecessary log growth and excessive diagnostic output.

I did not find a solution. What next?

If you are unable to resolve a Restore Verification problem, you are welcome to join the Bacularis community on the official Bacularis User Group forum:

https://group.bacularis.app

You can ask questions there and get help from other users and the Bacularis community.

When reporting a Restore Verification problem, please include as much relevant information as possible, such as:

  • Restore Test name,

  • verification method,

  • relevant JobId,

  • relevant job log,

  • Audit log entry,

  • Bacularis version,

  • Bacula version,

  • debug logs, if available.

Contents