config: add virtual file changer example + documentation#2090
Conversation
b28db39 to
7ba14b2
Compare
e5637f2 to
54b319e
Compare
f25da90 to
2b98257
Compare
...c/stored/backends/unix_file_device.d/bareos-sd.d/autochanger/FilechangerStorage.conf.example
Outdated
Show resolved
Hide resolved
...c/stored/backends/unix_file_device.d/bareos-sd.d/autochanger/FilechangerStorage.conf.example
Outdated
Show resolved
Hide resolved
...c/stored/backends/unix_file_device.d/bareos-sd.d/autochanger/FilechangerStorage.conf.example
Outdated
Show resolved
Hide resolved
core/src/stored/backends/unix_file_device.d/bareos-sd.d/device/vfile.conf.example
Outdated
Show resolved
Hide resolved
core/src/stored/backends/unix_file_device.d/bareos-dir.d/storage/Filechanger.conf.example
Outdated
Show resolved
Hide resolved
pstorz
left a comment
There was a problem hiding this comment.
Unfortunately was not able to install as we do not have current packages.
With your proposed changes a rebuild has been triggered, so packages should be available today. |
8831976 to
e15d126
Compare
|
This configuration has the initial device "vfile0000" "reserved for storage and labeling". Testing I did a restore and it used vfile0001 by default with no option given to select the reserved device. Is this expected? How is the reserved device used? Does a restore job need to be created that takes advantage of this reserved device? Does it only come into play if none of the vfile0001 - vfile0xxx are available and it then will let you mount the revered device? Perhaps a some documentation could be added to clarify its use? |
|
Interesting comment, I will have a check @wizhippo to let the drive available for restore, you need to set the drive in autoselect=yes mode, then you have a drive more free, but you can't request directly the restore to use it. |
287c5c7 to
d0e7d6e
Compare
bruno-at-bareos
left a comment
There was a problem hiding this comment.
I don't think that renaming to File will improve the situation.
My vote is against for the reason given in the review
core/src/stored/backends/unix_file_device.d/bareos-dir.d/storage/Filechanger.conf.example.in
Outdated
Show resolved
Hide resolved
|
Important commit for documentation and defaultconfig not directly related are now extracted and presented in #2225 |
7010a78 to
77fe07a
Compare
|
Today meeting we decided to setup the example and the configuration, like it was done to replace the default distributed |
2adec63 to
82e9e42
Compare
pstorz
left a comment
There was a problem hiding this comment.
Very good work! Thank you bruno.
...c/stored/backends/unix_file_device.d/bareos-sd.d/autochanger/FilechangerStorage.conf.example
Outdated
Show resolved
Hide resolved
core/src/stored/backends/unix_file_device.d/bareos-sd.d/device/vfile.conf.example
Outdated
Show resolved
Hide resolved
- update indexes syntax. - rewrap paragraph. - cleanup example from oldies - remove and adjust `Maximum Concurrent Jobs` - introduce virtual file autochanger with auto-numbered devices. - fix spelling Directory -> |dir| - standardize parameters spelling - use relative positionning into the rst to source directly config example in sources. config: add virtual disk changer example `bareos-dir.d/storage/File.conf.example` is using storage resource defined in `bareos-sd.d/autochanger/FileStorage.conf.example` virtual file changer is using autonumbered devices defined in `bareos-sd.d/devices/File.conf.example` - create virtual_diskchanger.d backend configuration to use unix_file_device.d backend - packaging: add example files to all platforms - File.conf.example: set Address and Password to be fill'up with post install scripts - named the changer File so it can replace the default distributed DIR File storage ressource and FileStorage ressource on SD Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com> Co-authored-by: Philipp Storz <philipp.storz@bareos.com>
e34e466 to
1be752c
Compare
With bareos#2090 *.conf.example files get modified when installing a package. on RPM based distributions `rpm -V` should not lead to a altered package warning. `*.example.conf` files are marked as config files in the spec file. Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
With bareos#2090 *.conf.example files get modified when installing a package. on RPM based distributions `rpm -V` should not lead to a altered package warning. `*.example.conf` files are marked as config files in the spec file. Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com> (cherry picked from commit 8f784bb)
With bareos#2090 *.conf.example files get modified when installing a package. on RPM based distributions `rpm -V` should not lead to a altered package warning. `*.example.conf` files are marked as config files in the spec file. Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
With bareos#2090 *.conf.example files get modified when installing a package. on RPM based distributions `rpm -V` should not lead to a altered package warning. `*.example.conf` files are marked as config files in the spec file. Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com> (cherry picked from commit 8f784bb)
With bareos#2090 *.conf.example files get modified when installing a package. on RPM based distributions `rpm -V` should not lead to a altered package warning. `*.example.conf` files are marked as config files in the spec file. Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
This PR aims to introduce configuration example files for using an
autochanger with virtual disk autonumbered devices.
We also revisit some related chapter of the documentation.
After first presentation (2024-01-14), we want to rename disk to file, to respect the rest of the configuration CamelCase should be used, but it is not as practical and equivalent our tape changer is all lowercase.
We want to avoid name finishing with -
Please check
If you have any questions or problems, please give a comment in the PR.
Helpful documentation and best practices
Checklist for the reviewer of the PR (will be processed by the Bareos team)
Make sure you check/merge the PR using
devtools/pr-toolto have some simple automated checks run and a proper changelog record added.General
Source code quality
TODO