AWS S3 Object Locking

[JustMeHere]

Does Backup4All S3 work with S3 object locking? I'm asking in this forum because if it doesn't it would be a very important feature to add.

The idea is the object is protected from a ransom attack as long as it's locked. The lock can be set to expire after n days. That way stale backups can be removed after the lock out period.

[Adrian (Softland)]

Hi,

Backup4all does not have such a feature for S3 object locking.
If you use a backup configuration set to run daily incremental backups and weekly/monthly full backups, then periodically delete older backups, you can set different object locking periods for each file.

An easier way to protect against ransomware is to keep multiple backup versions in destination.
The attack cannot be run on AWS, so the backups are safe there.
If for some reason the local computer gets infected and the local files gets encrypted by a ransomware, then you run a backup of the encrypted files, the new backup will be stored near the old backups.

[JustMeHere]

The issue is using the computer running the backups to AWS S3 to delete the existing files.

The world's most popular VM backup software is compatible with object locking to protect against this possibility.

While I use B4A for personal backups, using it for my clients would be attractive.

I think the program is most of the way there, but the way the catalog is handled on S3 might need to be tweaked.

[Adrian (Softland)]

Hi,

I added your request on our Wishlist.