20.11.2019 09:41:02 :: Subscribing to guest processing components
20.11.2019 09:41:03 :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing with failover) Details: Job failed ('Fehler beim Prüfpunktvorgang für "SBS". (ID des virtuellen Computers: D2EB4A81-9BF5-4E08-A03E-F1C80088FBE5)
Für "SBS" können keine Produktionsprüfpunkte erstellt werden. (ID des virtuellen Computers: D2EB4A81-9BF5-4E08-A03E-F1C80088FBE5)'). Error code: '32770'.
Failed to create VM recovery snapshot, VM ID 'd2eb4a81-9bf5-4e08-a03e-xxdewr4324'.
20.11.2019 09:41:14 :: Truncating SQL server transaction logs
20.11.2019 09:41:19 :: Retrying snapshot creation attempt (Failed to create production checkpoint.)
20.11.2019 09:41:19 :: Required backup infrastructure resources have been assigned
20.11.2019 09:41:31 :: Guest processing skipped (check guest OS VSS state and hypervisor integration components version)
20.11.2019 09:41:36 :: Creating VM recovery checkpoint (mode: Crash consistent)
So why is the application item restore with a crash consistent backup possible?
Regarding the error message. It looks like a Hyper-V issue. Please take a brief look at this topic. Could you please try to create a production checkpoint manually to confirm the root cause resides on the Hyper-V side?
Answering your question, I do not think it would be possible to perform an application item restore from this particular backup. Are you saying you have done it?
We do not utilize legacy checkpoints at all - Veeam B&R relies purely on the production checkpoints when backing up Hyper-V 2016 and later. If a production checkpoint cannot be created manually by following the above procedure, meaning there is an issue with Hyper-V components or VSS, the best way to proceed would be to raise a support case with Microsoft. The topic I have linked above might be worth checking for additional information.