huge db size in logshipping | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

huge db size in logshipping

i had restored a full backup of size 220gb my cob server i.e destination server in logshipping……as there was a problem in logshipping… long do u think will it take to restore a db of such huge size???…..i took just 2hrs ……wondering how it got over so early!!!!!!!!!!there wasnt many jobs configured….it was totally dedicated for logshipping……. rgds
When you are restoring any database it depends on the throughput…
If you are using the network backup then it depends on the network configuration and or NIC card configuration of source and destination server…
When you restore big databases…first time it may take longer because it has to allocate the space… You can monitor the restore throughput using perfmon backup throughput counter…
Moderator All postings are provided “AS IS” with no warranties for accuracy.

Thanks for the info Regards
I have seen questions asking why the restore is slow, but this is typical as you wondered why it has complete so early [<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ />], as explained it is purely dependant upon the system resource usage on the destination server and also if you have copied that file locally on that server then yes the throughput is 100%.<br /><br />Also<a target="_blank" href=></a> look at SQL Management pack in thsi case.<br /><br /><b>Satya SKJ</b><br />Microsoft SQL Server MVP<br />Writer, Contributing Editor & Moderator<br /<a target="_blank" href=http://www.SQL-Server-Performance.Com>http://www.SQL-Server-Performance.Com</a><br /><center><font color="teal"><font size="1">This posting is provided AS IS with no rights for the sake of <i>knowledge sharing. <hr noshade size="1">Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.</i></font id="size1"></font id="teal"></center>