Volume Error Issue in Bacula Backup System

[Meth]

Hi everyone, I'm experiencing issues with volume errors in my Bacula setup. When trying to run a PostgreSQL backup job, all volumes are being marked as "Error in Catalog" and the job cannot find any appendable volumes. Environment: - Bacula Enterprise - PostgreSQL backup job - Storage: FileChgr1-Dev1 (/opt/bacula/archive) - Pool: Default - Media Type: File1 Error logs: bacula-dir JobId 765: Start Backup JobId 765, Job=FigoTestPsql_DB.2024-12-20_15.35.05_07 bacula-dir JobId 765: Connected to Storage "BackupServer-101-FileChgr1" at 10.2.80.101:9103 with TLS bacula-dir JobId 765: Using Device "FileChgr1-Dev1" to write. bacula-dir JobId 765: Connected to Client "FigoTest-fd" at 10.2.41.58:9102 with TLS figodb-test-fd JobId 765: Connected to Storage at 10.2.80.101:9103 with TLS backupserver101-sd JobId 765: Marking Volume "FigoPgTest-001" in Error in Catalog. backupserver101-sd JobId 765: Marking Volume "test" in Error in Catalog. backupserver101-sd JobId 765: Job FigoTestPsql_DB.2024-12-20_15.35.05_07 is waiting. Cannot find any appendable volumes. Please use the "label" command to create a new Volume for: Storage: "FileChgr1-Dev1" (/opt/bacula/archive) Pool: Default Media type: File1
What I've tried so far: 1. Created new volumes with proper labels 2. Checked storage directory permissions 3. Verified bacula user permissions Questions: 1. What could be causing all volumes to be marked as "Error in Catalog"? 2. Are there specific permission requirements I should check? 3. How can I properly diagnose the root cause of this issue? Any help or guidance would be greatly appreciated. Best regards,

[Marcin Haba]

On Fri, 20 Dec 2024 at 13:38, Meth <bys...@gmail.com> wrote:
>
> Hi everyone, I'm experiencing issues with volume errors in my Bacula setup. When trying to run a PostgreSQL backup job, all volumes are being marked as "Error in Catalog" and the job

Hi Meth,

In this job log part there is not any message why this error happens.
If in the whole job log there is not anything more about this error,
then I would propose to enable debugging for SD and Director.

In Bconsole for example:

setdebug level=400 trace=1 storage=xxxxx-sd
setdebug level=400 trace=1 dir

and after please run this job again.

In the Director and Storage Daemon working directory you will find
files with debug:

xxxxx-sd.trace

xxxxx-dir.trace

After that you can disable debug by setting level=0 in the setdebug commands.

Are you seeing anything wrong in the debug files?

Best regards,
Marcin Haba (gani)

[Marcin Haba]

Hi Meth,

One more thing. In case Bacula Enterprise it is closed source software
that I am not able to support. In this case you will need to contact
the Bacula Systems support team.

Best regards,
Marcin Haba (gani)