The VBR does not have any immutable backups on any object storage. All we want to do is being able to send customer backups to object storage with the same possibility of immutable backups as on our ordinary hardened repositories - but without having to keep an offboarded customer's backups for any number of years. We must be able to remove a customer's data after they have left (I wouldn't be surprised if some regulation or other are even forcing us to remove it) - how this ability could not be seen as the natural and default state is beyond me. "Compliance mode" can never guarantee the continued existence of backups for the whole retention period as long as someone has physical access to the storage. This is the same argument that are often mentioned on these forums when it comes to limitations for what "immutability" and other data security ambitions can achieve. It's not a criticism against Veeam but against the very existence of a software setting that effectively locks out the storage owner from his own box, or at least part of it (the part taken up by data stored for x years for a customer no longer present).
And for that, it seems that we must use "governance mode". Which it now seems that this COS platform dropped in my knee has no support for (see 2.2.3.4 in https://cloud.ibm.com/media/docs/downlo ... le-cos.pdf)...
And for that, it seems that we must use "governance mode". Which it now seems that this COS platform dropped in my knee has no support for (see 2.2.3.4 in https://cloud.ibm.com/media/docs/downlo ... le-cos.pdf)...
Statistics: Posted by DanielJ — Jun 04, 2025 1:23 pm
