Bareos Bug Tracker
Bareos Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000824bareos-core[All Projects] directorpublic2017-05-30 15:532017-06-08 15:21
Assigned To 
PlatformLinuxOSanyOS Version3
Product Version16.2.4 
Target VersionFixed in Version 
Summary0000824: Consolidation job requires explicit Storage definiton in Pool resource
DescriptionDocumentation states that defining Storage is not required in either Pool or Job resource, but that it must exist in at least one.

However, I ran into the issue where Virtual Full job requires Storage to be defined in Pool resource even though it was already present at Job resource.

Error message presented was:
Fatal error: No Storage specification found in Next Pool "poolname".

Manually copying storage from Job to Pool resource removed the error and backup job completed successfully. This is bad workaround as this removes flexibility that we previously exploited in having Storage defined at Job level rather than Pool level.

Detected storage line in job log looks like this.
*When defined in Job resource:
  "Storage: "storagename" (From Job resource)"
*When defined in Pool resource:
  "Storage: "storagename" (From Storage from Pool's NextPool resource)"

If any more information is required, please do let me know.

Kind regards,
Momcilo 'Momo' Medic.
Steps To Reproduce*Create pool without Storage definition.
*Create Always Incremental job with Storage defined.
*Wait for first Consolidation job.
*Error is thrown.
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action
Attached Filespatch file icon 0001-Fixes-bug-0000824-Consolidation-pool-requires-storag.patch [^] (1,061 bytes) 2017-06-08 15:21 [Show Content]

- Relationships

-  Notes
medicmomcilo (reporter)
2017-06-08 15:21

This one seems relatively easy to fix.
We need to allow for backup to take place if we already have write storage defined.
I am attaching proposed patch that would make job only fail if wstorage is not defined in Job resource and we don't have storage in pool.

Patch is rather small and should be easy to review.

Please let me know if any more information is needed from me.

Kind regards,

- Issue History
Date Modified Username Field Change
2017-05-30 15:53 medicmomcilo New Issue
2017-06-06 15:41 joergs Status new => acknowledged
2017-06-08 15:21 medicmomcilo File Added: 0001-Fixes-bug-0000824-Consolidation-pool-requires-storag.patch
2017-06-08 15:21 medicmomcilo Note Added: 0002651

Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker