Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Disaster Recovery SQL

Status
Not open for further replies.

HBelk

IS-IT--Management
Jul 10, 2003
5
US
We are currently evaluating different ways to keep our Disaster Recovery SQL Servers in sync with our Production SQL Servers.

Log Shipping in SQL Server 2000 Enterprise Edition works well and allows both servers to be running SQL services. It even allows you to view the data on your DR server to do periodic "sanity" checks on your DR data.

We have looked at a package by NSI Software named DoubleTake. It copies bit by bit the physical SQL Database file to the DR Server. Each change in the file size triggers the data copy to the DR site. SQL is installed on the DR server but cannot run as a service until you "Failover" to the DR machine.

It's very easy to install and allows you to failover the database pretty fast. No transaction logs to restore. But I have a hard time dealing with the unknown factor, since the DR SQL service cannot run while the production SQL server is running. I would feel more comfortable if I could schedule table counts or comparisions to make sure Prod and DR are exact copies.

My question is has anyone used DoubleTake for SQL Disaster Recovery and what were your experiences?

Thanks so much.
H Belk
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top