6

I am using SQL Server 2014 version 12.0.2000.8 on both systems. When I try to restore the backup taken from the first system onto the second system it says:

No backup set selected to be restored

However I can restore it on the first system without any errors. I also tried to restore using the following command:

RESTORE DATABASE EBS_ATM 
FROM DISK = 'G:\ebsBkup\ebs_bkup.bak'

The above command threw the following error message:

Msg 3013, Level 16, State 1, Line 3
RESTORE DATABASE is terminating abnormally.

I have checked rights and permissions on the folder as well as the .bak file.

Database version was checked through the query DetermineVersionOfSQLServer.sql in the Microsoft Knowledge Base article, How to determine the version, edition and update level of SQL Server and its components.

  • The database does not already exist on the second instance
  • RESTORE FILELISTONLY and RESTORE VERIFYONLY also throw error 3103
  • I know there should be another message before the 3013 eror, but I am getting only the messages I have posted.

The bak file is quite big ~70 GB. First I 7zipped and copy-pasted. Didn't work. Then I 7Zipped in 700 MB tranches. Didn't work. Finally I copied without zipping. Didnt work.

I would appreciate any help on this.

12
  • You could maybe check for NTFS File permissions... Otherwise, according to a post on sqlservercentral you should update to at least CU5. Dec 15, 2015 at 18:12
  • 1
    Have you tried to take another backup? Make sure you do it WITH INIT so that there is no confusion about which backup file to use. You probably need to use WITH MOVE on the restore as well, unless the data/log paths match exactly on both systems. Dec 15, 2015 at 18:14
  • @Jefferson I will look into the NTFS permission part tomorrow. As for CU5 I believe it is needed if the versions are different. Both systems in my case have exact same version.
    – Arcturus
    Dec 15, 2015 at 20:03
  • @Aaron I will try the WITH INIT suggestion tomorrow. I have already tried WITH MOVE and it gave same error. I have also scrapped the backup and took a fresh one. Lets hope it works. Thanks for the help,
    – Arcturus
    Dec 15, 2015 at 20:06
  • 2
    Just 1 more point to consider: I'd copy the backup file back to the original server, unzip, and attempt to restore that specific file. Perhaps something happens during the transportation and/or uncompression process that isn't caught when it's restored on the source? Worst case, you could also check a 3rd server and get 'quorum' :) Dec 16, 2015 at 2:01

2 Answers 2

2

No backup set selected to be restored

As SqlBak Blog Here the above error comes in two scenario.

1)You are trying to restore your database to a lower version of SQL Server. If you make a database backup on a higher version, let’s say SQL Server 2012 and then you try to restore it on SQL Server 2004, you will get this error message: No Backupset Selected to be Restored.

2)The backup file is unreadable or corrupted. You can simply check your database backup using the following command:

RESTORE HEADERONLY FROM DISK='D:/DatabaseBackupFileName.bak';

I think as my knowledge it's a incomplete error message. Because most of the time along with Msg 3013, Level 16, State 1, Line 3, the operating system errors (like Operating system Error 3,5 etc) or some error come.

Msg 3013, Level 16, State 1, Line 3 RESTORE DATABASE is terminating abnormally.

For this error i would recommend to Pinal Dave blog Here,Here and MSDN Blog Here

Even Remus Rusanu answer also in dbastackstange related to Network drive with same error message Here

0

If TDE is enabled you will need to either move the certificate or asymmetric key that is used to open the database encryption key or decrypt the database take a backup to a new file then move and restore on the new server. Microsoft link: Move a TDE Database

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.