Hi,
I have a similar issue during Consolidation in my implementation:
2022-04-15 17:00:04 mcrbckxxx JobId 214: Releasing device "AI-Device-Cons"
(/mnt2/BAREOS).
2022-04-15 17:00:04 mcrbckxxx JobId 214: Fatal error: stored/acquire.cc:217
No suitable device found to read Volume "Test-AI-Cons-0901"
2022-04-15 17:00:04 mcrbckxxx JobId 214: Releasing device "AI-Device-Inc"
(/mnt2/BAREOS).
2022-04-15 17:00:04 mcrbckxxx JobId 214: stored/acquire.cc:158 Changing
read device. Want Media Type="File-Cons" have="File-Inc"
device="AI-Device-Inc" (/mnt2/BAREOS)
2022-04-15 17:00:04 mcrbckxxx JobId 214: Ready to append to end of Volume
"Test-AI-Cons-0903" size=224
2022-04-15 17:00:04 mcrbckxxx JobId 214: Volume "Test-AI-Cons-0903"
previously written, moving to end of data.
2022-04-15 17:00:04 bareos-dir JobId 214: Using Device "AI-Device-Cons" to
write.
2022-04-15 17:00:04 bareos-dir JobId 214: Using Device "AI-Device-Inc" to
read.
2022-04-15 17:00:04 bareos-dir JobId 214: Connected Storage daemon at
10.96.0.18:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
2022-04-15 17:00:04 bareos-dir JobId 214: Bootstrap records written to
/var/lib/bareos/bareos-dir.restore.5.bsr
2022-04-15 17:00:04 bareos-dir JobId 214: Consolidating JobIds
202,205,206,210,211
2022-04-15 17:00:04 bareos-dir JobId 214: Start Virtual Backup JobId 214,
Job=backup-Test-MCR-CL-7499.2022-04-15_17.00.02_18
I think that the problem here is that is trying to read the first Full
backup in the Volume "Test-AI-Cons-0901" which has a different MediaType
than AI-Device-Inc, but I followed the documentation that declare "Full
Backup Pool = AI-Consolidated" in the Job configuration.
Below my configs:
#### SD configurations ####
#/etc/bareos/bareos-sd.d/storage/bareos-sd.conf
Storage {
Name = bckxxx
Maximum Concurrent Jobs = 20
}
#/etc/bareos/bareos-sd.d/device/AI-Device-Inc.conf
Device {
Name = AI-Device-Inc
Media Type = File-Inc
Archive Device = /mnt2/BAREOS
LabelMedia = yes
Random Access = yes
AutomaticMount = yes
RemovableMedia = no
AlwaysOpen = no
Maximum Concurrent Jobs = 1
}
#/etc/bareos/bareos-sd.d/device/AI-Device-Cons.conf
Device {
Name = AI-Device-Cons
Media Type = File-Cons
Archive Device = /mnt2/BAREOS
LabelMedia = yes
Random Access = yes
AutomaticMount = yes
RemovableMedia = no
AlwaysOpen = no
Maximum Concurrent Jobs = 1
}
#### DIRECTOR configurations ####
#/etc/bareos/bareos-dir.d/storage/bckxxx-AI-Inc.conf
Storage {
Name = bckxxx-AI-Inc
Address = *****
Password = "*****"
Device = AI-Device-Inc
Media Type = File-Inc
Maximum Concurrent Jobs = 1
}
#/etc/bareos/bareos-dir.d/storage/bckxxx-AI-Cons.conf
Storage {
Name = bckxxx-AI-Cons
Address = *****
Password = "*****"
Device = AI-Device-Cons
Media Type = File-Cons
Maximum Concurrent Jobs = 1
}
#/etc/bareos/bareos-dir.d/pool/Test-AI-Inc.conf
Pool {
Name = Test-AI-Inc
Pool Type = Backup
Storage = bckxxx-AI-Inc
Recycle = yes
Auto Prune = yes
Volume Retention = 360 days
Maximum Volume Bytes = 50G
Maximum Volumes = 10
Volume Use Duration = 23h
Label Format = "Test-AI-Inc-"
Next Pool = Test-AI-Cons
}
#/etc/bareos/bareos-dir.d/pool/Test-AI-Cons.conf
Pool {
Name = Test-AI-Cons
Pool Type = Backup
Storage = bckxxx-AI-Cons
Recycle = yes
Auto Prune = yes
Volume Retention = 360 days
Maximum Volume Bytes = 50G
Maximum Volumes = 10
Volume Use Duration = 23h
Label Format = "Test-AI-Cons-"
}
#/etc/bareos/bareos-dir.d/jobdefs/Test-DefaultJob.conf
JobDefs {
Name = "Test-DefaultJob"
Type = Backup
Level = Incremental
FileSet = "File-Test"
Messages = Standard
Pool = Test-AI-Inc
Priority = 10
Write Bootstrap = "/var/lib/bareos/%c.bsr"
Full Backup Pool = Test-AI-Cons
Incremental Backup Pool = Test-AI-Inc
}
#/etc/bareos/bareos-dir.d/job/backup-Test-MCR-CL-7499.conf
Job {
Name = "backup-Test-CL-7499"
Client = "CL-7499"
Enabled = no
JobDefs = "Test-DefaultJob"
AlwaysIncremental = yes
AlwaysIncrementalJobRetention = 7 days
Accurate = yes
Schedule = Cons-Test
}
Thanks in advance.
BR,
Luca
Il giorno venerdì 8 aprile 2022 alle 16:56:23 UTC+2 Jan Hebler ha scritto:
> Hi Andreas
>
> Am Freitag, 8. April 2022, 15:55:36 CEST schrieb Andreas Rogge:
> > Hi Jan,
> >
> > Am 08.04.22 um 13:10 schrieb Jan Hebler:
> > > Maybe it is worth to mention this in https://docs.bareos.org/
> > > TasksAndConcepts/VolumeManagement.html#section-multiplestoragedevices
> > > As there is only an example for multiple devices using the same
> directory
> > > which uses (in that case correct) the same media Type.
> >
> > you're right, and I would be really happy if it was not so easy to get
> > it wrong.
> > However, you're referring to a subsection of the "Concurrent Disk Jobs"
> > chapter. The third paragraph in that chapter is completely devoted to
> > the very problem you were running into.
> You are right, there is an example on how to implement this, unfortunally
> one
> section above and under the line "concurrent disk jobs". I for myself was
> not
> aware that this will helps with the different pools...
> >
> > If you have any idea on how and where to document this so people don't
> > run into that problem all the time, we're really open to suggestions.
> In the Chapter Always incremental there are an example configuration with
> three Pools which uses the Storage File1 and File2 (btw: why uses the
> longterm-pool file1 as Storage?) If the documentation under "Using
> multiple
> devices" would keep these Names, that would help a lot. Or if ALL the Disk-
> related examples would use an continuous Scheme. Like this:
>
> You start with 3 Pools: incremental, differential and full. here you could
> explain the configuration of the Pools, the Storage, show how to use
> different
> devices in one storage to split the pools in separate directories,
> including
> the device type and so on.
> Next you could explain an conventional Setup with the usual incremental,
> differential and full backups.
> Next you could explain an Always incremental Backup, using differental for
> the
> consolidated and full for the Longterm Backups. That way, you could keep
> the
> Storage-definitions. There are only changes to the Pools required, if i
> got
> anything right.
> Finally you could show how to made concurrent Disk Jobs by adding devices
> to
> the Incremental and the other example by adding an second incremental pool.
>
> At least for me that would help a lot. But, then again, i'm not an Backup
> nor
> Bacula-Expert and maybe i'ts just my miserable english :-)
>
> Regards, Jan
--
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 bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/7b6ed705-d222-4147-ade0-fc8a7630eae5n%40googlegroups.com.
