Sidebar
public:5293_backuplog_cannot_be_performed_no_current_database_backup
Table of Contents
[V7] ISSUE: BACKUP LOG cannot be performed because there is no current database backup (MS SQL transaction log backup)
Article ID:
5293
Reviewed:
2018-01-24
Product Version:
AhsayOBM: 7.15.2.0 to 7.x
OS: Windows
ATTENTION 1st January, 2022: v7 officially End-of-Life [details]
Problem Description
When performing a MS SQL transaction log backup (ODBC backup mode), the following warning message is received in the backup report:
| No. | Type | Timestamp | Log |
| * | ... | ... | ... |
| * | info | ... | [Start] Backing up "SQL_hostname\MSDB\db_name" using "Transaction log" to "temp_path" |
| * | warn | YYYY/MM/DD hh:mm:ss |
[Microsoft][ODBC SQL Server Driver][SQL Server] BACKUP LOG cannot be performed
because there is no current database backup. |
| * | ... | ... | ... |
Cause
This error can occurs if there is no full backup performed before a transaction log backup.
This error can also occurs when the database recovery model had been changed (e.g. from Full to Simple or vice versa) but a Full backup was not performed since the change (Details).
Resolution
To resolve the issue, perform a Full database backup before performing a transaction log backup.
- The recovery model had been changed without taking a full backup.
- A SQL maintenance plan task had changed the recovery model (re-indexing can cause this).
- The database was detached from another server and attached to the current server.
Keywords
sql, odbc, log, differential, database, mssql, recovery, model, transaction
public/5293_backuplog_cannot_be_performed_no_current_database_backup.txt · Last modified: 2021/12/16 06:10 by anna.olalia