Someone in old ancient times told me that once you make a copy of you’re backup just strip down permission to
chmod 400 mybck.tar.gzIn the most recent times the new word “immutable” become the new mantra in the backup area. In most linux filesystem you can set immutable using
chattr +i mybck.tar.gzIf you perform regular backups and keep them, you are above average. (I am a consultant, so I see what you do.)
The backup domain is simple in terms of logic but coul be hard to maintain, in term of space, performance, reliability, and in short, costs. An afforrdable way to have all of them at raisonable price could be an Object Storage. All the hyperscaler and many vendor offer this service at scale at raisonable price. This is why many backup software vendor include now as “new feature” the cloud backup “Vault” that can be used in the 3-2-1 strategy.
As far as i know many of this “Vault” feature offer also Immutability. This is great!
In some of them they are using the “S3 Object Lock API” and this is bad, (at least) for OCI.
OCI does not provide S3 Object Lock API at the time of this blogpost.
To me is not there even if you try with “S3 compatible mode”.
In OCI Object Storage the “immutable” topic is addressed via the “Retention Rules“.
If any of my statement will change in the future will be a matter of a new blogpost. By now,
Cheers
dbocciolini 