StarWind VTL Immutable?
Posted: Thu Sep 16, 2021 3:43 pm
Hello all,
We have a customer using Veeam v10 backing up to StarWind VTL. They then send a copy to Azure. They want both the onsite and Azure copy to be immutable. Does StarWind VTL support immutability?
Veeam supports the immutability feature in v11 when using an Linux XFS repository, however the offsite copy to Azure we are told is NOT immutable since Microsoft Azure doesn't currently support immutability at the file level. AWS S3 has an object lock API that is per file which is what's required for Veeam to work properly, and any other object storage provider that had implemented that S3 object lock API should work (ex. Wasabi, or Cloudian).
When asking Veeam if StarWind could be used for immutable backup to Azure, the feedback was from their perspective it’s just a tape device. With Tape, they said immutability isn’t really a thing. There are WORM tapes for physical devices.
"VTL’s immutability on the back end would be a question for that vendor and their partners." <== So I ask, is there an immutability feature in StarWind VTL? And if so, if pushed to Azure would it still be immutable?
Hardening / air gapping like network segmentation, etc. is not good enough, they want immutability meaning the data is locked and unable to be deleted for a period of time.
Any feedback appreciated!
Thank you
We have a customer using Veeam v10 backing up to StarWind VTL. They then send a copy to Azure. They want both the onsite and Azure copy to be immutable. Does StarWind VTL support immutability?
Veeam supports the immutability feature in v11 when using an Linux XFS repository, however the offsite copy to Azure we are told is NOT immutable since Microsoft Azure doesn't currently support immutability at the file level. AWS S3 has an object lock API that is per file which is what's required for Veeam to work properly, and any other object storage provider that had implemented that S3 object lock API should work (ex. Wasabi, or Cloudian).
When asking Veeam if StarWind could be used for immutable backup to Azure, the feedback was from their perspective it’s just a tape device. With Tape, they said immutability isn’t really a thing. There are WORM tapes for physical devices.
"VTL’s immutability on the back end would be a question for that vendor and their partners." <== So I ask, is there an immutability feature in StarWind VTL? And if so, if pushed to Azure would it still be immutable?
Hardening / air gapping like network segmentation, etc. is not good enough, they want immutability meaning the data is locked and unable to be deleted for a period of time.
Any feedback appreciated!
Thank you