BACKUP LOG could not be completed because there is no current database backup

I tried to restore the database, but this message was shown. How to restore this database?

Failed to restore database "farhangi_db".
(Microsoft.SqlServer.Management.RelationalEngineTasks)
------------------------------ ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: BACKUP LOG could not be executed because
no current database backup. (Microsoft.SqlServer.SmoExtended)

+86
sql-server
Oct 27 '13 at 22:07 on
source share
13 answers

Right-click Databases> Restore Database> General: Device: [path to backup file] → OK

First I created the database, and then restored the backup file to my new empty database. This was wrong. I should not create the database first.

Now I do this:

Right-click Databases> Restore Database> General: Device: [path to backup file] → OK

+173
Oct 28 '13 at 7:14
source share

Another cause of this problem is setting the Take tail-log backup before restore "Parameters" parameter.

On the Settings tab, disable / uncheck Take tail-log backup before restore before restoring a database that does not yet exist.

+117
Apr 7 '15 at 16:57
source share

please view the image below and apply the changes in SqlServer → RightClick on Database - Task → Restore - Select Backup File -> Finalize the changes in the Settings Tab

please apply changes in SqlServer

+19
Jun 25 '18 at 6:02
source share
  • Make sure there is a new database.
  • Make sure you have access to your database (user, password, etc.).
  • Make sure that it contains a backup file without errors.

Hope this helps you.

+5
Oct 27 '13 at 22:46
source share

Another reason for this is to restore the same database under a different name. Delete the existing one and then restore it for me.

+2
Mar 26 '18 at 10:41
source share

In our case, this happened because the recovery model in the primary database was changed after we made a backup in preparation for sending the logs.

To ensure that the recovery model is set to Full recovery , before you back up and configure the delivery of logs, we allow it for us.

+1
Jul 21 '15 at 2:21
source share

I fixed my mistake when restoring a nonexistent database from SQL 2008 to SQL 2014 by checking the Move to new folder location of SQL2014 checkbox.

+1
Mar 14 '16 at 17:41
source share

You can use the following SQL to restore if you have already created the database

 RESTORE DATABASE [YourDB] FROM DISK = 'C:\YourDB.bak' WITH MOVE 'YourDB' TO 'C:\YourDB.mdf', MOVE 'YourDB_Log' TO 'C:\YourDB.ldf', REPLACE 
+1
Apr 15 '16 at 8:13
source share

I simply deleted the existing database that I wanted to override with the backup and restored it from the backup, and it worked without error.

0
Jul 25 '18 at 8:07
source share

I'm not sure if the database backup file you are trying to restore comes from the same environment in which you are trying to restore it.

Remember that the destination path for the .mdf and .ldf files is the same as the backup file itself.

If this is not the case, it means that the backup file comes from a different environment than the current one on the host, make sure that the path to the .mdf and .ldf files is the same (exists) as on your computer, move them to otherwise. (This is mainly a case of restoring a database in a Docker image)

How to do this: In "Databases" → "Restore the database" → "[Files]" → (check the box "Move all files to a folder" - basically the default path is already specified in your hosting environment)

0
Jun 09 '19 at 22:02
source share

If the problem persists, go to the recovery database page and check "Restore all files in the folder" on the "Files" tab. This can help

0
Aug 02 '19 at 9:08
source share

You can simply use this method:

  • If you have a database with the same name: WIN+Rservices.mscSQL SERVER(MSSQLSERVER)Stop
  • Go to your path to the MySQL data folder and delete the preview database files.
  • Start sql service
  • Right-click on the database and select Restore Database
  • on the Files tab, change the Data File folder and the Log File folder
  • Click OK to restore the database.

my problem was solved with this BY method ...

-one
Sep 07 '15 at 13:38
source share

Right click on your database Print Tasks> Back up and back up from the database before restoring the database I use this method to solve this problem.

-one
Mar 01 '17 at 19:13
source share



All Articles