Bareos Bug Tracker
Bareos Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000835bareos-core[All Projects] directorpublic2017-07-18 02:342018-06-28 17:14
Reporterdivanikus 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformLinuxOSDebianOS Version8
Product Version16.2.6 
Target VersionFixed in Version 
Summary0000835: Restore job picks wrong storage
DescriptionI'm using version 16.2.6 compiled from source package (https://packages.debian.org/buster/bareos [^])

When I'm trying to restore fileset I get the following:

*restore client=zabbix-int-fd select current all done yes
Using Catalog "Metahouse"
Automatically selected FileSet: ZabbixServer
+-------+-------+----------+---------------+---------------------+------------------+
| jobid | level | jobfiles | jobbytes | starttime | volumename |
+-------+-------+----------+---------------+---------------------+------------------+
| 4,949 | F | 557 | 5,332,479,991 | 2017-07-02 01:01:08 | Full-0138 |
| 4,949 | F | 557 | 5,332,479,991 | 2017-07-02 01:01:08 | Full-0140 |
| 5,178 | I | 536 | 5,359,064,324 | 2017-07-03 01:01:15 | Incremental-0139 |
| 5,200 | I | 536 | 5,387,606,276 | 2017-07-04 01:01:13 | Incremental-0007 |
| 5,240 | I | 536 | 5,715,316,484 | 2017-07-17 18:10:47 | Incremental-0012 |
| 5,240 | I | 536 | 5,715,316,484 | 2017-07-17 18:10:47 | Incremental-0014 |
| 5,248 | I | 536 | 5,716,501,252 | 2017-07-18 01:01:00 | Incremental-0012 |
+-------+-------+----------+---------------+---------------------+------------------+
You have selected the following JobIds: 4949,5178,5200,5240,5248

Building directory tree for JobId(s) 4949,5178,5200,5240,5248 ... +++++++++++++++++++++++++++++++++++++++++++++
543 files inserted into the tree and marked for extraction.
Bootstrap records written to /var/lib/bareos/bareos-dir.restore.1.bsr

The job will require the following
   Volume(s) Storage(s) SD Device(s)
===========================================================================

    Full-0140 bs-00-full FullFileStorage
    Incremental-0012 bs-00-inc IncFileStorage

Volumes marked with "*" are online.


557 files selected to be restored.

Using Catalog "Metahouse"
Job queued. JobId=5270
You have messages.
*m
18-Jul 02:53 bareos-dir JobId 5269: Start Restore Job RestoreFiles.2017-07-18_02.53.36_33
18-Jul 02:53 bareos-dir JobId 5269: Using Device "FullFileStorage" to read.
18-Jul 02:53 bs-00 JobId 5269: Ready to read from volume "Full-0140" on device "FullFileStorage" (/opt/storage/full/).
18-Jul 02:53 bs-00 JobId 5269: Forward spacing Volume "Full-0140" to file:block 0:2999808192.
18-Jul 02:53 bs-00 JobId 5269: End of Volume at file 0 on device "FullFileStorage" (/opt/storage/full/), Volume "Full-0140"
18-Jul 02:53 bs-00 JobId 5269: Warning: acquire.c:239 Read open device "FullFileStorage" (/opt/storage/full/) Volume "Incremental-0012" failed: ERR=dev.c:661 Could not open: /opt/storage/full/Incremental-0012, ERR=No such file or directory

18-Jul 02:53 bs-00 JobId 5269: Please mount read Volume "Incremental-0012" for:
    Job: RestoreFiles.2017-07-18_02.53.36_33
    Storage: "FullFileStorage" (/opt/storage/full/)
    Pool: Incremental
    Media type: File

It just tries to read Incremental-0012 from wrong storage (FullFileStorage instead of IncFileStorage).
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-17.2: impactyes
bareos-17.2: actionwill care
bareos-16.2: impactyes
bareos-16.2: actionwill care
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 Files

- Relationships

-  Notes
(0002872)
divanikus (reporter)
2018-01-12 14:22

Problem is still here, Bareos 17.2 from official repo.

bs-00 JobId 11502: Warning: acquire.c:241 Read open device "FullFileStorage" (/opt/storage/full/) Volume "Incremental-0043" failed: ERR=dev.c:664 Could not open: /opt/storage/full/Incremental-0043, ERR=No such file or directory
(0003056)
stephand (developer)
2018-06-28 17:14

The Documentation for Media Type points out:

"...
If you are writing to disk Volumes, you must make doubly sure that each Device resource defined in the Storage daemon (and hence in the Director’s conf file) has a unique media type. Otherwise Bareos may assume, these Volumes can be mounted and read by any Storage daemon File device.
..."

See http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirStorageMedia%20Type [^]

It is admittedly not very obvious why this is necesary. However, the documentation contains some more detailed explanations.

We should decide if we really want to consider this a bug, as it can be fixed by configuring different media types.

- Issue History
Date Modified Username Field Change
2017-07-18 02:34 divanikus New Issue
2018-01-12 14:22 divanikus Note Added: 0002872
2018-01-27 20:02 joergs bareos-17.2: impact => yes
2018-01-27 20:02 joergs bareos-17.2: action => will care
2018-01-27 20:02 joergs bareos-16.2: impact => yes
2018-01-27 20:02 joergs bareos-16.2: action => will care
2018-01-27 20:02 joergs Status new => acknowledged
2018-01-27 20:02 joergs Product Version 16.2.5 => 16.2.6
2018-06-28 17:14 stephand Note Added: 0003056


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker