Microsoft sql server ошибка 3013

title	description	author	ms.author	ms.reviewer	ms.date	ms.service	ms.subservice	ms.topic	helpviewer_keywords
MSSQLSERVER_3013	MSSQLSERVER_3013	pijocoder	jopilov	sureshka, mathoma	03/23/2023	sql	supportability	reference	3013 (Database Engine error)

MSSQLSERVER_3013

[!INCLUDE SQL Server]

Details

Attribute	Value
Product Name	SQL Server
Event ID	3013
Event Source	MSSQLSERVER
Component	SQLEngine
Symbolic Name	DMP_ABORT
Message Text	BACKUP DATABASE is terminating abnormally /RESTORE DATABASE is terminating abnormally.

Explanation

This error is a generic error that occurs when a backup or restore operation is interrupted unexpectedly. You see 3013 raised together with other error messages that provide more specific insight into the cause of the backup failure. Examples would include read or writes failure from/to the backup media or other unexpected Win32 API call failures.

Cause

There could be many various causes for an abnormal termination of a backup or a restore in SQL Server. Here’s a list of common reasons:

• Insufficient disk space
• Incorrect path to the backup storage device
• The backup file/device is already open by another program
• Backup media device failure or malfunction
• Database corruption — if the database is corrupt, the backup or restore operation may fail.
• Lack of BACKUP DATABASE, BACKUP LOG or CREATE DATABASE permissions to be able to back up or restore respectively
• SQL Server service account lack of access to the backup device

User action

Examine the SQL Error log for other messages that occur alongside this error for additional information and troubleshooting.

• For insufficient disk space, ensure sure that the drive where you’re writing the backup has enough free space available or use a different device. See Examples with errors 3203 and 3203

• For incorrect file path, double-check and correct the path and file name specified in the BACKUP or RESTORE command.

• For backup media failure, if you’re backing up to a tape drive or other backup device, make sure that the device is functioning properly and isn’t experiencing any hardware errors. See Examples with errors 3203 and 3203 and Example with error 3241

• For database corruption issues, you’re likely to observe other errors in SQL Server. Run DBCC CHECKDB to identify any errors in the database and resolve. For more information, see Troubleshoot database consistency errors reported by DBCC CHECKDB

• If your server principal account lacks permissions to do a backup or a restore operation, ensure account that is granted those permissions. See Backup permissions and Restore permissions

• For SQL Server service account permission issues, ensure that the SQL Server service account has read and write access to the backup device or the file system where the backup file is written. See Backup permissions.

Here are examples of commonly observed errors together with 3013.

Example with error 3241

In this scenario, error 3241 is raised with 3013 and indicates issues with the backup itself.

Msg 3241, Level 16, State 0, Line 2
The media family on device 'G:backupProdDB_backup.bak' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 2
RESTORE FILELIST is terminating abnormally.

Resolution:

This error typically indicates damaged backup(s) or the media that stores or transferred the backups malfunctioned. Find an alternative backup to restore either from different medium or try earlier or later backup.
Also, see KB5014298 for backup/restores of TDE databases — FIX: Error 3241 occurs during executing RESTORE DATABASE OR RESTORE LOG

For more troubleshooting ideas, see Media-related errors when you restore a database from a backup

Examples with errors 3203 and 3203

Errors 3202 and 3203 are backup errors raised when there are I/O-related issues. These two errors indicate whether a read or a write request was performed and show the underlying OS error that resulted from the I/O failure. These examples have been observed:

Msg 3203, Level 16, State 1, Line 1
Read on "G:SQLDATAProductionDb.ndf" failed: 483(The request failed due to a fatal device hardware error.)
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.

Msg 3202, Level 16, State 1, Line 2
Write on "Y:SQLDATAProductionDb.bak" failed: 1117(The request could not be performed because of an I/O device error.)
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.

Msg 3202, Level 16, State 1, Line 14
Write on "\BackupServerShareProdDb.bak" failed: 112(There is not enough space on the disk.)
Msg 3013, Level 16, State 1, Line 14
BACKUP DATABASE is terminating abnormally.

