 |
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 |
|
|
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. |
|
|
On the other hand, the documentation for the storage daemon says re device: "... If a directory is specified, it is used as file storage. The directory must be existing and be specified as absolute path. Bareos will write to file storage in the specified directory and the filename used will be the Volume name as specified in the Catalog. If you want to write into more than one directory (i.e. to spread the load to different disk drives), you will need to define two Device resources, each containing an Archive Device with a different directory. ..." I am using file storage, and I have my "tape" files in separate directories. I have performed many restores under this configuration, but today when I tried a restore, I get the type of error reported in this bug. What are you referring to when you say there are "more detailed explanations" so I can understand how to correct my configuration? Thank you for your response. |
|
|
For the time being -- in particular, to perform an urgent restore at this moment -- I have decided to combine the tape (type Disk, in bareos parlance) directories into one, create one storage daemon Device, and just have all my director Storage's point to the one Storage I defined for the storage daemon. It works now. I can both backup and restore as before. I still feel that this is either a bug, or maybe there needs to be additional documentation explaining how to use multiple directories in the storage daemon for Disk type Storage's. |
|
|
Always us a different Media Type if the Device writes/reads from a different directory. Bareos uses the Media Type as an indicator which media types can be put in which device. If you are using more than one Catalog, some devices get mixed up in the databases, even if they have a different Media Types. |
|
|
Closing old fixed issues |
- Anonymous
