immutable Backup to Url in sqlserver

SqlDba1995 Firstly, considering your situation, enabling versioning in the storage account is a practical workaround. However, be mindful of increased storage consumption due to each backup creating a new version, even if it's just a 0-byte file. Monitoring storage costs is crucial to avoid unexpected expenses.

From my experience, there are a few additional aspects to consider. Managing multiple versions can introduce complexity to the backup process, requiring careful tracking during both backup and restore operations. Additionally, performance may be impacted as each backup involves multiple interactions with the storage account.

While versioning addresses accidental deletions, it doesn't safeguard against data corruption. To enhance data integrity, implementing additional measures like checksums is advisable. Two more suggestions - consider scheduling backups outside the immutability period to allow for incremental updates without conflicts and explore backup methods that don't rely on incremental updates, such as copying the entire database to a separate storage location.