Resolution:

• The examples with OS 483 and 1117 indicate I/O device failure. Check for malfunction or damage of the storage media. Review System event logs, hardware configuration and logs and work with hardware administrator and vendor to address any issues with the media that stores the backups. Here’s an example of a message you may find in the System Event log, which indicates of I/O issues that need to be addressed:

  Warning PM,Disk,153,None,The IO operation at logical block address 0xe90525a0 for Disk 3 (PDO name: Device0000017) was retried.
  

• If OS error 112 is raised indicating space issues, ensure sufficient disk space on the local or remote storage where the backup is sent. If sufficient space is available, ensure reliability of storage media.

Example with 3624

In some cases error 3013 may be raised together with a system assertion. If a backup fails with an assertion, then the main focus is to address the assertion itself. Here’s an example of an issue observed:

Msg 3013, Sev 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
Msg 3624, Sev 20, State 1, Line 1
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.
Error: 17066, Severity: 16, State: 1.
SQL Server Assertion: File:     mediaRead.cpp:429 Expression:     !m_ActiveConsumptionList.IsEmpty () || !m_ActiveReads.IsEmpty () || !m_DecodeOutputQ.IsEmpty () || (CFeatureSwitchesMin::GetCurrentInstance ()->FEnableCheckingActiveDecodeQueueEnabled () && !m_ActiveDecodeInput.IsEmpty ()) SPID:         74 Process ID:     25440

Resolution:

Review the SQL Server error log and use the methodology outlined in this article MSSQLSERVER_3624 to troubleshoot the assert failures:

• Run DBCC CHECKDB on your databases and ensure all components on the I/O path are functioning properly.

• Lookup part or all of the assert expression online for any known issues. For example in this case if you look up «m_ActiveConsumptionList.IsEmpty» you may find this article:

  KB4469554 — FIX: Assertion error occurs during restore of compressed backups in SQL Server 2014, 2016 and 2017

• Update your SQL Server to a later build (Cumulative update)

• Ensure no external component is interfering and causing the failure

Example with error 4303

This example illustrates a restore of a transaction log sequence that failed and raised error 3013. The specific error 4303 indicates that either more transaction log restores are missing prior to this one or that the transaction log backup file is damaged. For example, the LSN = 4294967295429496729565535 doesn’t appear to be a valid LSN and that may be a result of a corrupt backup file or media.

Msg 4303, Level 16, State 1, Line 3
The roll forward start point is now at log sequence number (LSN) 8177105000003941300003. Additional roll forward past LSN 4294967295429496729565535 is required to complete the restore sequence.
Msg 3013, Level 16, State 1, Line 3
RESTORE DATABASE is terminating abnormally.

Resolution:

If you encounter errors such as 4303 together with 3013, find an alternative good backup to restore. Also check the stability of the storage media where backups are placed and repair as necessary.

See also

• Troubleshoot SQL Server backup and restore operations.

Overview of SQL Server Error 3013

One of the most frustrating situations that a user experiences while working with SQL Server is when errors are encountered. These errors disrupt the normal functioning of SQL Server and in worst case scenario may even lead to data loss. Sometimes, SQL Server Backup Detected Corruption In the Database Log. In this write-up, we are going to discuss about one such SQL Error 3013.

Error Description

SQL Server Error 3013 mainly occurs when the backup process to a disk/tape or a restoration process from a disk/tape is under process.

What is «Restore Database Terminating Abnormally» in SQL Error 3013 ?

The error message and the occurrence factors of SQL Server error 3013 vary according to the SQL Server version the user is currently working with.

SQL Server 7.0

In this SQL version, the error is encountered when the clustered index has been created in all the filegroups of the table.

SQL Server 2000

In this case, if the database of size 2 GB already exists and a separate database of size more than 2 GB is restored in the existing database, the error is generated.

SQL Server 2005

