all groups > sql server new users > april 2006 >
You're in the

sql server new users

group:

New to Clustoring/Failover Questions


New to Clustoring/Failover Questions Dennis Burgess
4/22/2006 11:18:54 AM
sql server new users:
Simply put we have a Single SQL 2005 server running our applications. This
server runs great, low load, databases under 200 meg mostly, maybe 2 gig of
total data.

We do backup via NetVault to tape everynight.

What we want though, is a SECOND, physical server with the same databases,
that preferrably, with either do 1 of 2 things.

1. If server 1 is not running, failed, whatever, server 2 will take over
within decent amount of time. No configuration on user end needed.
2. If server 1 not running, whatever, be able to have a backup sql server
with the latest data that was avabiled from Server 1 to be able to add an IP
or whatever to get the sql server going for end users.

Thats is, no HIGH load, no massive issues, just want a simple way to be able
to be back up quickly in the event of a physical server failure. Both
servers are P4 3.0 gig with 4 gig RAM and RAID 5 arrarys. They are
phsycaially identical.

Suggestions, comments?

We are not running vitual server, so I think that rules out clusting, we are
just running Windows 2003 with the latest service packs, gigabit nics.

Thanks in advance!

Dennis

RE: New to Clustoring/Failover Questions Linchi Shea
4/23/2006 7:29:01 PM
As far as HCL is concerned, constructing a cluster out of the servers on HCL
doesn't make the cluster certified for Windows 2000/2003. Clusters are a
separate category all by itself. See
http://www.microsoft.com/windows/catalog/server/default.aspx?subID=22&xslt=hardwarehome

Linchi

[quoted text, click to view]
Re: New to Clustoring/Failover Questions Hugo Kornelis
4/24/2006 12:38:23 AM
[quoted text, click to view]

(snip)
[quoted text, click to view]

Hi Dennis,

Sounds like a scenario for database mirroring. This new feature was
included but not officially reported in the RTM version of SQL Server
2005; since the release of Service Pack 1 last week, it is now also a
supported option.

You can set up two servers: one as principal, one as mirror. All changes
on the principal server are automatically forwarded to the mirror. When
the principal server fails or has to be taken offline for planned
maintenance, you can tell the mirror to take over the role of the
principal server ("manual failover").

If you can afford a third server, you can set it up as a "witness
server". The witness watches the status of the other servers and tells
the mirror server to take over the role of the principal server when the
principal server fails ("automatic failover").

(I believe that you can also set up a second SQL Server instance on the
mirror server as the witness server, but that reduces the reliability of
the database.)

--
RE: New to Clustoring/Failover Questions Linchi Shea
4/24/2006 10:47:01 AM
Oops! I apologize for replying to the wrong thread. Meant to reply to the
'Hardware Match' thread. Should have double-checked before clicking on Post.

Linchi

[quoted text, click to view]
AddThis Social Bookmark Button