We're at the planning stage of a cloud migration strategy, and I'm drilling down into the technical depths of DR/BC on both AWS and Azure.
As far as I can tell, if we went down the Azure route (using Veeam to restore our on-prem instances to Azure instances), once our VMs were in Azure, we'd no longer need Veeam - We could use Azure Backup to do the same thing, including file level restores, natively in Azure.
Now, in most respects, I prefer AWS over Azure. However, the AWS take on backup/restore seems to be somewhat behind that of Microsoft, as far as I see... I know I can take snapshots of EBS volumes, and if I want to do a file level restore, I have to mount that snapshot to another EBS volume, then run commands to copy the files back over the originals, etc. Sounds... laborious.
I know that we could just create an EC2 instance and install VBR on it, attach a big EBS volume and use that as a repository (I've done that in a test environment, and it works fine), but my question is... Is there a better way? Because I'd likely be using AWS snapshots to backup the full VM to a point in time, and Veeam would only really be needed for file level recovery, which seems like a bit of a waste, not to mention a cost overhead.
I also know that there are other products out there that deal with AWS FLR, but as we've been a loyal Veeam customer for the last 5 years, we'd like to continue using the interface/technology we know and love, where possible.
Any info welcome!