To backup Microsoft SQL Server, the account used for VM-side processing (application aware processing) requires certain permissions. Veeam recommends assigning the sysadmin role on the SQL Server but it is also possible to assign minimal permissions on the databases it needs to backup, which is the preferred method for security hardening.

The User Guide for VMware vSphere outlines the required permissions as well but for convenience, I've listed them here as well.

Instance-level roles:

Assign these roles:public

dbcreator

Database-level roles:

Assign these roles:

System databases master and model:db_backupoperator

db_datareader

public



System database msdb:db_backupoperator

db_dat  ...

In Veeam, when backing up linux-based VMs with application-aware processing turned on, testing the credentials may fail even though they have been entered correctly.

First, check whether you are really using linux-credentials and not Windows credentials, this can often be overlooked very quickly.

Check whether you see the logon attempt in linux. Depending on the distro, it is logged in a file in /var/log. E.g. for Debian/Ubuntu, it's logged in /var/log/auth.log. Looking at the logging will reveal whether it is a password or SSH key problem, or something else is going on.

Another possibility is that the required cipher is not allowed. Veeam requires the cipher aes128-cbc to be enabled. Alt  ...

When using Veeam to back up your VMs, and you get the following error on one or more VMs:

Error: VSSControl: -2147212529 Backup job failed.Discovery phase failed.Cannot add volumes to the snapshot set.Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{6c169bc7-d7bf-11e0-b074-806e6f6e6963}\].Cannot add volume to the set of volumes that should be shadowed.VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

According to KB1785, this is because of a third party VSS provider, present on the VM. If more than the default software provider is installed, another third party backup software suite may have enabled their provider on the VM, causing the initiation of a VSS backup  ...

There is a known issue with SentinelOne Agent 23.2.3.358 installed on a domain controller, which causes backups in Veeam for those machines to fail. The following error is displayed:

Error
Processing SERVER Error: VSSControl: -805306334 Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. Cannot prepare the [NTDS] data to a subsequent restore operation. Cannot process NTDS data. Updating BCD failed. Cannot execute [SetIntegerElement] method of [\\SERVER\root\wmi:BcdObject.Id="{cd12ab87-1a23-12f3-ba7c-dc9876b01357}",StoreFilePath=""]. COM error: Code: 0xd0000022

This is caused by the boot protection feature of SentinelOne. One possible   ...