Veeam Backup for Azure v2 has been released and includes many new features, as you remember, I wrote before about how-to deploy it from scratch, and much more.I remember discussing this on the blog, and with so many other people during all these years, Microsoft Azure is a great Cloud Provider, ahead of AWS on so many things, and behind on some others, but reliable no matter what.I can see Azure adoption going over the roof over the last years, and interestingly enough, I see more and more people from the vCommunity getting Azure certifications (and that is always a good sign).But as per usual, and for any service that our business relies on, it requires Backup, trying to follow the 3-2-1 rule as much as possible, and test those backups frequently.It might not be always a corrupted instance, but it can perfectly be as well:
- Human-error: And some instances, or instances get deleted. Especially with automation nowadays, one wrong character, comma, or dot, and can blow some resource groups within seconds.
- Ransomware/attacks: The instances are running regular operating systems at the end, this means Microsoft Windows Server or Linux on all the flavors. And these are in constant evolution, so if ransomware takes hostage of your production instances, at least you know you can always rely on any of the copies of the data you have produced with Veeam Backup for Azure.
- Testing/cloning: Well, why not? You have Backups, which can be snapshots or backups on Azure Blob, and you can recover from them within seconds to another Azure tenant, different networking config, resource groups, etc. Why not being proactive and test that critical patch, or upgrade to the applications on a different environment, using the backups as a data source. All good after testing? Alright-delete-all that environment.
- Compliance: Sometimes all the use-cases are good, and we all understand them, maybe even we have all automated and it can be rebuilt, or we think it can, within hours/minutes, but still following some regulations we will still need to have a Backup Strategy in place for these workloads in Azure.