WeeGee

Members
 View Profile  See their activity

  • Posts

    8

  • Joined

  • Last visited

 Content Type 

Posts posted by WeeGee

  4. Newer Files Overwritten By Older Files - Btsync 1.3.94

    in Sync Troubleshooting

    Posted

    @WeeGee

    It is stable, just some events come from a peer we don't have name for, only the ID. It is not very productive to put 16 bytes hexadecimal peer ID into history.

     

    But I see both (correct name and Remote peer), with only one other peer connected, and the messages clearly refer to the same peer, the messages have only minutes between them... 

    BTW: an ID would at least make it possible to differentiate between several "unnamed" peers (when there are more than one)

     

     

    Under which OS do you do this operation?

     

    OS X 10.9.4.

  6. Newer Files Overwritten By Older Files - Btsync 1.3.94

    in Sync Troubleshooting

    Posted

    @WeeGee

    "Remote peer" means Sync does not know who did it. When Sync knows - it replaces "Remote peer" with peer's name. There was a bug when RO peer "reflected" the removal command back to RW peer which caused file deletion (see my post above)

     

    I just looked at the history entries:

    Some lines say Remote peer, some say the correct computer name, all refering to the same computer... seems like the name resolution not very stable..

     

     

    I also found a "Renamed file" mesage, where the old and new name are reversed. Are there any other wrong messages in the current versions??

     

    Sharing a link or key via clipboard also doesn't work, nothing is copied to clipboard. Sharing via eMail gives me a working link.

  7. Newer Files Overwritten By Older Files - Btsync 1.3.94

    in Sync Troubleshooting

    Posted

    @RomanZ:

     

    All the files are signed with digital signature before they are sent. Private key is owned by RW peers, while RO own only public key. So, RO peers may only receive files - and none of RW peers will accept modified files from RO as they are not signed.

    I checked the keys, and the master, on which the lightroom catalog was edited, has both keys (naturally), and the slave (Synology Diskstation) has only the RO key.

     

    - .!sync files are ignored and never synced as they are service BTSync files.

    Well, after the disaster I found only the .!sync files, and nothing else.

     

    So I suspect that you have yet another RW peer, that decided to sync your Lightroom database. Are you confident that you have only 2 peers?

    Yes, 100% sure, there are only these two computers which have keys to this folder: one Mac (master) and one Synology (RO)

     

    Also, did you check that deleted database was moved to .SyncArchive folder?

    sure, but it wasn't there.

     

    BTW: Lightroom saves the database several times while it's open, similar to Excel.

     

    Here is the current history from the Mac, running the current BT Sync 1.4:

    2 hours ago

    Finished syncing with Schroeder

    2 hours ago

    Finished syncing with Schroeder

    2 hours ago

    Finished syncing with Schroeder

    2 hours ago

    Finished syncing with Schroeder

    2 hours ago

    Remote peer removed file Lightroom5.lrcat-journal

    2 hours ago

    Remote peer added file Lightroom5.lrcat

    2 hours ago

    Finished syncing with SALLY

    2 hours ago

    Added file Lightroom5.lrcat-journal

     

    Schroeder is the Synology backup, which has only the RO key.

    SALLY is a third PC, but it syncs only other folders, not the Lightroom folder.

     

    What do the lines beginning with "Remote peer " mean exactly? The remote peer is Schroeder, having just the RO key, as I understand it?

  8. Newer Files Overwritten By Older Files - Btsync 1.3.94

    in Sync Troubleshooting

    Posted

    I just had a similar problem which cost me many many hours of work to fix:

     

    Machine A) MacBook with BT Sync 1.3.94. Here I worked with Lightroom, modifying my 5 GB Lightroom database.

     

    Machine B) Synology NAS with BT Sync 1.3.94. Here I used the readonly key to make backups from machine A.

     

    This config was running for a while without problems.

     

    Now the sync was interrupted (A was in standby over night) and left a .!sync on B instead of the original lightroom catalog.

    When the sync resumed (probably after a shut down and reboot of B over night), the unimaginable happened: the new lightroom catalog file on A was deleted (ignoring the read only key!) and replaced with a .!sync file, which of course was incomplete and corrupt.

     

    Unfortunately my second backup (Crashplan) didn't had enough time to backup the new lightroom catalog before BT Sync deleted it. So all my edits were gone.....