Kevin Kline (@kekline) is a renowned database expert and software industry veteran. A long-time Microsoft SQL Server MVP and noted leader in the IT industry, Kevin is a founder and former president of PASS and the author of popular IT books like SQL in a Nutshell. Kevin is a top-rated speaker at industry trade shows worldwide. He also blogs at http://KevinEKline.com and blogs.sentryone.com.
During some restore operations in SQL Server, the transaction log redo step might be taking an unusually long time. Depending somewhat on the version and edition of SQL Server you've installed, you may be able to increase performance by tinkering with the readahead performance for the redo operations. To do this, you should use the MAXTRANSFERSIZE parameter of the RESTORE statement. For example, if you set MAXTRANSFERSIZE = 1048576, it'll use 1MB buffers.
One of the things that's simultaneously great and horrible about the Internet is that, once something gets posted out in the ether, it basically never goes away. (Some day, politicians will realize this. We can easily fact check their consistency.) Because of longevity of content posted to the Internet, a lot of performance tuning topics become "zombies." We shoot 'em dead, but they keep coming back!