SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Making databases highly available with SAN...


Making databases highly available with SAN...

Author
Message
chrisph
chrisph
Old Hand
Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)

Group: General Forum Members
Points: 357 Visits: 623
Hey folks,

I am going to be setting up a new sql instance in the next while at work and I want to make it have high availability/fail-over. I want to put the database files up on our SAN and have 2 physical servers clustered together.
Is there a better way to do this, perhaps utilizing mirroring with SQL (though I believe that would eliminate the ability to use the SAN) or some other technology that would produce good performance?

I know this is a pretty broad question but I want to see what others think before I pull the trigger on this.

Thanks
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87317 Visits: 45272
Not really enough info there.

To decide on a HA/DR setup you need to start with the data loss and downtime SLAs and go from there, also budget and some idea of what kinds of disasters the solution has to withstand. Also, clustering has a single-point of failure in the storage and no redundant copy of the data. Log shipping and mirroring have two (or more) copies of the data.

Ha/DR setups have nothing to do with performance. You cluster or mirror or logship to survive the failure of some component or components

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


chrisph
chrisph
Old Hand
Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)Old Hand (357 reputation)

Group: General Forum Members
Points: 357 Visits: 623
The SAN has redundancy built in so that is why I am leaning towards it.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87317 Visits: 45272
chrisph (11/14/2012)
The SAN has redundancy built in so that is why I am leaning towards it.

Err......
Check with your SAN vendor that whatever form of 'redundancy' they have is certified to work with SQL Server databases, otherwise your 'redundant' copy may be a waste of bits.

Everything that I said about HA/DR stands, redundancy in the SAN or not. HA/DR design starts with your SLAs, not your hardware.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Robert Davis
Robert Davis
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2752 Visits: 1623
Gail wasn't advocating not using a SAN. She was merely saying not to count on the SAN's redundancy to save you in a disaster. If the whole SAN goes down, built-in redundancy is gone too. Mirroring and log shipping gives you multiple copies of the data, but if you put all partners on the same SAN, you lost that redundancy as well if you lose the whole SAN.

As Gail stated, it depends on what you are trying to protect against and what your SLAs are (how much data can you lose and how long can you be down for in the case of a disaster).



My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master, SQL Server MVP
Database Engineer at BlueMountain Capital Management
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search