In the instance of restoration of both the data and log files at the same time, the Error 3013 is encountered.

Reason behind Its Occurrence

The dominant reason behind the occurrence of this error is the inability of the database to read the filemark present in the backup device or inaccessibility of the filemark itself. Before proceeding further, let us know what filemark actually is.

A filemark in a backup device is the element that does not store user data. In order to organize and unify the storage patterns, the filemarks, divide the partition in smaller segments. Their primary task is splitting data of all the individual files that are stored in the backup device.

The other reasons, which also play an important role in the occurrence of SQL error 3013, are:

• Media failure on the device in which the backup has been stored.
• Write failure whilst the execution of the backup process.
• Connectivity loss during the network backup process.

Workaround

1. The error can be removed by manual deletion of the device and ensuring that the server performs new backup to the device. The command to do so is:

2. In case the restoration process is the reason behind the error occurrence, it is possible to retrieve the other backup data by specifying the file number in the device.

In order to check the presence of multiple backup sets on the device, run the following code:

For indicating a specific set of backup, run the following command:

Note: The FileNumber term is used to represent the file series that the user wants to restore

Conclusion

In the blog, we discussed about the SQL Server Error 3013. With the help of the workarounds mentioned in the above section, the users can easily remove this error and continue with the restoration and backup process. In case if you failed with manual solution then you can also try SQL BAK recovery tool to successfully repair corrupt SQL .bak file.

Fix SQL Server Backup Error – Backup Database is Terminating Abnormally. sqlstate 42000 (Error 3013)

Let us assume that you are restoring a database backup from any disk or tape. While doing this, you have changed the logical name of the database. And then you may receive the following error message: SQL Server backup error 3013 or Msg 3013, Level 16, State 1, Line 1 Backup database is terminating abnormally

This error is interconnected to restoring the database. Using the statement RESTORE FILELISTONLY, a user can check the backup file. You will notice that the modified logical name of the database is corrupted or damaged and the last character of the name is truncated.

Consider the following user Query: SQL Server Backup Error 3013

Clark Williams: “Hi. The problem is when we tried to backup and restore our database using SQL Server 2008, we got an error. The schedule was to create seven backups of twenty-three databases. The schedule worked fine for some time. But, from the past two days, all the backups failed. The server is showing the following error:

Write on “T:\.bak” failed: 170(The requested resource is in use.)
Msg 3013, Level 16, State 1, Server, Line 1
BACKUP DATABASE is terminating abnormally.
Outcome: Failed

What would cause the above problem to occur? How should I correct it and prevent it from happening again?”

Important Note: In case if your SQL Server Backup files are corrupted and you are looking for a Quick Solution to repair corrupted .bak files then I suggest you take the help of SQL Backup Recovery Software. For complete details, the user can try the demo version of this software.

Download Now Purchase Now 100% Secure

Causes For the SQL Server Backup Database Error 3013

Oftentimes, when an administrator is backing up the database, SQL 3013 flashes up on the screen. The possible reasons due to which this SQL server backup error 3013 is displayed are:

• Write failure occurred while creating the backup: When there is insufficient storage space on the backup drive, the file gets compressed.
• When unauthorized users attempt to view network drive, SQL Server may result in the error.
• Media failure occurred: When the storage device where the backup file is saved undergoes any media failure, this may also result in SQL Server Error
• When the database is in Suspect mode, and the user tries to perform a backup of the transactional log, the error may occur.

Dependency upon Versions of SQL Server and Operating Systems

Errors in the SQL Server are dependent on the operating system and the versions of SQL application. The stated point will become more clear in the following section:

• SQL Server 7.0: In this version, an error occurs when a clustered index is created corresponding to each filegroup.
• SQL Server 2000: This error occurs in relation to another database. There are two possible situations under which the error in this version occurs:
  First, the database is lesser than 2 GB in size
  Second, the other database is having size more than the size of the pre-existing database
• SQL Server 2005: In this version, the error occurs when an administrator tries to back up both data files as well as log files simultaneously.

