> On a related note, we’re also exploring immutable Veeam backups to Ceph > S3-compatible object storage. We came across this unofficial Veeam > object storage compatibility list: > https://forums.veeam.com/object-storage-as-backup-target-f52/unoffizial-compatibility-list-for-veeam-cloud-tier-t56956.html > > It looks promising. We've also read that Veeam/ceph works better when > veeam creates larger objects rather than many small ones—something we’ll > aim to validate during our PoC. > > If anyone here has experience using Veeam with S3-compatible object > storage/immutable backups, we’d love to hear about it. If this drifts > too far from the main topic of the list, feel free to reply off-list.
It works fine. As you said, make sure to set Veeam to use the largest possible object size, otherwise ceph will be spending a lot of time shuffling small items around, and the overhead will be what kills you, not the actual size. First attempt for us ended in ceph having some 660M objects of average size less than 180k. Probably a bit outdated but here is a guide on where to set the sizes: https://community.veeam.com/blogs-and-podcasts-57/sobr-veeam-capacity-tier-calculations-and-considerations-in-v11-2548 -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
