Replicating a SQL2000 cluster
We want to replicate a SQL2000 cluster to a single machine at a DR site. Any ideas on the replication technology we should look at and any pitfalls to watch out for?

    Requires Free Membership to View

    Login

    When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchStorage.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

There are a number of options available, depending on the type of replication your business requirements and budget will dictate. The possibilities include SQL's native replication capabilities, third-party software-based replication and data replication at the storage level.

Using SQL's built-in ability to replicate is likely the simplest approach, mostly because it does not require the addition of any third-party software or technology. It provides snapshot type replication (point-in-time) as well as transactional replication should there be a requirement for synchronized copies of the database. However, it does require an additional SQL server (subscriber) to be installed and licensed. It also implies strong SQL skills.

There are third-party software solutions available that build on SQL's native replication capabilities. They typically provide a relatively more user friendly interface with add-on features that can be useful for troubleshooting, such as a log view of replication failures down to the a single record level. That said, these solutions must be purchased separately and still require a licensed database server at the receiving end.

Another option is replication at the storage level, which can be accomplished via either hardware or software depending on the storage array used. This approach does not necessarily require an additional licensed server unless combined with a high availability cluster component. Data can simply be replicated and synchronized to a distant volume. Typically, this type of solution requires in-depth skills as a number of configuration files and parameters must be taken into consideration to ensure database integrity.

This was first published in July 2005