metta
Just now opened V9 (running on my Win7 desktop), and synced all 4 of the test brains I have open in TB9.

Then I updated TB9 to version 232.

After the new update was finished, I synced each of the 4 test brains again, and I was surprised to see that 2 of the 4 brains synced again, as if new edits had just been made.

Q. Why would 2 of these 4 brains need to sync again after the new version update when they were all synced immediately prior to the update?

Output log attached.
Quote
metta
Also, why are my test brains in TB9 automatically updating when I have the automatic sync turned OFF?
Quote
mcaton
Metta,

Very interesting observation.  I don't have a known reason for sync occurring after an application update if it was recently synced.  I'll roll back and test that scenario.  Also, the 'disabled auto sync still syncing' issue is an older bug that may have found it's way back.  I've flagged this for further testing as well.  Thanks again for noticing.

Matt
Quote
Harlan
When a sync completes, that does not mean that it is completely up to date. Each sync is a single two-way exchange of information. Sometimes it is not possible to get everything completely sync in that single exchange and in this case any remaining changes will be sent on the next subsequent sync.
Regards,
-Harlan
Quote
metta
Puzzling. Is the sync in TB9 working differently from the sync process in TB8?

The reason I ask is that I never noticed a sync in TB8 not being complete. In other words, any sync made from desktop to webbrain was always complete -- as was any subsequent sync from the webbrain to another brain installation.

In addition, each time the sync ran, changes from the webbrain were downloaded while changes from TB installation were uploaded. This always seemed to happen quite reliably and predictably -- and, I confess, TB9 seems be operating somewhat differently.

Is this just my imagination, or is the sync process different in the 2 versions of TB?
Quote
mcaton
The sync process is quite different for version 9. Our v9 "re-engineered from the ground up" motto includes TheBrain Cloud as well as the synchronization process. We much prefer the new process for speed and reliability!

Thank you,
Matt
Quote
metta
Thanks for confirming, Matt. I'm glad if you feel the sync speed and reliability is better in TB9.

I'm hoping that with more experience using TB9 I'll get a better feel for how the new sync process is working, and I have my fingers crossed that the recent data loss I experienced in 2 different V9 brains was simply a strange anomaly.
Quote
metta
For years now I have opted to sync all my brains manually, in order to avoid inadvertently overwriting anything with an automatic sync. In light of this, is it important to me to have a full and clear understanding of how the sync process is working TB9.

To this end, I've reviewed Harlan's detailed feedback about how the TB9 sync process works -- and I've continued to reflect on his recent feedback in this thread about a "complete" sync not being completely "up-to-date":

Harlan wrote:
When a sync completes, that does not mean that it is completely up to date. Each sync is a single two-way exchange of information. Sometimes it is not possible to get everything completely sync in that single exchange and in this case any remaining changes will be sent on the next subsequent sync.


In this content, I understand that (1) incremental changes need to be sent independently from each computer to the web client server before they can be transmitted and synced with other brain installations and (2) it takes a total of 3 syncs for all changes from 2 installations to be shared across the web server.

I also understand the little sync triangle will let me know (1) when I have local changes that need to be uploaded to the server and (2) when there are changes on the server that need to be to downloaded.

What is not clear to me, based on Harlan's feedback above, is whether:
all the local changes from one brain installation can be uploaded to the server at one time and
> all the changes from the server can be downloaded at the same time the local changes are being uploaded.

Is there any reason why this is NOT possible with way TB9 sync works?

I'm just trying to understand to what Harlan is referring when he said that "any remaining changes will be sent on the next subsequent sync".
-- Is this simply a reference to the 3rd sync that has to occur in order to complete a sync between 2 different installations?
Quote
mcaton
Metta,

Under normal circumstances, all changes from the client and the server will be exchanged in one successful sync.

Thanks,
Matt
Quote
metta
Thanks for confirming, Matt. Always appreciate your helpful feedback and follow-up.
Quote

Newsletter Signup  Newsletter        Visit TheBrain Blog   Blog       Follow us on Twitter   Twitter       Like Us on Facebook   Facebook         Circle Us on Google+  Google         Watch Us on Youtube  YouTube       

TheBrain Mind Map & Mindmapping Software     Download TheBrain Mind Mapping Software