I'm referring to the VMware snapshot which is created when running a veeam job with with application aware processing activated and NetApp snapshot as target. Maybe I just think too complicated. What I try to explain is that if Veeam creates the necessary VMware snapshot, then create a NetApp snapshot while the VMware snapshot exists and delete the vm snapshot afterwards you would end in a NetApp snapshot with a VMware snapshot in it. Or more precisely, the NetApp snapshot will contain a vmdk file (read-only) plus a vmdk delta file to which all disk writes are redirected. So my question is: If I revert to the NetApp snapshot with built-in commands and then boot the vm (which consists of one vmdk and one vmdk-delta file) it will boot from crash consistent state with delta file, won't it? This is not case if I use Veeam to recover from restore point out of NetApp snapshot because Veeam uses the vmdk, more specifically its configuration (like it would do with instant recovery directly out of the backup file), independently of existing delta file, right? I know that I will definitely get the application consistent state with instant recovery, full vm restore, file level recovery etc... Perhaps this is more a VMware- / NetApp-related and less a Veeam-related question... but maybe somebody else can jump in.