tag:blogger.com,1999:blog-798194812750898417.post1316842318901566802..comments2010-08-05T08:29:48.585-07:00Jeffhttp://www.blogger.com/profile/05278298222887921824noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-798194812750898417.post-61065508721379425352010-08-05T08:29:48.585-07:002010-08-05T08:29:48.585-07:00Typical a Microsoft answer -- it depends.<br /><br />Direct attached SCSI may take around 6GB/hour, but I&#39;ve seen some high performance fibre channel SANs with HUGE caching controllers get up to 180GB/hour.Jeffhttp://www.blogger.com/profile/05278298222887921824noreply@blogger.comtag:blogger.com,1999:blog-798194812750898417.post-89954729518424491242010-08-05T08:20:57.731-07:002010-08-05T08:20:57.731-07:00What is the time it takes for the ESEUTIL step to run? I&#39;ve read estimates from 1 to 10 GB per hour depending on the options used. Does this seem correct?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-798194812750898417.post-9217816599827979642010-05-14T11:20:16.669-07:002010-05-14T11:20:16.669-07:00Hey Jeff,<br /><br />Great blog post! One quick thought - you should not have to run a /p against the restored DB. If you run eseutil Enn /r /i /d in the same folder as the dirty restored DB and logs, it should play back clean for you. The /i switch specifically ignores any &quot;hanging attachments&quot;.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-798194812750898417.post-17594152181998123882009-11-16T14:53:45.068-08:002009-11-16T14:53:45.068-08:00Keith Johnson. I like that.Jim G.http://www.blogger.com/profile/18251794656419415554noreply@blogger.com