Workaround to Fix MSG 3013, level 16, state 1, line 1 Backup Database is Terminating Abnormally

To restore SQL Error 3013 manually, there are 2 manual methods. Both of them are described in detail:

#Solution 1

In this method, you need to take the database offline after changing the logical name of the database and then again bring the database online.

Following command needs to be performed:

#Solution 2

When you change the logical name of the database, insert a white space at the end of new file name. The command to implement the following change is:

Note: It is possible that you have to restart the database after changing the logical name of your database

Limitations of the Manual Solution to Troubleshoot SQL Server 2012 Backup Error 3013

Although the manual solution is free of cost, there are some of the drawbacks associated with the manual approach. The limitations of the manual method to fix SQL Server Backup Error 3013 are listed below:

• The workarounds depends on the version of the SQL Server
• A user must have a good technical knowledge regarding SQL Server
• Restoration using manual method may result in loss of information.

Professional Solution to Fix Backup Database is Terminating Abnormally. Sqlstate 42000 (error 3013)

The best solution to resolve the error is to use a third-party tool like Revove SQL Database Repair Tool. It is the trouble-free solution to fix msg 3013, level 16, state 1, line 1 backup database is terminating abnormally. According to the experts, it is the master solution to fix SQL Server 3013 error. By using this the user can easily recover the SQL Server database and also the user can export the data to SQL Server easily. Some of the features which make it distinct from other available products are:

• A file can be saved with two options: With only schema or With Schema & Data
• Supports SQL Server 2019, 2017 2016, 2014, 2012, 2008, 2008 R2, 2005, 2000 versions
• Preview and Recover Deleted SQL Table Records
• Supports SQL Server version 2019 and below versions.

Note: The user can also read the another similar post to fix SQL Server error 823.

Conclusion

When an admin change the logical name of the database while creating the backup of SQL file, SQL Server Backup error 3013 occurs. There are workarounds to eliminate the error. But, the problem is that the manual method is not that effective to remove the error. In fact, it may also result in loss of data. To overcome these problems, users can opt for an automated solution. This is the professional solution to fix SQL Server Backup Error 3013, level 16, state 1, line 1 backup database is terminating abnormally.

Overview of MS SQL Server Error Code 3013/3266

When you are trying to perform a database backup to a disk or tape, or a restore from disk or tape, error 3013/3266 may occur. For different SQL users, they may receive different messages when they encounter the error.

For SQL Server 7.0 Users:

For SQL Server 2000 Users:

For SQL Server 2000 Users:

For SQL Server 2005 Users:

What Can Cause Error Code 3013/3266

Several reasons can cause the «BACKUP DATABASE is terminating abnormally» error. Let us have a look:

• Media failure in which the data backup has been stored.
• Write failure occurs during the execution of the backup process at the same time.
• Connectivity loss occurred during the network backup procedure.
• There’s not enough space. The size of the database is 2 GB while a separate database is larger than 2 GB. It is restored in an existing database.
• The database is unable to read the file mark, which is available in a backup device or inaccessibility of file mark itself. 

Method 1. Manually Fix MS SQL Error 3013

To fix the error manually, follow the solutions below:

1. Delete or Erase the Device

To fix the error, you must delete or erase the device to perform new backups to the backup device. Before you delete or erase your data, back up your database in advance.

BACKUP DATABASE mydatabase TO DISK=’C:MyDatabase.bak’ with FORMAT

2. Run Query Analyzer

If the error message occurs during a restore operation, it may be possible to retrieve other backup sets from the device by specifying the file number. Run the following command to retrieve the backup from Query Analyzer.

RESTORE HEADERONLY FROM DISK=’C:MyDatabase.bak’

Each backup set has one entry in the output. To indicate a specific backup set, use this code:

RESTORE DATABASE mydatabase FROM DISK=’C:MyDatabase.bak WITH FILE = FileNumber

Important: FileNumber is the backup set number you want to restore.

Method 2. Fix Microsoft SQL 3013 Error with EaseUS MS SQL Recovery

