I am using IDS 7.31UC5 on SCO UNIX 5.0.5. I have an HDR setup in Async Updating mode. I believe that using this scenario, there is the possibility of having committed transactions in the Primary, and in case of some failure, these same transactions are not committed to the Secondary. These lost transactions can then be found in a "lost-and-found" file. The Secondary, in this scenario, remains as a Secondary server.
Let's say I was able to bring the Primary server up and started HDR again. Transactions are also happening on the Primary.
Will the transactions in the lost-and-found file be replicated and committed to the Secondary before any other logs are sent?
I need some clarification on this matter as the Admin Guide doesn't have a lot of information on it.
Let's say I was able to bring the Primary server up and started HDR again. Transactions are also happening on the Primary.
Will the transactions in the lost-and-found file be replicated and committed to the Secondary before any other logs are sent?
I need some clarification on this matter as the Admin Guide doesn't have a lot of information on it.