Omni-NFS-Series

Example one: MS SQL/IIS web server data replication and failover

Highlight: a small auto part shop needs to backup database and web server files to off site location and keep the web server running 24x7

 Tom and Kay are partners of a successful auto parts distribution business: ABC Auto Parts. They use a Windows 2003 server to run SQL database for keeping customers’ and products’ information. This Windows 2003 server also hosts their web site for online advertising and sales. 

 With the online business going global and sales growing exponentially, they decided that it is important to keep the web server up 24x7. They learned that server failover is the way to go.

Along the way, they also learned that it is equally important to prevent the loss of customer and products information stored on the computers. So, they set out to find a data protection and failover product.

 They found Xlink’s ClusterReplica ENT. From reading the online documentation, they learned that ClusterReplica ENT could replicate data to multiple systems in different locations whenever a new piece of data is entered into the computer. It can also carry out automatic failover of both SQL database and IIS web server services. The cost for the software is within their budget range. Xlink’s ClusterReplica ENT is what Tom and Kay looking for.

 They bought Xlink’s ClusterReplica software and bought two additional Windows systems, one Windows 2003 server and one Windows XP professional for the arrangement. The Windows 2003 server is used as the Secondary station for failover. It is to be placed in the shop to be ready to take over the server functions. The Windows XP system is to be used as a remote backup set in Tom’s house in the basement. Tom’s house is about 30 miles away from ABC Auto Parts.

 Downloaded the software from Xlink’s web site, Tom and Kay installed the software by themselves in following steps:

1.       Install ClusterReplica ENT on the Windows 2003 system currently running in the store and set it as the Primary station.

2.       The newly purchased Windows 2003 server is labeled as system A, and the Windows XP system B. On both systems, the MS SQL server 2005 and IIS web server are installed and configured.

3.       ClusterReplica ENT is then installed on both systems as Replica Member stations. Tome takes system B to his house and set it up in the basement, and leaves system A in the store.

4.       From the Primary station, Kay first defines system A as the Secondary station, and then defines system B to be a remote Replica Member for real-time data replication.

5.       The remote backup server has the Data Version Management function turned on so that multiple versions of all files are kept for effective roll back should a mistake is done on the active server. The file retrieving can be done remotely from the shop  without having to go to Tom’s basement.

 With this setting:

1.       Whenever there is a piece of new data entered into the Primary station, it is immediately replicated to system A and system B. This process protects data from accidental deletion and data corruption.

2.       Should there is a fire or flood or power off in the store, system A, sitting in the basement of Tom’s house, will take over the server role to keep the IIS web server on for network client connection.

3.       System A will keep in sync with the Primary station at all times of the applications and data files. So, if a file is removed from the Primary station, it will also be removed on system A.

4.       System B, on the other hand, does not work the same way. It keeps all file received but never remove any of them. Older records of customers and parts can be found here.

Tom and Kay got it all setup in one afternoon. The cost of the new system is also within their expectations. From now on, they will not worry about loosing customers due to natural disasters or human errors.