 |
Seems vchanger didn't get updated in ages and as such is unusable with any bacula > 5.1 as it needs to support the new listall keyword which is added to mtx-changer and disk-changer but not to vchanger it seems. Output needs to look like this: # Drive content: D:Drive num:F:Slot loaded:Volume Name # D:0:F:2:vol2 or D:Drive num:E # D:1:F:42:vol42 # D:3:E # # Slot content: # S:1:F:vol1 S:Slot num:F:Volume Name # S:2:E or S:Slot num:E # S:3:F:vol4 # # Import/Export tray slots: # I:10:F:vol10 I:Slot num:F:Volume Name # I:11:E or I:Slot num:E # I:12:F:vol40 So this is more an enhancement that needs to be made for vchanger to support bacula and bareos then anything else. Given that there are very limited updates on vchanger (last update Thu May 20 12:25:52 2010) I think chances are very slim this gets ever added. |
|
|
Is there a updated replacement to be used instead of vchanger? Is disk-changer that replacement? When I was setting this up over the last four months I was reading that vchanger was the replacement for disk-changer and to use vchanger instead. Would the Bareos project would want to take vchanger under their wing as well since the source is available under the GPLv2? |
|
|
disk-changer is a script part of Bacula and Bareos which is used mostly for regression testing. It emulates a VTL using the same interface that mtx-changer uses. I use it myself with a fixed set of volumes and it works well not sure it will however work well with devices that are semi permanent. Think vchanger was one time invented to handle removable media but its biggest problem is that its unmaintained and as such misses stuff needed nowadays. As to updates to vchanger from the Bareos project, not likely to happen unless we have enough spare time and nothing else to do. There seem to be really a lot of earlier Bacula related projects which are orphans now. |
|
|
So vchanger is still the software to use for removable media. I'll see if I can contact the author to see if he can provide any updates, though I'm not hopeful. I understand the time factor as I'm also don't have enough time in the day to get my projects done. |
|
|
I guess at this time, this bug should be reclassified as an enhancement or will not fix. |
|
|
Given it was bad weather here anyway last night, in some lost hours I had a quick hack at vchanger. https://github.com/bareos/contrib-vchanger This is however fully unsupported but I think in essence it shouldn't break anything else I only added the two extra keywords needed for BAREOS e.g. listall and transfer. The bareos-master branch has the commit to add bareos specific stuff. I haven't bother documenting it. Feel free to fork it on github and add the documentation as that is something I really don't fancy doing. If it works (from my limited testing it looked alright.) great if not maybe I can see what is wrong but again no promises. I saw you asked questions on the vchanger mailing list and reading that list seems that some enhancements in other fields were in the pipeline in 2013 but it seems they never landed. |
|
|
Thank you for taking a look at the code and modifying it. I'll be able to test in probably this weekend. My full backup takes place on the first and it takes 3 days to complete. |
|
|
Good news. I got this response back from the developer: Actually, I have been working on vchanger, and version 1.0.0 should be released soon, hopefully in April or early May. While the LISTALL command is indeed implemented in mtx-changer and disk-changer since Bacula version 5.1, it is not documented in the Bacula Autochanger Interface documentation, or anywhere else to my knowledge. Since neither the Storage Daemon nor the Director use the LISTALL command, the statement that vchanger will not work with any bacula > 5.1 is simply not true. It just will not work with some of the web-based GUIs. My guess is that one of the GUI projects added LISTALL to mtx-changer, but it was never documented. Nevertheless, another user has already requested LISTALL support and it is being added in vchanger 1.0.0.. New features for 1.0.0 will be: 1. Change in the way volume files are mapped to virtual slots and in the way virtual drives are loaded. ��� When vchanger began, Bacula supported Storage Daemon on Windows Server 2003. Since that ��� version of Windows could symlink to directories, but not to files, symlinks had to be created to the ��� magazine mountpoint and metadata stored on the magazine to track loaded drives. Vchanger will ��� now simply use symlinks as the virtual drive, the target of the symlink being the volume file that is ��� loaded in the virtual drive. This allows a number of nice features, including: ������� * Individual magazines can have any number of volume files ������� * Volume files can have any filename ������� * New volume files can be added or removed dynamically without config file change ������� * Volume files can be moved from one magazine to another without affecting volume labeling ������� * Volume files created for a native disk Device resource can be moved to a magazine used ���������� with a vchanger Autochanger resource as long as the Media Type matches. ������� * Dynamic and unlimited number of virtual drives without config file change. The actual number ���������� of Virtual drives used is determined only by the number of Device resources defined in the ���������� Storage Daemon config file. 2. Now uses libudev, if available, to determine magazine filesystem mountpoints by UUID 3. Supports sending 'update slots' and 'label barcodes' commands via bconsole as needed 4. New udev rules generator supplies udev rules to send 'update slots' command at udev hotplug ��� event detection to support plug-n-play of external drives 5. Added support for undocumented LISTALL command 6. Deprecated INITMAG extended command 7. Added CREATEVOLS extended command to support dynamic creation of volume files 8. Added REFRESH extended command to support udev hotplug events 9. Added spec files for building RHEL6 and RHEL7 RPM s 10. Updated documentation |
|
|
Ok great his response as to the fact that Bacula 5.1 don't use listall is however not accurate but he is right nothing is documented. At least BAT uses listall as in so called API mode its used for status slots. Bareos now uses it in most cases so that is the actual change to Bacula. But we wait then for a new vchanger to see what happens but its been kind of dead for almost 5 years so I didn't expect it to see a new release. |
|
|
vchanger 1.0.0 was released 3 days ago which has LISTALL support. This morning added some small changes to the 1.0.0 version for the transfer command so that is at least accepted. The new vchanger has quite a different approach to some things so you might want to have a close look on the changes needed to your config. |
- Anonymous
