We updates VB4AWS yesterday to version 8. We are using VB4AWS since a few years already and have existing S3 buckets in AWS. For whatever reason it seems that Object Lock was enabled on all buckets long ago, probably when creating them years ago. At the same time we starte offload to S3 with immutability enabled and may just have used same bucket settings (no default retention in S3).
But this was working without issue. Now after yesterdays update, all backups are failing with:
But although Object Lock is enabled in S3, I can not enable immutability for the repository in VB4AWS.Backup policy has stopped with failures. Name: xxxx Error: Invalid immutability settings for a repository xxxx in S3 bucket xxxxx: Enable backup immutability because the S3 Object Lock feature is enabled on the selected bucket.
We did not change S3 settings. This is how it was the last years. I replied support immediately but did not get any further feedback since yesterday evening. It looks we might have hit a corner case where OL was enabled before and bucket was used without immutability. But I thought it was immutability was introduces in v7, so why do we now get the issue after updating from v7 -> v8?It appears there was an upgrade as well as a change on the S3. We do not support retroactively enabling the object lock as this must be done prior to adding the repository and taking any backups. At this point it should be disabled on the bucket and if you need to move to immutable backups, create a new repository with the settings in place prior to adding the repo to VBAWS.
The main problem is that no backups are running and we can not just tell VB4AWS that is should ignore OL. We have several hundred of TB at multiple locations in S3. We can not just start over with new buckets.
Is there any other way than to rollback to snapshot old version that hopefully will work?