One of the worst behavior about backup software is when it stop to do his job. About Veeam Backup & Replication v9.5 can be happen that some virtual machines are not more protected and the error showed into log file is:
Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (”). Error code: ‘32768’. Failed to create VM recovery snapshot, VM ID ’62bfb4be-a38a-4c27-a360-ee5f87ccbb93′. Retrying snapshot creation attempt (Failed to create production checkpoint.) Task has been rescheduled Queued for processing at 10/18/2017 10:40:08 PM Unable to allocate processing resources. Error: Job failed (”). Error code: ‘32768’. Failed to create VM recovery snapshot, VM ID ’62bfb4be-a38a-4c27-a360-ee5f87ccbb93′.
There are some solutions to resolve the issue but the cause is linked with SQL VSS Writer. In particular that machine affected with this error are all with Azure Active Directory Connect. To resolve the problem is necessary reinstall the component LocalDB, as showed in figure 1.
The problem is not from Veeam B&R but is into latest version of Azure AD Connect. The workaround is enable via GPO the policy “Do not forcefully unload the user registry at user logoff” for the machine with the component installed. More information can be found at this link: https://support.microsoft.com/en-us/help/2287297/a-com-application-may-stop-working-on-windows-server-2008-when-a-user