Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dewacorp.alliances
452 Posts |
 Posted - 2007-08-13 : 20:58:05
|
| Hi allI'm quite surprised yesterday that we've restored 32GB database and took only 7 minutes which is based on our statistic this sort of thing took about at least 30+ minutes.Here's what the situation is:1. We have 5 logical drives (C: - Physical disk - OS / Installation, F: - SAN - Data1, G: - SAN - TLog1, K: - SAN - Data2, L: - SAN - Tlog2).2. We've just presenting the K: and L: recenly. Normally, if I want to restore, we move .bak file from the tape to F: or G: then restored and this took normally 30+ minutes.3) But yesterday, I moved the .bak to a new L: SAN drive and restore to F: and G: and took about 7 minutes?!?! I verify this backup and 100% restored and intact.So is this because reading/writing from/to another SAN logical drive is QUICKER than reading/write on the same logical SAN disks?Can someone verify on this if this is the case? I'm appreciated your comment.Thanks |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-13 : 22:48:41
|
| Yes, since that separates read from write so reduces disk contention. You can verify that in perfmon or SAN monitoring tool. |
 |
|
|
|
|
|
SAN and Restoration Timing