Nope, there is no luck with Rados, as bareos use single object as one volume. 1kb volumes would be a pain to the bareos database and backuping performance, 1GB or larger volumes would be a pain to ceph, as it have pools with 1GB objects... Ceph cries when rebalancing placement groups with large objects. 1GB objects seems too large for ceph and too small for bareos volume.
I have this solution at the moment. It may work if bareos use RadosGW (as it splits data to small chunks) as storage backend. I will see if it is possible to do something with python-sd http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-34300026.2.4 -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
