Versitygw as a backup target

[TonioRoffo]

Hello,

I've been doing some small tests to versitygw running as a S3 gateway.

It seems to be working (at least in smaller tests) and is very efficient on a single target machine - actually near native speed is achieved)
Object locking/versioning seems to be a step too far, it just locks up - without it, it seems to run fine (backups, mounting, deleting, all okay)

Still a bit confused about the underlying way versityg3 stores objects. I created a bucket, but on the filesystem itself, the veeam backup data seems to be stored in a different folder. When completely deleting from veeam point of view, the data is gone, but all the objects remain in this folder, taking up space still. (even with versioning disabled)

Did anyone else on the forum attempt to use versitygw? I'd love to discuss.

[TonioRoffo]

Well I guess it's far from veeam ready. Deleting the backups, including GFS, throws an error

"7/11/2025 10:50:09 Error [testtoberemoved_2025-11-07T095122] Failed to delete backup Error: Failed to copy checkpoint
Agent failed to process method {Cloud.DeleteBackup}."

[sfirmes]

@TonioRoffo ,

At this time, Versity isn't listed as a compatible S3 solution for use with our software.

I see that you reference GFS backups. Are you trying to use Versity's S3 Gateway with VBR's Archive Tier feature? If so, Versity isn't listed as a compatible solution for this feature either.

Please refer to our Veeam Ready page to find a list of the products that have passed our testing and are compatible with our software.

If/when they participate in Veeam Ready and pass the tests, I will update this thread.

Hope this helps.

[TonioRoffo]

Hello,

Thank you. I am aware that versitygw is not on the list. However I do love to tinker and see what is possible and open possibilities for the future. I was merely checking if others on the forum tried this way as well. I will send the veeam logs to the versitygw github and hope it is something that might be fixed in the future. The speed, even on silly hardware, was near perfect and backup/restore works flawlessly over quite a period of time. Only deleting data seem to throw an error at this point.

I have not used it as an archive or capacity tier at this point. Just a normal backup direct to S3 with keeping weeklies & monthlies turned on. When wanting to delete the whole repository I got the question if I wanted to keep the weekly and monthly full backups as well, that was what I was referring to.

The project is backed by large entities like CERN so it has a healthy future.