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:
Comments
Post a Comment