J
Joost Haakman
Guest
Hi All, I want to implement online backup and after imaging for our application. I am actually a bit reluctant to do so because there are some “features” in our application that worries me in terms of losing the integrity of the data that is divided over multiple databases. There are 2 things that bother me about our application: We have quite a few transactions that write data to multiple databases at the same time. I can’t be sure that all the “logical” transactions mentioned at point 1 , aren’t in fact 2 or more physical transactions. What worries me is that when I restore data and I have made my backups online and/or have after imaging enabled, I can never be sure that the records that are divided over all these databases and belong together are all restored. Resulting in an application that will behave erratically. I know about Two-phase commit and if I understand it correctly this would solve data integrity issues that would otherwise be the result of the transactions mentioned at point 1. I don’t believe this would prevent the loss of data integrity in the case of a transaction mentioned at point 2. This is a long introduction for the following questions I actually want to ask you: - What steps should be taken to ensure data integrity over multiple databases when performing an online backup? - What steps should be taken to ensure data integrity over multiple databases when after imaging is enabled? - What are the conditions under which data integrity over multiple databases can be assured? I want to thank you for reading this far and I hope you can provide me with some insight in this matter. Or perhaps some answers. Kind regards, Joost.
Continue reading...
Continue reading...