 |
Do you have multiple storages in places, like requested in http://doc.bareos.org/master/html/bareos-manual-main-reference.html#StoragesAndPools ? If yes, what is the output of list joblog jobid=595 |
|
|
Yeas, there are multiple storage pools defined as: Pool { Name = AI-Incremental Pool Type = Backup Recycle = yes Auto Prune = no Maximum Volume Bytes = 100G Label Format = "AI-Incremental-" Volume Use Duration = 23h Storage = File Next Pool = AI-Consolidated } and: Pool { Name = AI-Consolidated Pool Type = Backup Recycle = yes Auto Prune = no Volume Retention = 10 years Maximum Volume Bytes = 100G Label Format = "AI-Consolidated-" Volume Use Duration = 23h Storage = File Next Pool = AI-Longterm } (+ there is longterm pool too) I have just realized that both pools point to the same storage engine/definition: 'File' - which is not the case in the docs - is this a problem? The command does not reveal much: 2017-01-12 17:27:14 bareos-dir JobId 616: Start Virtual Backup JobId 616, Job=SomeJob.2017-01-12_17.27.14_15 2017-01-12 17:27:14 bareos-dir JobId 616: Consolidating JobIds 7,27,47,67,87,111,133,155,177,199,221,243,265,287,309,331,353,375,397,419,441 2017-01-12 17:33:02 bareos-dir JobId 616: Bootstrap records written to /var/lib/bareos/bareos-dir.restore.5.bsr |
|
|
Yes, having only one storage is the problem, as Bareos will need a separate one for reading and writing. You are right. Your joblog does not reveal this fact. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html#UsingMultipleStorageDevices |
|
|
OK, many thanks for clarifying! I created another storage (File-Consolidate), pointing to the same SD and device and assigned it to the Consolidate job - but this does not seem to be enough, the job is stuck again. Does this other storage has to be pointed to a different SD? Or is simply different device on the same SD is good enough? It would be good to understand what is the exact requirement here? |
|
|
OK, I created a new device on SD pointing to the different filesystem path - and used this device as a storage target in director - it seems to work now! It might be a good idea to clarify documentation here, as it is not clear what exactly is required to get this thing up and running: it only says that "at least two storages are needed" - but this can be interpreted as 'Storage Pools' or 'Storage definitions in director'. Possibly some additional logging to detect this situation would be useful too. |
|
|
Forgotten resolved issue |
- Anonymous
