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 |
|
mparter
Yak Posting Veteran
86 Posts |
 Posted - 2004-05-25 : 16:12:58
|
| Scenario:Two sites, approx 10 miles apart. Connected via a 100Mb leased line and a backup 54MB VPN connection between sites. We have a mission crticial SQL Server based application that must be available as much as possible. I did look briefly at clustering but the distance between sites appears to be a potential stumbling block. Site A has a HP SAN solution, Site B has a NAS solution. Both sites will be running Windows 2003 Enterprise Edition and SQL Server 2000 Enterprise Edition.Any advice on potential solutions greatly appreciated.Thanks. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-25 : 17:03:52
|
| Will you need to use both servers or will one just be used for disaster recovery? If for disaster recovery, then look into log shipping whether it be log shipping using Enterprise Edition or your own custom built one.You should really consider moving the second server so that you can use clustering. You should also consider having a disaster recovery site. Here is what we've got:In our main site, we've got two nodes being clustered. At our disaster recovery site, we've got the same environment and it gets log shipped to in case of a disaster. So if there is a hardware problem at the main site, we can utilize clustering to bring up the instance on the other node. But if a site problem occurs, we move to the disaster recovery site. And then while at the disaster recovery site, if we have a hardware problem, we can still use the other node as we've clustering setup there too.Tara |
 |
|
|
mparter
Yak Posting Veteran
86 Posts |
Posted - 2004-05-25 : 17:07:51
|
| As there's users on both sites, the ideal scenario would be some sort of mirrored solution, so that users use their local "copy" of the server. If one fails, then they can failover to the one on the other site until their own one is recovered. Is this asking too much? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-25 : 17:10:35
|
| I've never worked on a solution like this. Mirrored usually means only one system is being used though. To use both sites, you could replicate the data from one server to the next. But failing over would not be automatic.Tara |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-05-25 : 20:15:01
|
| You could do active/active clusters at each site and log ship both active nodes across to the other passive node.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
SQL Redundancy Advice