Database redundancy in Cimplicity

Hi,

I have two redundant Cipmlicity servers (8.2 SIM 24) and one viewer. I have done the following configuration regarding the DNS's and data logging:

1- At the Primary server:
a) ODBC connection (Name: FIRST SQL) to look at PRIMARY\CIMPLICITY database
b) ODBC connection (Name: SECOND SQL) to look at SECONDARY\CIMPLICITY database

2- At the Secondary server:
a) ODBC connection (Name: FIRST SQL) to look at PRIMARY\CIMPLICITY database
b) ODBC connection (Name: SECOND SQL) to look at SECONDARY\CIMPLICITY database

3- In Cimplicity Database Logger settings I have configured following DSN's;
Point Connection-Master: FIRST SQL
Alarm Connection-Master: FIRST SQL
Point Connection-Slave: SECOND SQL
Alarm Connection-Slave: SECOND SQL


I'm facing a problem in the logged data when I do the following scenario:

1- Both servers are running ----> Data is logged in both Primary & Secondary databases.

2- Primary server is shutdown ----> Data is logged in the Secondary database.

3- Primary server is up again ----> Data is logged in both Primary & Secondary databases but they are not synchronized.

How can I guarantee that if any of the databases is not available for nay reason will get synchronized by the active one when it becomes available again?? :confused:

Appreciate ur help.