Insider protection vs s3 object lock

[dhayes16]

Hello all. Veeam insider protection via cloud connect is a great feature. But from what I have read in order to use it you need to have gfs enabled for your backup copy job to the cloud connect partner and this can add up a lot in cloud storage costs since you will at least double your storage needs.

Now that Wasabi supports s3 object lock we have been testing it and it works quite well. We were thinking this might be a viable lower cost alternative to get immutable storage for ransomware / deletion protection since Wasabi is relatively low cost. Now it is not as robust as insider protection in that you do not get all the services of a cloud connect partner (sending drives overnight, spinning up cloud vms, etc). But Wasabi via a sobr with immutable seems like a viable alternative option. Any downsides?

We have also deployed a Linux hardened repo on prem as well and this too is a great option. But we were thinking of cloud.

Thanks for any input.
Dave

[HannesK]

Hello,
if you like to go to the cloud with the copies of your customer backups, then the only downside I see is the bandwidth you need.

Best regards,
Hannes

[veremin]

But Wasabi via a sobr with immutable seems like a viable alternative option. Any downsides?

It's a valid option indeed.

Now it is not as robust as insider protection in that you do not get all the services of a cloud connect partner (sending drives overnight, spinning up cloud vms, etc).

You can combine both by creating cloud repositories on Scale-Out Backup Repository with Capacity Tier attached. If you enable copy mode and immutability features, your tenants backups will be copied to object storage (as soon as they are created) and locked from deletion.

You can even enable Insider Protection, if you want to.

Thanks!