On 2/14/2015 12:19 AM, Mayank Kumar (mayankum) wrote: > Thanks all for the responses. Just want to clarify the scenario one more > time:- > > -by syncing, I mean taking the modifications on the active machine and > sending over wire to another machine(in some proprietary format) , where > there is a similar sqlite application which receives the records and the > records are written to a sqlite db residing on that machine using a sqlite > apis. > -when the two sqlite applications come up on the active and standby machines > for the FIRST time, we ALSO do a rsync of the sqlite db from the active to > standby to make them same and then subsequently sqlite applications keep in > sync using the mechanism I highlighted in 1 above. In this process, when we > do a rsync, does it make sense to copy the journal file which was created by > the application, so that after the rsync is completed and the sqlite > application on the standby side comes up, it can recover any lost > transactions before it starts to receive record by record copies which it > will write to its own db using sqlite apis.
Thank you for the much clearer explanation, and in this case, yes definitely, copy the entire DB file-set - in fact, leaving the journal out might break it as Richard mentioned before. > I hope I have not introduced more confusion. > Quite the contrary...
