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 |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2006-10-26 : 13:32:46
|
| In 2007 we plan on moving many of our SQL Servers (2000 & 2005) to a SAN. We will also be investigating the best way to replicate data from our production SAN to a Disaster Recovery SAN. I would like to know if people rely on built-in SQL Server replication / log shipping or third party products like DoubleTake or MirrorView. What's the advantage, if any, to using a third-party product?Thanks, Dave |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-10-26 : 14:03:19
|
| We use log shipping for our 2000 servers and database mirroring for our 2005 servers. Replication is not a disaster recovery solution, so that's never under consideration for us. Our DR site is located about 300 miles away. Twice a year we move our databases and applications to this DR site to ensure it is a functional site. We live production running there for about 3-4 weeks. We are actually doing this now. We moved our databases on September 23rd to the DR site and we'll be moving them back on November 4th.From all of this experience with DR, I'd say that database mirroring completely simplifies things. We can complete a database move in about 5 seconds, all databases within about 30 seconds. With log shipping, it took a minute to a few minutes per database.Tara Kizer |
 |
|
|
|
|
|
Log Shipping or Third-Party Replication for DR?