[THIN] Re: Slightly OT: SQL Redundancy
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 10:18:06 -0700
Thanks,
Did you implement replicated SAN? One of the sore spots is despite the
current SAN having all redundant controllers, multi-path, switches, etc. It
still became unavailable due a stupid bug in the logging agent on the
brocade switches. Taking down, not just one, but ALL of the fibre switches
that connect to the storage unit.
Joe
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Henry Sieff
Sent: Tuesday, August 16, 2005 9:38 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Slightly OT: SQL Redundancy
I use MSCS with a FC SAN for clustered SQL and File Servers. The
back-end SAN does most of the fault-tolerance (redundent controllers,
RAM Cache, multiple paths to data, RAID, etc).
Failover times vary with the number of clustered resources. On the low
side (3 clustered disk resources, 1 instance of SQL server/SQL Agent
with the prereq'd clustered network name and ip address) the failover is
done in about 10 seconds + however long it takes to startup the db's on
the sql server, which depends on the recovery time you have set and the
number/size of the db's. I would think that if it were dedicated to IMC
datastore, it would be about 2 additional seconds on that, since those
are small.
We don't dedicate, so we usually look at about 20-30 seconds for a
failover. It is completely transparent to the farm - the active node
uses the clustered ip address in addition to its own node ip address,
and the clustered name will point to that in WINS/DNS, so the farm won't
even notice the change.
The only downside is the cost: you have to double your hardware
purchase, and unless you do active/active clustering (where you run two
virtual instances of SQL server, one on each node) you have half your
capacity idle. You also need to have the shared storage, but that isn't
that expensive anymore.
--
Henry Sieff
Network Engineer
ph. 504-620-3420
mob. 504-931-4638
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
> Sent: Tuesday, August 16, 2005 10:55 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Slightly OT: SQL Redundancy
>
> Hello,
>
>
>
> What a success (or failure) has the group encountered in
> making SQL servers Highly Available? Either through
> clustering (Microsoft or third-party) or replicated partners.
> We are looking to move the Citrix DataStore and a few
> application databases to a HA solution, while minimizing the
> impact to farm in event an HA partner goes down.
>
>
>
> Joe
>
>
********************************************************
This Weeks Sponsor: triCerat Inc.
You need Day Zero Protection!
Get Proactive with triCerat's Simplify Suite.
Solve printing, security and profile problems before they occur.
http://www.tricerat.com/?thethintl2
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Excellent SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Weeks Sponsor: triCerat Inc.
You need Day Zero Protection!
Get Proactive with triCerat's Simplify Suite.
Solve printing, security and profile problems before they occur.
http://www.tricerat.com/?thethintl2
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Excellent SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