What if error 3013 still exists even after performing all the manual solutions? What can you do? You can restore the data from a corrupt .bak file. You should try EaseUS MS SQL Recovery to fix this error. It is a superior database repair software. It can repair corrupted MDF or NDF SQL server database and solve SQL database problems. Besides, it can do the following things:

• Repairs corrupted SQL server database components — tables, triggers, indexes, keys, rules & stored procedures.
• Undelete SQL records from SQL Database.
• Save the database scan results to resume data recovery at a later stage.
• Export the repaired file to CSV, MDF, HTML, and MDF formats.

Follow the steps to repair your database and fix the error:

Step 1: Select the corrupted database for recovery

• Launch EaseUS MS SQL Recovery.
• Select the corrupted database file by clicking «Browse» (the two dots) or «Search».
• After selecting the file, click the «Repair» button to start the Analyzing process. 

What Can Cause Error Code 3013/3266

Several reasons can cause the «BACKUP DATABASE is terminating abnormally» error. Let us have a look:

• Media failure in which the data backup has been stored.
• Write failure occurs during the execution of the backup process at the same time.
• Connectivity loss occurred during the network backup procedure.
• There’s not enough space. The size of the database is 2 GB while a separate database is larger than 2 GB. It is restored in an existing database.
• The database is unable to read the file mark, which is available in a backup device or inaccessibility of file mark itself. 

Method 1. Manually Fix MS SQL Error 3013

To fix the error manually, follow the solutions below:

1. Delete or Erase the Device

To fix the error, you must delete or erase the device to perform new backups to the backup device. Before you delete or erase your data, back up your database in advance.

BACKUP DATABASE mydatabase TO DISK=’C:MyDatabase.bak’ with FORMAT

2. Run Query Analyzer

If the error message occurs during a restore operation, it may be possible to retrieve other backup sets from the device by specifying the file number. Run the following command to retrieve the backup from Query Analyzer.

RESTORE HEADERONLY FROM DISK=’C:MyDatabase.bak’

Each backup set has one entry in the output. To indicate a specific backup set, use this code:

RESTORE DATABASE mydatabase FROM DISK=’C:MyDatabase.bak WITH FILE = FileNumber

Important: FileNumber is the backup set number you want to restore.

Method 2. Fix Microsoft SQL 3013 Error with EaseUS MS SQL Recovery

What if error 3013 still exists even after performing all the manual solutions? What can you do? You can restore the data from a corrupt .bak file. You should try EaseUS MS SQL Recovery to fix this error. It is a superior database repair software. It can repair corrupted MDF or NDF SQL server database and solve SQL database problems. Besides, it can do the following things:

• Repairs corrupted SQL server database components — tables, triggers, indexes, keys, rules & stored procedures.
• Undelete SQL records from SQL Database.
• Save the database scan results to resume data recovery at a later stage.
• Export the repaired file to CSV, MDF, HTML, and MDF formats.

Follow the steps to repair your database and fix the error:

Step 1: Select the corrupted database for recovery

• Launch EaseUS MS SQL Recovery.
• Select the corrupted database file by clicking «Browse» (the two dots) or «Search».
• After selecting the file, click the «Repair» button to start the Analyzing process. 

Note: To use this software, you need to stop the SQL Server service.

Step 2: Repair the corrupted database

• The software displays all the recoverable items in a tree-like structure. The items are shown in a left pane.
• Select the desired component to be recovered. From the window, click the «Export» button. 

Step 3: Export to the database or as scripts

• Choose to export the database objects to database or export the items as scripts
• If you choose «Export to database», enter the information required and choose the target database.

Step 3: Export to the database or as scripts

• Choose to export the database objects to database or export the items as scripts
• If you choose «Export to database», enter the information required and choose the target database.

• A window appears up asking you to provide credentials to connect to the server and the destination to save the recovered items. In order to begin the repairing process, click «OK». 

Note: Before clicking «OK», you need to restart the SQL Server service.