Anyone deployed stretch clustering ?

Ive come across this article
http://www.microsoft.com/technet/pro...y/hasog05.mspx
and was interested in stretch clustering .. and have one node of my cluster
in a geographic dispersed location ..
Has anyone done that and can elaborate more on the storage section of this
doc.. We have EMC SAN in place and curious on the technology of how to make
those 2 SANs appear to be one SAN to the MSCS cluster.. Basically if i setup
a 3 node cluster with 2 passive.. each of the passive nodes being on
different geographical sites and my priority of failover would be is Prodn
Server A fails, then it would failover to the local passive node and if
thats not available ( due to site failure) then move to passive node on the
other site.. Is this possible ? Love to hear more
Hassan,
You would need to first implement a remote mirroring solution with your SAN.
EMC's solution, SRDF (Symmetrix Remote Data Facility), is one of the only
solutions that has been qualified for geographically dispersed Microsoft
clusters. If you implement SRDF, you should also look into EMC's
SRDF/Cluster Enabler for MSCS product (formerly known as GeoSpan) to
automate the failover to the remote site. It's a nice solution and it works
quite well.
If you're considering a geographically dispersed clustering solution, you
might want to take a look at the following KB article for some of the
restrictions/limitations of such a solution:
http://support.microsoft.com/?id=280743
Regards,
John
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ezMQejIkEHA.1996@.TK2MSFTNGP09.phx.gbl...
> Ive come across this article
> http://www.microsoft.com/technet/pro...y/hasog05.mspx
> and was interested in stretch clustering .. and have one node of my
cluster
> in a geographic dispersed location ..
> Has anyone done that and can elaborate more on the storage section of this
> doc.. We have EMC SAN in place and curious on the technology of how to
make
> those 2 SANs appear to be one SAN to the MSCS cluster.. Basically if i
setup
> a 3 node cluster with 2 passive.. each of the passive nodes being on
> different geographical sites and my priority of failover would be is Prodn
> Server A fails, then it would failover to the local passive node and if
> thats not available ( due to site failure) then move to passive node on
the
> other site.. Is this possible ? Love to hear more
>
>
|||One challenge u may face with stretch is the fact that the IP Heartbeat has
to be on same subnet and have a guaranteed roundtrip of <500ms as per below
http://www.microsoft.com/technet/pro.../geoclust.mspx
Also with 3 node you will need either Datacenter or Windows 2003
Andy.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ezMQejIkEHA.1996@.TK2MSFTNGP09.phx.gbl...
> Ive come across this article
> http://www.microsoft.com/technet/pro...y/hasog05.mspx
> and was interested in stretch clustering .. and have one node of my
cluster
> in a geographic dispersed location ..
> Has anyone done that and can elaborate more on the storage section of this
> doc.. We have EMC SAN in place and curious on the technology of how to
make
> those 2 SANs appear to be one SAN to the MSCS cluster.. Basically if i
setup
> a 3 node cluster with 2 passive.. each of the passive nodes being on
> different geographical sites and my priority of failover would be is Prodn
> Server A fails, then it would failover to the local passive node and if
> thats not available ( due to site failure) then move to passive node on
the
> other site.. Is this possible ? Love to hear more
>
>
sql

Any fix for internal server error on SQLXML 3.0 and server 2003?

After developing a SQLXML SOAP app using XP pro, I've gone to deploy
it and discovered that SQLXML's SOAP doesn't seem to work on Windows
server 2003. Research on Google shows tons of people having the same
problem over the past year or so, but no solutions that seem to work.
Here's where I'm at:
- Installed Windows server 2003 + IIS 6
- Installed Soap Toolkit 3.0
- Installed SQLXML 3.0 SP2
The virtual directory is created, along with the soap virtual names
and methods. Gettings the WSDL works fine using
http://server/soap/name?WSDL , and if I allow sql= queries, the DB
connection clearly is working because
http://server/soap?sql=select+@.@.version works fine.
However, any attempt to use the actual SOAP resource results in the
infamous (and misspelled) "Internal server error occured. Request
aborted.".
The soap DLL is definitely registered; the ISAPI extension shows up in
the IIS web services extensions as allowed, and the isapi DLL is set
as the wildcard extension for the virtual directory. I've tried
putting quotes around the executable name in the configuration of the
virtual dir.
Has anyone gotten this to work, or is there definitive word that it
cannot work?
Thanks
-Brooks
I have had this exact same problem with Windows 2003. However, I have not found a solution yet. Like you, I have tried everything that has been posted in newsgroup articles but still no luck.
The use of SQLXML with Windows 2003 Server seems to be a bit middled since the instalation instructions state that the SOAP Toolkit is a pre-requisite, yet there is a Microsoft KB article (KB811215) stating that the SOAP Toolkit is only supported on Windo
ws 2003 Server for client-side components and client-side applications.
I think that Micosoft need to refresh their SQLXML information in light of Windows 2003 and the imminent withdrawl of the SOAP Toolkit.
Mark.
|||We're working on this as we speak. SqlXml included in Sql Server 2005 will
not have this requirement. We're also working on plans to release it
sooner. As soon as I have details this group will be the frist to know, I
promise!
Thanks,
Irwin
Irwin Dolobowsky
Program Manager - SqlXml
http://blogs.msdn.com/irwando
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Abrams" <anonymous@.discussions.microsoft.com> wrote in message
news:6019E7CE-3AB3-4B24-AB9B-EB7AF4D85871@.microsoft.com...
>I have had this exact same problem with Windows 2003. However, I have not
>found a solution yet. Like you, I have tried everything that has been
>posted in newsgroup articles but still no luck.
> The use of SQLXML with Windows 2003 Server seems to be a bit middled since
> the instalation instructions state that the SOAP Toolkit is a
> pre-requisite, yet there is a Microsoft KB article (KB811215) stating that
> the SOAP Toolkit is only supported on Windows 2003 Server for client-side
> components and client-side applications.
> I think that Micosoft need to refresh their SQLXML information in light of
> Windows 2003 and the imminent withdrawl of the SOAP Toolkit.
> Mark.
>