Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Restore 1.9T on SQL 2008


Restore 1.9T on SQL 2008

Author
Message
Nchax Phoku
Nchax Phoku
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 665
Hi guys,

Need urgent help..
I am restoring 1.9T from multiple backup files, the restore was doing 10% an hour until it got to 80%.
Its been on 80% for the the last 4 hours, retore I/O are movind and there is activity on the disk.
What else can I check to verify that the restore is not stuck?
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45474 Visits: 39948
Nchax Phoku (11/16/2012)
Hi guys,

Need urgent help..
I am restoring 1.9T from multiple backup files, the restore was doing 10% an hour until it got to 80%.
Its been on 80% for the the last 4 hours, retore I/O are movind and there is activity on the disk.
What else can I check to verify that the restore is not stuck?


Considering the time you asked and the time it is now, the delta time represents the correct answer... just wait. Microsoft's progress reports apparently aren't based on duration.

As a sidebar, I recommend changing the progress reporting to 1% in the future for this size database.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
_Beetlejuice
_Beetlejuice
Valued Member
Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)

Group: General Forum Members
Points: 64 Visits: 1301
This query will tell you how long the restore will take in seconds:

SELECT Percent_Complete, Estimated_Completion_Time / 1000 as [CompletionTimeSeconds]
FROM sys.dm_exec_requests
WHERE Command LIKE '%RESTORE%'
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47429 Visits: 44405
_Beetlejuice (11/17/2012)
This query will tell you how long the restore will take in seconds:

SELECT Percent_Complete, Estimated_Completion_Time / 1000 as [CompletionTimeSeconds]
FROM sys.dm_exec_requests
WHERE Command LIKE '%RESTORE%'


It'll tell you how long the restore is estimated to take, which may be very different from the time it actually does take.

One reason I can think of, the last portion of a restore is to run crash recovery on the newly restored database, if the log is badly fragmented or there were lots of open transactions at the time of the backup, that recovery process may take a long time. From what I can tell, the progress (STATS = 10) is the percentage of the data copied (which can be easily calculated), not the percentage of time (which is incredibly difficult to estimate correctly)


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


Nchax Phoku
Nchax Phoku
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 665
Thanks everyone for responding.
@Jeff, I think I should do that next time
@_Beetlejuice, i got hold of the script but it gave me different estimated_completion_time
each time I ran it.
@GilaMonster, the log file was only 30G - not sure about the open transactions though.

By the way, the Restore took 8 hours from 80% to 100%.

Kind Regards
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search