little fulcrum
Hello, if I’m not wrong S3 SnapMirror transfers only recent object version in case versioning is enabled on the source bucket.
If I have situation that source bucket has versioning enabled together with ObjectLock due to the Veeam immutable backups, could this be still snapmirrored to elsewhere?
I know that locked bucket could. But if destination will not have all the object versions?
Thank you,
Lukas
civic carbon
Just to verify, veeam is using the built-in ONTAP S3 object locking available in 9.14.1 and later?
gusty hollow
does Veeam even create multiple versions of objects? As far as I understood it, it just drops every object into S3 and locks it, and then it is never written to (or changed) again.
open hamlet
From what I can say - Ontap 9.12 is Veeam Ready "tested", 9.14 is not - so i would say it's not officially validated. I used it and i tested it, but not on customer side.
From what I know, versioning is always required when object lock is used (not only with Veeam). This is because also a "deleted" object is a version - and it's still there if it has object lock....
i took a quick look on my veeam Lab using S3 explorer, as far i could see it was always only one version - but not 100% sure. But anyway - why use Snapmirror? I would always prefer the copy mechanism of the vendor, which in Veeam are "Copy Jobs", that works because they know their file structure.
little fulcrum
Just to verify, veeam is using the built-in ONTAP S3 object locking available in...
Correct, Veeam is able to use ONTAP S3 as immutable repository since version 9.14.1