You can find here some of the frequent or common errors faced which manually performing a database backup or an automated maintenance plan or custom backup job failed.
Backup failed to complete the command BACKUP DATABASE database_name. Check the backup application log for detailed messages.
Backup Error 3041 is a generic error that is returned when a backup fails. Along with this error, there are additional errors returned and can be found in the SQL Server error log. Look for other specific backup errors, which will point the cause of the backup failure.
BackupDiskFile::CreateMedia: Backup device ‘\\BackupServer\Backups\Test\Test_Backup.bak’ failed to create. Operating system error 53(the network path was not found.)
If you carefully read the complete error message, it gives the cause of the failure “Operating system error 53(the network path was not found”.
Cannot open backup device ‘D:\Backups\Test_backup.bak’. Operating system error 3(The system cannot find the path specified.)
Make sure that the path D:\Backups exists, sometimes with user oversight, the path mentioned could be wrong lie the folder name could be backup and we use backups and will result in an error. – Another issue when this can occur is if there is any space at the end of the folder name.
Cannot open backup device ‘D:\Backups\Adv.bak’. Operating system error 5(Access is denied.)
BACKUP ‘Test_DB’ detected an error on page (1:12534) in file ’Test_DB.mdf’.
Error: 3043, Severity: 16, State: 1.
BackupMedium::ReportIoError: write failure on backup device ‘0a158c7d-a7a3-4d5a-8b58-124602e40a14’.
Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.)
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
Whenever SQL Server database backup is performed, an entry for that backup is made into msdb..backupset table. Check if the data and log files of msdb is set for autogrowth. Verify if there is sufficient free space of the disk drive where msdb files are located.
BACKUP DATABASE cannot be used on a database opened in emergency mode.
This error can occur if you try to perform backup of a database which is in emergency mode, which is not supported. Bring your database online and then perform the backups.
The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
This error can occur, if we try to perform transaction log backup of a database whose recovery model is set to “SIMPLE”. Transaction Log backups are not supported for databases in Simple recovery mode. If the database is critical and recovering as much data is required and if point in time recovery is important, then change the recovery model of the database to “FULL” and then schedule job to perform regular transaction log backups.
The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
Msg 3241, Level 16, State 7, Line 1
The media family on device ‘PathToBackupFile\BackupFile.bak’ is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
This issue can occur for various reasons, some of them are as mentioned below.
Restore verifyonly from disk = 'PathToBackupFile\BackupFile.bak'