Skip to main content

SQL Express database backup restore failed


Database backup is a good strategy but knowing that you can rely on your backup when you needed it most is another story.

When doing backup one way to ensure that backup is okay, is seeing the message that the database backup  was successful like this image below.




But upon restoring the said backup that was successfully done, during the database restore; the system now is showing that a damage was detected, and the system is showing restore failed.

So, technically unable to restore the “.bak” file.

Restoring the backup can be done using the graphical interface or using T-SQL commands to restore the database.

But none of it will work, no matter how many times you tried, if some unforeseen issues will occur or for whatever reason the system and the sys-ad is just having a bad day.

An error of Restore failed for sever (Microsoft.SqlServer.SmoExtended) and also shows VERIFY DATABASE is terminating abnormally, keeps showing every time you restore the database.

The database backup was successful, but then unable to restore the backup. A chilling moment especially if its a production server.

What works for me for this scenario was to “restart” the SQL service.

After restarting the service, tried restoring the backup file and everything works fine. 

Restarting the server may have work but then if the server has multiple services running on it, rebooting the server will cause other services to fail and more issues may not be available while the server was rebooting.

So, rebooting the specific service is ideal as it won't affect the whole server.

See image below on how to restart the service:



Cheers! Till next time…

================================
Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:


Heaven's Dew Fall  Prayer app for Android :



Catholic Rosary Guide  for Android:


Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:




Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more