Repository Verification Takes Too Long

Product version: 11.1

Last modified: 25 March 2026

Problem

A Repository Verification job may take more than 24 hours to complete, even when running on a system with high-performance hardware.

During verification, the process appears to progress very slowly, and CPU utilization remains low despite multiple CPU cores being available.

Background

By default, repository verification may run using a single CPU thread, which can significantly limit performance on systems with multiple CPU cores.

When the repository contains a large amount of backup data, single-threaded verification can result in very long verification times.

Solution

To increase maintenance speed, add more CPU/RAM to the transporter assigned to the repository (if possible).

After that, you can assign more CPU threads for maintenance in the repository configuration file:

  1. Gracefully stop the running maintenance or verification job.

  2. Detach the repository.

  3. Stop the Transporter service.

  4. Navigate to the repository system folder and open the /NakivoBackup directory.

  5. Create a configuration ( .conf) file in this directory.

  6. Edit the file and add the following parameter:

    maintenance.threads=4

  7. (Linux only) Ensure the file has the same owner and permissions as the /NakivoBackup folder:

    chown bhsvc:bhsvc .conf

    chmod 770 .conf

  8. Start the Transporter service.

  9. Attach the repository.

  10. Run the Repository Verification job again.

Notes

  • The optimal number of maintenance threads depends on the available CPU resources and repository workload. In most environments, increasing the number of threads improves verification performance, but excessively high values may increase CPU and disk load.

  • Adjust the parameter based on the available hardware resources and monitor system performance during verification.

  • The maintenance.threads parameter is not available in the user interface and must be configured manually in the config file.