[THIN] Re: Slightly OT: SQL Redundancy
- From: "Steve Greenberg" <steveg@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 12:35:10 -0700
Henry,
Thanks, that is a good explanation and exactly what I was looking for....
Regards,
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd D8453
Scottsdale, AZ 85262
(602) 432-8649
www.thinclient.net
steveg@xxxxxxxxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Henry Sieff
Sent: Tuesday, August 16, 2005 12:24 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Slightly OT: SQL Redundancy
Within SQL you can replicate and log ship.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlma
g01/html/LogShippinginSQLServer2000.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlma
g01/html/LogShippinginSQLServer2000.asp is a description of logshipping,
basically - you backup your tlogs on your production sql server and
restore them to your standbye. It gets a good copy of the db as of the
last shipment. Failover is manual, and this is a clunky way of doing the
job.
Clustering SQL server under normal circumstances uses a shared storage
space. SQL Server 2000 is cluster aware. Once you set up your MSCS
cluster, you create the pre-requisite cluster resources for SQL server
(Servname, IP Address, and at least one clustered physical disk resource
besides the cluster quorum). You run the SQL 2000 setup, and it detects
that you have MSCS and guides you from there.
Now, you could set up MSCS and cluster a network name and ip with the
shared quorum disk, and then install a local unclustered copy on SQL
server with local disk resources for the data on each node with
replication or logshipping, and just use MSCS to switch that network
name/ip address between the two. Clients would just point to the
clustered name or ip address. That would give you what you want.
--
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 Steve Greenberg
> Sent: Tuesday, August 16, 2005 1:07 PM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Slightly OT: SQL Redundancy
>
> Can anyone clarify exactly what MS offers in their clustering
> in relation to SQL. For example, I know you can Replicate SQL
> and you can cluster it. When I think of cluster I think of a
> shared disk space that both servers access, when one server
> fails the other takes over looking at the same physical data
> location. When I think of replication I think of two servers
> with separate disks replicating data across servers and disk
> space. Does MS offer the option to replicate to two separate
> SQL servers with separate disk storage AND failover
> automatically, i.e. server 2 takes on the network identity of
> server 1 automatically?
>
>
>
> I understand that Double Take does this, I am just trying to
> clarify whether MS offers the same features or not.
>
>
>
> thanks
>
>
>
> Steve Greenberg
>
> Thin Client Computing
>
> 34522 N. Scottsdale Rd D8453
>
> Scottsdale, AZ 85262
>
> (602) 432-8649
>
> www.thinclient.net
>
> steveg@xxxxxxxxxxxxxx
>
>
>
> ________________________________
>
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Mann
> Sent: Tuesday, August 16, 2005 10:07 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Slightly OT: SQL Redundancy
>
>
>
> No I did not. Was after failover/high availability more so
> than clustering for more performance. Ended up just adding 2
> additional SQL servers when things started to getting heavy,
> of course this means even more hardware sitting around idle
> and even more licenses to buy, but since the servers are all
> spec'd the same, it gives me a lot of spare hardware to play
> with in the event of failures.
>
>
>
> ________________________________
>
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
> Sent: Tuesday, August 16, 2005 1:04 PM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Slightly OT: SQL Redundancy
>
> Thanks, did you also evaluate the GeoCluster product as well?
>
>
>
> Joe
>
>
>
> ________________________________
>
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Mann
> Sent: Tuesday, August 16, 2005 8:56 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Slightly OT: SQL Redundancy
>
>
>
> Double-Take.
>
>
> I successfully replicate with it, AND have successfully
> migrated to a newer SQL server using it. I tried to do an
> automatic failover, but it didn't work properly because the
> Double-Take service wasn't running as a Domain Admin, so it
> couldn't rename the computers in AD properly.
>
>
> Aside from that, the database aspect of it was 100% flawless.
> It does bit-by-bit replication of files, so as long as you
> replicate all your DBs, master, etc., it will work great.
>
>
>
>
>
>
>
> ________________________________
>
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
> Sent: Tuesday, August 16, 2005 11: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:
