LLI Wiki — My Digital Knowledge Base

Veeam Backup & Replication tips: quiescence, SQL logs, Azure SQL

Fixes for common Veeam issues: VMware quiescence, SQL Server transaction logs, console removal and a login for Azure SQL.

Common Veeam Backup & Replication issues and their solutions: VMware quiescence, SQL Server transaction log backup owned by another job, removing the console, and a dedicated backup account for Azure SQL.

VMware quiescence

If quiescing (consistent snapshot through VMware Tools) causes trouble on a VM, these resources help choose or disable the mode:

Error: "Failed to prepare guest for SQL Server transaction log backup ... Job A owns SQL Server transaction logs backup"

Transaction log backup of a given VM can be performed by a single job only: Veeam prevents other jobs from touching the logs of that VM. By default, a 7-day delay applies before another job can take over. To do it immediately, create the registry value SqlBackupLogsAgeDaysToSkipLogBackup set to 0:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

"SqlBackupLogsAgeDaysToSkipLogBackup"=dword:00000000

Installation issue: removing the console

See Remove Veeam Backup & Replication console.

List installed products to find the product codes:

wmic product list brief > installed.txt

Before uninstalling the console, uninstall all Veeam Explorers:

Each component can be removed with msiexec /x {ProductCode}, for example for the console:

msiexec /x {00000000-0000-0000-0000-000000000000}

Installed products list (including Veeam) in Notepad

Azure SQL backup: dedicated account

On the logical server (master database), create a login for Veeam and give it the required server roles:

BEGIN TRY
    DROP LOGIN [sqlbackupveeam];
END TRY
BEGIN CATCH
END CATCH;
GO
CREATE LOGIN [sqlbackupveeam]
WITH PASSWORD = '<PASSWORD>',
SID = 0x<SID>;  -- copy the SID
GO
ALTER SERVER ROLE [##MS_DatabaseConnector##] ADD MEMBER [sqlbackupveeam]
GO
ALTER SERVER ROLE [##MS_DatabaseManager##] ADD MEMBER [sqlbackupveeam]
GO
ALTER SERVER ROLE [##MS_DefinitionReader##] ADD MEMBER [sqlbackupveeam]
GO
ALTER SERVER ROLE [##MS_LoginManager##] ADD MEMBER [sqlbackupveeam]
GO

In each database to back up:

CREATE USER [sqlbackupveeam] FOR LOGIN [sqlbackupveeam] WITH DEFAULT_SCHEMA=[dbo]
GO
EXEC sp_addrolemember N'db_owner', N'sqlbackupveeam'
GO

Notes

Mastodon LLIMastodon SocialFosstodon