Constantly sync one PC to another.

[Peon]

Hi Forumites!!!!!

I have a client that needs an immediate failover backup system for a small server. The server is running a piece of software called Mede-mass.

What the client would like is that should the primary PC server box fail for whatever reason they can simply switch over to the seconday box. What happened is that the servers NIC failed this weekend.

What im thinking of doing is using Windows Live Mesh. Should they wish to use the seconday PC then they simply run the netsh script which will change the IP of the secondary box to that which was used by the primary. Then restart so that the Mede-mass server component has bind on port and IP.

Can anyone suggest alternate ideas, perhaps out of the box solutions?

Yours faithfully, the hard working Peon, chopping down trees since 1994
Peon

 

[$m@Rt@$$]

I run have an identical 2nd microserver and run the drives in mirror (through windows disk management). Should the one machine fail I just change the ip address and load one of the mirrored drives and boot it up. A for away.

 

[Peon]

I run have an identical 2nd microserver and run the drives in mirror (through windows disk management). Should the one machine fail I just change the ip address and load one of the mirrored drives and boot it up. A for away.

Thats a good idea.

 

[ponder]

How about a mirrored cluster with automated application failover & virtual IP?

 

[Peon]

How about a mirrored cluster with automated application failover & virtual IP?

Cost implications? Its just serving 3 users.

 

[Nerfherder]

You could also use a load balance so that you don't even need to do anything, if one site dies it will automatically balance to the other.

 

[[email protected]]

I second the mirror factor

 

[WAslayer]

seems that the software uses a database to store its data.. so assuming that windows live mesh plays nice with the database application, you should be okay there.. id say find a load balancer solution, that will auto switch between servers, to avoid needing user intervention and increasing the risk of id 10 t errors..