...
BugZero found this defect 3638 days ago.
A Backup or Replication job using Application-Aware Processing fails with an error similar to:
The VeeamVssSupport service cannot be installed because the VeeamVSSSupport service is still present from a previous job run and is marked for deletion by the OS. The service becomes marked for deletion by the OS when the OS fails to process the service delete request that the previous job run sent. By default, Non-Persistent Runtime Components are used by Veeam Backup & Replication when performing Application-Aware Processing. A connection is made to the Guest OS during each backup job run, and the VeeamVSSSupport service is installed. When the VM is done being processed, Veeam Backup & Replication sends a request for the VeeamVSSSupport service to be deleted.
Reboot the VM's guest OS to allow Windows to remove the VeeamVSSSupport service that is marked for deletion.
If this issue frequently recurs for a specific VM, consider switching from Non-Persistent Runtime Components to Persistent Runtime Components. When using Persistent Runtime Components, the VeeamVSSSupport service is not removed after each job run and is left present within the Guest OS, ready for the next job run. To enable the use of Persistent Runtime Components: Ensure the VeeamVSSSupport service is not stuck marked for deletion. If it is, reboot the VM. Enable Use persistent guest agent within the job for that specific VM. Manually install the Veeam Installer Service on the VMThe VeeamInstallerSvc.msi is located on the Veeam Backup Server in: C:\Program Files\Veeam\Backup and Replication\Backup\Packages With "Use persistent guest agent" enabled in the job and the Veeam Installer Service installed, during the next run of the job, the VeeamVSSSupport service will be created and will not be removed after the job completes.