PowerProtect Data Manager 19.11 Virtual Machine User Guide

PDF

Troubleshooting Microsoft SQL Server databases skipped during virtual machine transaction log backup

If a transaction log backup is not appropriate for a database, the database is automatically skipped. Databases are skipped for the reasons outlined in the following table.

Table 1. Microsoft SQL Server skipped database cases and descriptions
Case	Description
Database has been restored	When a database has been restored, this database is skipped during a transaction log backup because there is no backup promotion.
System database	System databases are automatically skipped during a transaction log backup.
Database state	The database is not in a state that allows a backup. For example, the database is in the NORECOVERY state.
Recovery model	The database is in the SIMPLE recovery model, which does not support a transaction log backup.
Other backup product	The most recent backup for the database was performed by a different backup product.
New database	The database was created after the most recent full backup.
Backup failure	The database was in a state that allows a backup, and a backup was tried, but the backup failed.

All skipped databases are backed up as part of the next full backup. Also, a skipped database does not result in a failure.

The only instance in which a transaction log backup job would potentially fail is if all Microsoft SQL Server instance databases failed to be backed up or were skipped.