Operational Defect Database
BugZero found this defect 3002 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2104
How to exclude MS SQL Databases from SQL Log backup
Last update date:
9/9/2022
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Challenge
It is necessary to exclude specific databases on one or more Microsoft SQL Server instances from Veeam SQL Transaction Log backup processing.
Solution
The following registry value is used to exclude databases from SQL Transaction Log backup. The exclusion will take effect during the next SQL Transaction Log Backup session. Create this registry value on the server where Veeam Backup and Replication is installed. Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication Value Name: SqlBackupDatabasesToSkip Value Type: String Value (REG_SZ) Value Data: InstanceName:DatabaseName;InstanceName:DatabaseName Take note of the formatting, the registry value uses a colon between the instance name and the database name, and a semicolon is used to separate sets of instance and database pairs. Notes: This exclusion registry value is not server-specific and will apply to every SQL server processed by any SQL Transaction Log Backup. Do not include the server name in the registry value, only the Instance Name and the Database Name. The default SQL Instance, MSSQLSERVER, must be added to the rule as simply the word default. Example: The database "EDSHSD" in the instance named "SQLInstance" becomes SQLInstance:EDSHSD
