Search
Subscribe
Categories
- Backup and Restore
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- Deadlocks
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Jobs
- Links
- Locking
- Memory
- Monitor Performance
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Cachestore
- SQL Error Logs
- SQL Optimizer
- SQL problems
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- Virtualization
- Wait Stats
Recent Posts
- How to check Operating System type with Powershell
- ALTER TRACE and developers
- Predict ALTER INDEX REORGANIZE finish time
- Cannot connect to SQL Server
- Timeout occurred while waiting for latch: class 'LOG_MANAGER'
- The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time
- How to create a SQL Server Security Audit
- Cannot use Large Page Extensions: lock memory privilege was not granted
- Compare two files with Powershell
- Export-CSV Powershell
SQL BACKUP failed to complete BACKUP LOG and sql error 3041.
The Backup Operators reported a SQL Server BACKUP failed error . They attached the TSM log entry.
20-05-2011 20:31:34 ACO5422E Received the following from the MS SQL server:
20-05-2011 20:31:34 An exception occurred while executing a Transact-SQL statement or batch.
20-05-2011 20:31:34 BACKUP LOG cannot be performed because there is no current database backup.
20-05-2011 20:31:34 BACKUP LOG is terminating abnormally.
I checked the SQL Error Logs . The related entry is :
BACKUP failed to complete the command BACKUP LOG MYDB. Check the backup application log for detailed messages. Error: 3041, Severity: 16, State: 1.
Looking at the SQL Server logs – there was an earlier entry of an ad-hoc SQL Server Backup.
A developer had taken an ad-hoc SQL Server BACKUP , without using the COPY_ONLY parameter, onto a local disk. This caused the BACKUP LOG to fail .
Copy only backup in SQL server 2005 and not break the backup chain
The Backup Operator issued a full SQL database BACKUP onto tape – this allowed the BACKUP LOG to start working correctly.
Source:Jack Vamvas (http://www.sqlserver-dba.com)
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |