Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

restoration issue Expand / Collapse
Author
Message
Posted Wednesday, April 9, 2014 2:35 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 10:24 AM
Points: 424, Visits: 1,049
restored full backup with norecovery , getting below error while restore the diff backup with recovery .

Error:
Unexpected termination on thread: 0, Return code: x80770004

RESTORE
DATABASE is terminating abnormally.
Problems were identified while planning for the RESTORE statement.
Previous messages provide details.
A previous restore operation was interrupted and did not complete processing on file 'abc_data'. Either restore the backup set that was interrupted or restart the restore sequence.

A previous restore operation was interrupted and did not complete processing on file 'abc_Data'. Either restore the backup set that was interrupted or restart the restore sequence.


any help to resolve this ?
Post #1559828
Posted Wednesday, April 9, 2014 3:01 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:35 AM
Points: 42,998, Visits: 36,155
charipg (4/9/2014)

A previous restore operation was interrupted and did not complete processing on file 'abc_data'. Either restore the backup set that was interrupted or restart the restore sequence.


i.e. Restore the full again, it didn't complete last time.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1559834
Posted Wednesday, April 9, 2014 5:57 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 4:14 PM
Points: 15,725, Visits: 28,130
Please don't cross post questions to multiple forums. It just confuses the discussion.

Gail, I said the same thing on the other one.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1559894
Posted Wednesday, April 9, 2014 6:14 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 10:24 AM
Points: 424, Visits: 1,049
full restaoration will take again half day.

is there any other way to solve it ?
Post #1559899
Posted Wednesday, April 9, 2014 6:19 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 4:14 PM
Points: 15,725, Visits: 28,130
In general, not always, but usually, the error message is telling you what's wrong and what you need to do to resolve it. You had an incomplete restore, specifically on a file (which possibly suggests extra steps you haven't detailed here), you either need to complete that restore operation or restart it.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1559902
Posted Wednesday, April 9, 2014 6:53 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:35 AM
Points: 42,998, Visits: 36,155
charipg (4/9/2014)
full restaoration will take again half day.


Then you may want to get started.

Probably longer than half a day, since the last restore failed part way through for some reason we don't know.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1559918
Posted Wednesday, April 9, 2014 8:44 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 10:24 AM
Points: 424, Visits: 1,049
ok..thanks for the advice.
Post #1559996
Posted Friday, April 11, 2014 12:18 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 21, 2014 4:05 AM
Points: 70, Visits: 466
You may also try to improve the restore time by testing MAXTRANSFERSIZE and BUFFERCOUNT values.
Post #1560715
Posted Friday, April 11, 2014 1:37 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:56 AM
Points: 2,603, Visits: 2,061
If you think that your backup is corrupt you can use RESTORE VERIFYONLY to check if the backup is good?

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Post #1560740
Posted Friday, April 11, 2014 3:48 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 4:14 PM
Points: 15,725, Visits: 28,130
free_mascot (4/11/2014)
If you think that your backup is corrupt you can use RESTORE VERIFYONLY to check if the backup is good?


Which will check just the header unless your backup is done with checksum. If your backup was done with checksum then verify only will redo the checksum validation and check the header. But, it doesn't check all of the header, so you can still have a bad backup after running checksum and verifyonly. The only way to ensure you have a good backup is to run a restore.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1560785
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse