@Archana Himane When a disk snapshot is in progress in Azure, write operations to the disk are not locked, but some precautions need to be taken to ensure data consistency.
To create a disk snapshot, Azure takes a point-in-time copy of the disk by creating a crash-consistent snapshot of the underlying storage. This means that the snapshot reflects the state of the disk at the time the snapshot was created, but it may not include in-flight writes that were not committed to disk at the time of the snapshot.
Azure provides several mechanisms to ensure data consistency when a disk snapshot is in progress.
One mechanism is to use a file system that supports atomic writes, such as NTFS, to ensure that data is written atomically to disk. This can help to ensure that writes are either fully committed or not committed at all, so that there are no incomplete writes at the time the snapshot is taken.
Another mechanism is to use Azure Backup or Azure Site Recovery to create consistent snapshots that take application-aware backups. These backups can ensure that applications are quiesced and writes are flushed to disk before the snapshot is taken.
In general, it's recommended to avoid write-intensive operations during the snapshot creation process, as they can impact the performance of the disk and potentially cause data inconsistencies in the snapshot. If you need to perform write-intensive operations, it's recommended to create a new disk and attach it to the VM, rather than using the existing disk, to avoid impacting the snapshot.
Please let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.