Roger, the bigger challenge / cost here isn't the link (as you don't need 2
WAN links between the sites for HB and Public traffic), it is the need to
replicate your storage if you were to deploy a Multi-site Failover Cluster.
I'd probably look into database replication initially and see if that will
serve your needs...
Hope this helps,
--Ryan
--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
"Roger Nome" <> wrote in message
news:...
> Hi Guys,
>
> Just looking for some direction on how to tackle a specific problem.
>
> I have a customer who has one site. All the machines are Windows 2003
> Standard Server 64bit.
>
> There are the following:
> - Domain Controller
> - SQL 2005 Box/App Server
> - Terminal Server
>
> The customer wants a disaster recovery site. Only the SQL 2005/App Server
> box needs to at the DR. What is the easiest solution to do this?
>
> My think was to roll up to 2008 Advanced server and create a cluster. The
> problem is, the link between the two are on a dsl link. It's a controlled
> dsl link as this is a medical company. I think there needs to be two
> links, one for the heartbeat and one for the normal traffic.
>
> Am I on the correct wave length here?
>
> Looking for other solutions if you have any ideas.
>
|