yes, you´re right, i have fixed this, thank you for pointing that out, but
now i have another issue, which i don´t know if it´s related. i open a new
post for that
Bruno Friedmann (bruno-at-bareos) schrieb am Mittwoch, 30. Juli 2025 um
14:58:01 UTC+2:
> Hello Marcus,
>
> I don't think you paid enough attention about your Media Type File versus
> FileCons when they should all the same type to make AI working ;-)
>
>
> On Thursday, 24 July 2025 at 20:32:30 UTC+2 Markus Dubois wrote:
>
>> i´m still struggling. After running a consolidate job , a virtual full
>> kicks in automatically afterwards, but breaks after a few minutes:
>>
>>
>> bareos-dir JobId 53: Replicating deleted files from jobids
>> 1,6,9,11,13,16,20 to jobid 53
>>
>> 17
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Releasing device "FileStorageCons1"
>> (/var/lib/bareos/storage).
>> 16
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Releasing device "FileStorageCons1"
>> (/var/lib/bareos/storage).
>> 15
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Fatal error: stored/acquire.cc:206 No suitable device
>> found to read Volume "AI-Consolidated-0001"
>> 14
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Releasing device "FileStorage"
>> (/var/lib/bareos/storage).
>> 13
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: stored/acquire.cc:156 Changing read device. Want
>> Media Type="FileCons" have="File"
>> device="FileStorage" (/var/lib/bareos/storage)
>> 12
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Ready to append to end of Volume
>> "AI-Consolidated-0613" size=234
>> 11
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Moving to end of data on volume "AI-Consolidated-0613"
>> 10
>> 2025-07-24 20:26:38
>> bareos-dir JobId 53: Using Device "JustInTime Device" to write.
>> 9
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Using just in time reservation for job 53
>> 8
>> 2025-07-24 20:26:38
>> bareos-dir JobId 53: Using Device "FileStorage" to read.
>> 7
>> 2025-07-24 20:26:37
>> bareos-dir JobId 53: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
>> 6
>> 2025-07-24 20:26:37
>> bareos-dir JobId 53: Connected Storage daemon at 192.168.188.31:9103,
>> encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
>> 5
>> 2025-07-24 20:26:37
>> bareos-dir JobId 53: Consolidating JobIds 1,6,9,11,13,16,20 containing
>> 6426160 files
>> 4
>> 2025-07-24 20:26:37
>> bareos-dir JobId 53: Bootstrap records written to
>> /var/lib/bareos/bareos-dir.restore.3.bsr
>> 3
>> 2025-07-24 20:24:01
>> bareos-dir JobId 53: Start Virtual Backup JobId 53,
>> Job=AIbackup-omvserver.2025-07-24_20.23.59_29
>> 2
>> 2025-07-24 20:24:01
>> bareos-dir JobId 53: shell command: run BeforeJob
>> "/var/lib/bareos/scripts/jobcheck.sh"
>> 1
>> 2025-07-24 20:24:01
>> bareos-dir JobId 53: Version: 24.0.5~pre13.8f151fe4c (14 July 2025)
>> Ubuntu 22.04.5 LTS
>> Zeige Zeile 1 bis 18 von 18 Zeilen. Zeilen pro Seite.
>> ____
>>
>> the interesting part of the log is:
>>
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Fatal error: stored/acquire.cc:206 No suitable device
>> found to read Volume "AI-Consolidated-0001"
>> 14
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: Releasing device "FileStorage"
>> (/var/lib/bareos/storage).
>> 13
>> 2025-07-24 20:26:38
>> bareos-sd JobId 53: stored/acquire.cc:156 Changing read device. Want
>> Media Type="FileCons" have="File"
>> device="FileStorage" (/var/lib/bareos/storage)
>>
>> don´t know why the virtual full has difficulties to access the storage
>> when everything is fine as long as it is not virtual
>> Markus Dubois schrieb am Mittwoch, 2. Juli 2025 um 17:12:58 UTC+2:
>>
>>> no, of course i have tried a rerun (because i didn´t know this, ehat
>>> you´ve said above), but on every daily schedule the bareos now tries a
>>> Virtual Full, so nothing manual there.
>>> The first failed Virtual was also a scheduled or automatically happening
>>> run, because of this setting:
>>>
>>> Max Virtual Full Interval = 14 days
>>>
>>> So this was triggered trough this setting and gets now triggered every
>>> day and failing everytime.
>>> My questions remain:
>>> 1.) Why is this happening in the first place?
>>> 2.) if there is a "fix" like you described above (consolidated run),
>>> then what needs to be done to prevent this in the future?
>>>
>>> Bruno Friedmann (bruno-at-bareos) schrieb am Dienstag, 1. Juli 2025 um
>>> 13:03:27 UTC+2:
>>>
>>>> If you tried a rerun that's normal and expected and documented.
>>>> If you want to reschedule a AI job, you have to rerun the consolidation
>>>> job which is the only one to know which jobs needs to be consolidated.
>>>>
>>>>
>>>> On Tuesday, 1 July 2025 at 12:58:32 UTC+2 Markus Dubois wrote:
>>>>
>>>>> i have this job config:
>>>>>
>>>>> Job {
>>>>> Name = "AIbackup-omvserver"
>>>>> Client = "omvserver"
>>>>> FileSet = omvserver
>>>>> Type = Backup
>>>>> Level = Incremental
>>>>> Schedule = "AISchedule"
>>>>> Storage = File
>>>>> Priority = 50
>>>>> Messages = Standard
>>>>> Pool = AI-Incremental
>>>>> Spool Attributes = yes
>>>>> Maximum Concurrent Jobs = 1
>>>>> Full Backup Pool = AI-Consolidated
>>>>> Incremental Backup Pool = AI-Incremental
>>>>> Accurate = yes
>>>>> Allow Mixed Priority = no
>>>>> Allow Duplicate Jobs = no
>>>>> Always Incremental = yes
>>>>> Always Incremental Job Retention = 7 days
>>>>> Always Incremental Keep Number = 7
>>>>> Always Incremental Max Full Age = 11 days
>>>>> Max Virtual Full Interval = 14 days
>>>>> Run Script {
>>>>> Console = ".bvfs_update jobid=%i"
>>>>> RunsWhen = After
>>>>> RunsOnClient = No
>>>>> }
>>>>> }
>>>>>
>>>>> i have these running jobs:
>>>>>
>>>>> jobid | name | level | jobstatus | starttime
>>>>> -------+--------------------+-------+-----------+---------------------
>>>>> 70 | AIbackup-omvserver | f | f | 2025-07-01 12:37:21
>>>>> 69 | AIbackup-omvserver | f | f | 2025-07-01 12:36:23
>>>>> 68 | AIbackup-omvserver | f | f | 2025-07-01 12:35:47
>>>>> 67 | AIbackup-omvserver | f | f | 2025-07-01 12:28:58
>>>>> 62 | AIbackup-omvserver | I | T | 2025-06-29 19:00:04
>>>>> 64 | AIbackup-omvserver | f | f | 2025-06-29 19:00:04
>>>>> 59 | AIbackup-omvserver | I | T | 2025-06-28 19:00:04
>>>>> 55 | AIbackup-omvserver | I | T | 2025-06-26 19:00:05
>>>>> 51 | AIbackup-omvserver | I | T | 2025-06-25 19:00:04
>>>>> 47 | AIbackup-omvserver | I | T | 2025-06-24 19:00:04
>>>>> 43 | AIbackup-omvserver | I | T | 2025-06-23 19:27:03
>>>>> 39 | AIbackup-omvserver | I | T | 2025-06-16 19:00:04
>>>>> 36 | AIbackup-omvserver | F | T | 2025-06-15 19:00:02
>>>>> 37 | AIbackup-omvserver | I | A | 2025-06-15 19:00:00
>>>>> 23 | RestoreFiles | F | T | 2025-06-12 08:31:25
>>>>> 3 | AIbackup-omvserver | F | A | 2025-06-06 19:00:01
>>>>> 1 | AIbackup-omvserver | F | T | 2025-06-06 09:15:00
>>>>>
>>>>> But my virtual full fails because it doesn´t see the jobs:
>>>>>
>>>>> bareos-dir JobId 70: Error: Bareos bareos-dir 24.0.4~pre21.6a9d93652
>>>>> (03Jun25):
>>>>> Build OS: Ubuntu 22.04.5 LTS
>>>>> JobId: 70
>>>>> Job: AIbackup-omvserver.2025-07-01_12.37.19_11
>>>>> Backup Level: Virtual Full
>>>>> Client: "omvserver" 24.0.4~pre21.6a9d93652 (03Jun25) Ubuntu 22.04.5
>>>>> LTS,ubuntu
>>>>> FileSet: "omvserver" 2025-06-06 09:14:58
>>>>> Pool: "AI-Consolidated" (From Run NextPool override)
>>>>> Catalog: "MyCatalog" (From Client resource)
>>>>> Storage: "FileCons" (From Storage from Run NextPool override)
>>>>> Scheduled time: 01-Jul-2025 12:37:19
>>>>> Start time: 01-Jul-2025 12:37:21
>>>>> End time: 01-Jul-2025 12:37:21
>>>>> Elapsed time: 0 secs
>>>>> Priority: 50
>>>>> Allow Mixed Priority: no
>>>>> SD Files Written: 0
>>>>> SD Bytes Written: 0 (0 B)
>>>>> Rate: 0.0 KB/s
>>>>> Volume name(s):
>>>>> Volume Session Id: 0
>>>>> Volume Session Time: 0
>>>>> Last Volume Bytes: 0 (0 B)
>>>>> SD Errors: 0
>>>>> SD termination status:
>>>>> Accurate: yes
>>>>> Bareos binary info: Bareos community build (UNSUPPORTED): Get
>>>>> professional support from https://www.bareos.com
>>>>> Job triggered by: User
>>>>> Termination: *** Backup Error ***
>>>>>
>>>>> 4 2025-07-01 12:37:21 bareos-dir JobId 70: Fatal error: No previous
>>>>> Jobs found.
>>>>> 3 2025-07-01 12:37:21 bareos-dir JobId 70: Error: Cannot run always
>>>>> incremental job at level VirtualFull with no jobid list.
>>>>> 2 2025-07-01 12:37:21 bareos-dir JobId 70: Start Virtual Backup JobId
>>>>> 70, Job=AIbackup-omvserver.2025-07-01_12.37.19_11
>>>>> 1 2025-07-01 12:37:21 bareos-dir JobId 70: Version:
>>>>> 24.0.4~pre21.6a9d93652 (03 June 2025) Ubuntu 22.04.5 LTS
>>>>>
>>>>> how to troubleshoot this?
>>>>
>>>>
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/b0adde8e-a022-4154-b2b9-29e0694a50een%40googlegroups.com.
