Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Achieving Server Redundancy at Remote Offices Expand / Collapse
Author
Message
Posted Tuesday, April 25, 2006 10:26 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/mcook/achievingserverredundancyatremoteoffices.asp


Post #275406
Posted Thursday, May 25, 2006 6:41 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, August 8, 2007 2:25 PM
Points: 53, Visits: 1

I'm not sure I follow these IP addresses:

 

Production Server: Name : PROD1 IP : XXX.XX.XX.223

Secondary Server: Name : LOGSHIP1 IP : XXX.XX.XX.224

We create an alias like this:

Alias : Name : PROD1V IP : XXX.XX.XX.223

 

shouldn't there be 3 total?

 

Post #282731
Posted Thursday, May 25, 2006 6:51 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61
It depends. sounds like a microsoft answer doesn't it. But seriously, if you include the unused IP address the failed production server gets changed to then yes - 3 IP addresses will be needed. If you're only talking about normal production operation, then you only need two - one for the alias and the production server and another for the log shipping server.



Post #282737
Posted Thursday, May 25, 2006 7:12 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, June 12, 2009 7:37 AM
Points: 125, Visits: 115
Great article.  - Tim Chapman
Post #282748
Posted Thursday, May 25, 2006 7:59 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 870, Visits: 912
Good article.

By the way, it sounds like you've got a couple of unused licenses.

You do not need to buy a sql server or windows server license for the passive server - either in log shipping or clustering. Unless of course you're using the SQL Server for other, non-passive, purposes.

Taken from Microsoft's licensing white paper:

"When doing failover support, a server is designated as the passive server. The purpose of the passive server is to absorb the data and information held in another server that fails. A passive server does not need a license, provided that the number of processors in the passive server is equal or less than those of the active server. The passive server can take the duties of the active server for 30 days. Afterward, it must be licensed accordingly."



Karl
source control for SQL Server
Post #282774
Posted Thursday, May 25, 2006 8:02 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61
thanks for the information. I knew only one license was needed when using Microsoft Log Shipping included in Enterprise edition, but thought that anything outside that required additional licenses. Again, thanks...


Post #282783
Posted Thursday, May 25, 2006 8:36 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, November 17, 2014 9:13 PM
Points: 311, Visits: 526

You're probably better off maintaining the second license if you go ahead with your strategy of having the secondary work for multiple primaries.  It might be in use frequently, albeit for short periods each time.

But... if you have multiple primaries for the secondary, I don't think your switch of the secondary's IP address and alias is going to work as well.  What if two primaries fail at once?  It's unlikely, I'm sure, and this article is a good treatment of a reasonable, low-cost and responsible method.  Thanks!

Post #282797
Posted Thursday, May 25, 2006 8:41 AM


Keeper of the Duck

Keeper of the Duck

Group: Moderators
Last Login: Friday, November 14, 2014 7:14 AM
Points: 6,625, Visits: 1,876
How are you handling network outages?


K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of Introduction to SQL Server: Basic Skills for Any SQL Server User
| Professional Development blog | Technical Blog | LinkedIn | Twitter
Post #282799
Posted Thursday, May 25, 2006 8:45 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61
thanks for the comments. you're correct, the setup can accommodate only a single failure in the multiple primary-single secondary situation, but our assessment was that you can go pretty far down the proverbial rabbit hole in trying to achieve redundancy, and that this was as you said a reasonable, low-cost solution....


Post #282802
Posted Thursday, May 25, 2006 9:03 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61
the two servers - primary and secondary are located next to each other on the local lan. In the event that there is a problem with the primary and we need to failover to the secondary ... and the wan link is down, there are procedures in place that a designated person at the facility can be guided through by a DBA....or did i miss your point entirely...


Post #282815
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse