Jump to content

Recommended Posts

Posted

Hi Everyone

 

Just wanted to get some feedback on my ideas.

 

We are having all our servers replaced in July and I was wondering if we could cluster our Sims servers to provide failover support. What I am thinking of is to have two servers running the full version of SQL 2005 with load balancing enabled. Then to provide failover for the SIMS s:\ drive to use some sort of DFS distributed file system software to mirror the Sims folder across the two servers.

 

Has anybody else got this set, or looking to something like this, any help would be great

 

Cheer

 

Matt

Posted (edited)

You can't use the built in load balancing with SIMS.net, it isn't supported. The reason I saw was that it changes the schema of the DB in some way. What was suggested was a sort of 'semi-failover', ie. Run a backup of the DB and attach it on a second server at a specific frequency.

 

Then you could use something like Nagios, and a couple of scripts to switch things around should a failure occur.

 

This would mean that any changes made between backups would be lost though.

 

EDIT: I have been informed that the stance has changed since I was told MSSQL clustering doesn't work. According to Capita Supportnet's KB72633 it will work, so long as you follow their instructions.

Edited by localzuk
Posted

You can use SQL Server mirroring though this will provide a backup should the primary server fail you'll need a heartbeat type server to change the secondary to the primary and vice versa this will work as long as sims use the sql native client not some freakish monster to connect to the server (You may have to change the connect.ini file as well to allow when failing over)

 

Wes

Posted
When I spoke to our local support team about this I was told that it is possible and there is one local(ish) school doing it but Capita don't fully support it so we would probably, unless we have a lot of experience with SQL, need outside support to set it up and maintain it. Also, I'm not sure, but I think clustering needs the enterprise version of SQL server which makes it very expensive. We have gone for the low tech but cheaper solution of having a second - lower spec - server with SIMS installed and kept up to date on to which we can restore our latest database back up. This gives us down time of < 1/2 an hour with a potential data loss of 1 day - back to last nights backup. It has been agreed that this is an acceptable compromise
Posted

If you're setting up anything new and whizzy which might take a lot of time (particularly multiple SQL Servers) don't forget that you're going to need to migrate from SQL 2005 to SQL 2008 at some point between October 2009 and October 2010.

 

Just worth bearing in mind.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...