Thanks for your input. From what I have seen of SANs, they simply cannot
beat SCSI RAID in terms of performance for the dollar. The DB we're looking
logs. SANs that can approach that level of performance all appear to be
implement failover clustering at this time. It looks like we will go with
log shipping or perhaps transactional replication.
"Don Wilwol" <donWilwol@(EMAIL)yahoo.com> wrote in message
news:%23qLS7BcrFHA.1236@TK2MSFTNGP10.phx.gbl...
> [SEE inline]
>
> --
> Hope it helps
>
> dw
>
> _______________________________
> Don Wilwol
> donwilwol(DELETE)@yahoo.com
>
http://spaces.msn.com/members/wilwol/ >
>
> "John" <jglass67@msn.com> wrote in message
> news:el42cpWrFHA.2996@tk2msftngp13.phx.gbl...
> > Hello,
> > We are looking to implement (finally) some redundancy into our SQL
Server
> > setup. We are interested in failover clustering, but from what we've
seen
> > so far most people use a SAN to implement it.
>
> You are seeing scsi attached clusters less and less as SAN prices come
down,
> but there are still plenty of them out there. Its still a viable solution.
>
>
> We'd prefer using independent
> > servers, each with their own RAID array (similar to replication, but
with
> > the seamless failover capabilities of clustering). Is this scenario
> > possible or recommended?
>
>
> There are third part applications that make this possible. I'm in the
> process of testing NSI's Double Take and Geo cluster applications right
now.
> We hope to use it to set up a DR site for both SQL and Exchange. I've also
> heard of one called neverfail that I haven't looked into, but may just to
> see what its like.
>
> > Thanks,
> > John
> >
> >
>
>