Although you can take a snapshot at any time, if the VM is running, there is still data being streamed to the disks. The snapshots might contain partial operations that were in flight. Also, if there are several disks involved, the snapshots of different disks might have occurred at different times. These scenarios may cause to the snapshots to be uncoordinated. This lack of coordination is especially problematic for striped volumes whose files might be corrupted if changes were being made during backup.
To avoid this situation, the backup process must implement the following steps:
- Freeze all the disks.
- Flush all the pending writes.
- Create an incremental snapshot for managed disks for all the disks.
Azure Backup is not the only option here. For SQL Server backup, another option is to backup to Azure Blob storage. There are several challenges that you face when backing up SQL Server. These challenges include storage management, risk of storage failure, access to off-site storage, and hardware configuration. Many of these challenges are addressed by using Azure Blob storage for SQL Server backups.
Hope this helps! Let me know if you have any other questions.
Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.