Hi again;
This error will be displayed if the account used for the log truncating does not have enough rights or either the VSS SQL service is stopped; Also I will be mentioning more workarounds at the end of the page.
In resume you will be seeing an error like this one:
“databases will be backed up in crash-consistent state and transaction log processing will be skipped”
Ensure the displayed service is always running in order to perform the backup correctly “crash consistent state” & also ensure Admin credentials are selected and correct on the backup job
Useful advises ( extracted from Veeam official page)
- Grant the SQL VSS Writer service user a sysadmin role (Instructions in KB here: https://www.veeam.com/kb1978)
- Restart SQL VSS Writer service (Instructions in KB here herehttps://www.veeam.com/kb2041)
- In the case of SBS machines that are also Domain Controllers, ensure that the SQL Writer is running as a domain administrator and not local system
- Allow the SQL Writer service account access to the Volume Shadow Copy service via the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
If the DWORD value “NT SERVICE\SQLWriter” is present in this key, it must be set to 1.
If the Volume Shadow Copy service is running, stop it after changing this registry value. Do not disable it.
sevenitblog.com 