Disaster recovey for SBS2000/Terminal Server - what is the best way to get a solid backup/high availability situation
Posted on 2004-04-21
I am setting up a new SBS 2000 using Terminal Services, and may add SQL Server 2000 to the SBS machine in the near future. I currently have a 2000 server running SQL Server 7 to support my main application. The 2000 server is backed up to tape every night by Veritas Baclup Exec.
Backup to tape is certainly a good thing to do, but the volume of new data stored every day is large enough that it would be a major pain to reconstruct a whole day's worth of work even if all of the disaster recovery mechanisms worked very smoothly.
I have a budget that would support duplication of the hardware and software, I. e., I could set up another SBS2000 serveras a hot spare and put SQL Server 2000 on both systems, with a RAID array on both to hold database info. A substantial part of each day's work is stored in the form of Microsoft Word documents that are not stored in the database; these are stored on a dedicated disk partition. There are quite a lot of these, more than 150,000 the last time I looked.
What I need is a good way to replicate the day's work from the live system to a hot spare system so that the spare could be brought up very quickly after a failure without losing much work. SQL Server 2000 supports several kinds of replication, but that doesn't help with the vast pile of Word documents.