This document is not supported any longer.

Excluding Databases from Log Backup Process

In this article

    If you need to exclude a database from transaction log processing (without excluding the database itself from application-aware VSS processing), you can use the following methods:

    • Set database logging model to simple - then no log file will be created for this database, and log processing job ('child') will not be run for it.
    • Create a list of databases to be excluded from transaction log processing. For that, you will need to create the following registry entries under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication:

    Registry entry

    Type

    Default value

    Description

    Examples

    SqlBackupInstanceDatabaseDelimiter

    REG_SZ

    :

    Specified character string will be treated as a delimiter between InstanceName and DatabaseName in a list entry.

    sql_instance_name: - skip all databases from such SQL server instance (for example, sql_2014:)

    :db_name - skip all databases with such name on all instances (for example, :master).

    SqlBackupInstanceDatabasePairsDelimiter

    REG_SZ

    ;

    Specified character string will be treated as a delimiter between list entries.

    sql_2014:;:master

    SqlBackupDatabasesToSkip

    REG_SZ

    None

    Instructs Veeam to exclude SQL databases from transaction logs backup process. Databases and instances should be listed using the delimiters described by the SqlBackupInstanceDatabaseDelimiter and SqlBackupInstanceDatabasePairsDelimiter

    sql_intance_name:db_name - skip everything which contains such instance and database name

    sqlserver:msdb;sqlserver:model;:master;sqlserver:

    If database name contains default delimiter character(s), you can use any other character or character string as delimiter when creating a list of exclusions. For example, if  SqlBackupInstanceDatabaseDelimiter value is set to ###123###, then SqlBackupDatabasesToSkip will contain a list of entries like this:

    sql_instance_name###123###db_name_1;sql_instance_name###123###db_name_2