Achieving Server Redundancy at Remote Offices

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Mark Cook » Achieving Server Redundancy at Remote Offices...

20 posts, Page 2 of 2

««1 2

Achieving Server Redundancy at Remote Offices

Rate Topic

Display Mode

Topic Options

Author

Message

K. Brian Kelley

Posted Thursday, May 25, 2006 9:37 AM

Keeper of the Duck

Group: Moderators
Last Login: Yesterday @ 1:13 PM
Points: 6,584, Visits: 1,790

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

Nope, you got it. That's what I was looking for. I didn't see that in your article and this is an area some organizations miss.

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 #282837

Mark F. Cook

Posted Thursday, May 25, 2006 9:43 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61

thanks for the comments so far, all are appreciated and noted...

Post #282844

Hoang Binh

Posted Thursday, May 25, 2006 11:04 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, May 16, 2013 2:16 AM
Points: 1, Visits: 9

A question please.
When failure occurs in the primary server, how can you get data from the last synchronization to the time before the failure?

Post #282877

Mark F. Cook

Posted Thursday, May 25, 2006 12:16 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61

depending on the availability of the server, you may be able to ship the last log, etc. if the server is completely unavailable, there's not much you can do except accept that some data will be lost. what we tried to do was to gauge how much time we could afford to lose in the event of a system failure. obviously you can configure longer or shorter time intervals, but the less time you can afford to lose, the more you need to look at something like clustering or perhaps database mirroring in SQL2K5 that provides more real-time synchronization.

Post #282887

Andy Warren

Posted Tuesday, May 30, 2006 6:58 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

Did you consider replication as an option?

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #283551

Mark F. Cook

Posted Tuesday, May 30, 2006 12:38 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61

sorry, posted this earlier but apparently i had some issue with my connection. anyway, to be completely honest, we probably should have included it as an option. we were/are aware that its was possible to use replication in this way, but most of what we read in posts, etc steered us away from using it for failover.

Post #283669

Charles Tsang

Posted Friday, May 25, 2007 4:48 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, January 25, 2013 4:49 AM
Points: 6, Visits: 264

On a course I was on, the passive server in a database mirroring setup for SQL2005 was said to be acting in unlicensed mode. This would mean that full functionality was not available (reporting/analysis).

Have you found this to be the case for your situation where the passive server is unlicenced?

Charles

Post #368959

Mark F. Cook

Posted Friday, May 25, 2007 6:27 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61

There isn't any real limitation to the functionality of MSSQL with log shipping - at least not the "roll your own" kind i've used in the past. In my experience with log shipping (SQL2K), the destination database can be accessed by users in between the times when logs are restored to it. At that point, user connections have to be killed as the database needs to be in single user mode.

My understanding of licensing is that if the destination server is used only for failover, a second license isn't required. However, if you allow users to connect to it, i would think a second license would be necessary.

Post #368981

netmikem

Posted Friday, May 25, 2007 4:06 PM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Sunday, May 19, 2013 4:27 PM
Points: 570, Visits: 224

Hi Mark.

This topic is dear to my heart these days as I've recently been charged with BCP for our firm.

One of the guys working with me suggested the use of a CNAME DNS entry to achieve something similiar to what you did with the IP address solution. The idea is to have a generic server name that can be resolved to a real machine name and in the event of the production server going down, you simply change the CNAME entry to the secondary machine.

For example, consider the following configuration. The production database server is named PROD and the failover one is called EXTRA. You would create a CNAME DNS entry named DBSERVER and point it to PROD.

All applications would be configured to connect to DBSERVER.

If PROD ever went offline unexpectedly, you would change the CNAME DNS entry for DBSERVER from PROD to EXTRA.

We've tested it and it seems to work like a charm.

I'm interested to know if you considered this approach but decided the IP address strategy was better for some reason?

Regards,

- Mike

Post #369202

Mark F. Cook

Posted Friday, May 25, 2007 8:08 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 21, 2010 8:23 AM
Points: 116, Visits: 61

Mike

it sounds like a good approach but one we never considered. I'll be interested in trying it at some point.

thanks
mark

Post #369213

« Prev Topic | Next Topic »

20 posts, Page 2 of 2

««1 2

Permissions