![]() Your points highlighting the differences (one file per database item in the older format vs. However, I recently switched to the OPVault format because there was no longer a choice when creating a new folder sync file. ![]() To answer your question, I had been using the Agile Keychain format, which seemed to work. I'm now engaged in two parallel threads about this topic (partly my fault), so I'll leave it up to you or one of your colleagues to decide whether to merge them. I can understand that a pen drive may not feel like an acceptable course of action but if ChronoSync is throwing away an entire modified band in one OPVault to use the band in the other there is the very real potential for data loss. As the pen drive is removable we get proper notifications from OS X when it is mounted or dismounted but more importantly, they're all syncing to the same container and there is no multiple differing copies to worry about. You go from a third party sync solution trying to merge different copies of the sync container to there only being one sync container, the one on the pen drive. This is why if you want to use Folder Sync we do strongly suggest use of a pen/flash drive that you pass between Macs. Now imagine ChronoSync is choosing one altered band over another - it could be potentially deleting all sorts of what seem to be unrelated data but still data that is stored in the same band. It means multiple items are held in each band and edits to two very different items can both be to the same band. This issue is amplified if you use the OPVault container because while the Agile Keychain format specified a single file per item in your vault, the OPVault container uses bands, just like OS X does for disk images. This does have the potential to result in data loss when using ChronoSync in contrast to Dropbox. To the best of my knowledge ChronoSync does not offer the ability to do anything like this and instead you have to choose one or the other. In these instances we read the contents of both the file and the conflicted copy and store the differences in a new custom section of the item in question and the section is titled Conflicts. When Dropbox finds a file has been altered in more than one location it creates conflict files and 1Password is aware of these. 1Password reads and writes to a folder and the actual syncing is handled by Dropbox. Hi and would be very curious to know whether you use the older Agile Keychain format or the newer OPVault when syncing.Īt the heart of it, Dropbox sync is the same as Folder Sync on a Mac. Has anybody seen something like this before? I am using the latest non-beta software. I can even see the errors from the last modification time. This is a simple scenario for chronosync but something gets messed up in the process. When I sync, the new entries get copied to the other vault but the existing password is not updated. And I create other logins/password in that vault, too. And say I update the password in one of them. Say I have a login already in both mac's vault. Now the problem seems to be more serious than this. This would cause information loss, right? So, first please clarify how folder sync functions in these two cases. ![]() In that case chronosync (or any other sync software) would obviously register a conflict and I would need to manually pick one as the source. In other words, can the folder sync feature understand what has changed in /Users/uname/vaultsync/myvault and apply them to /Users/uname/Library/Application Support/1Password 4/Data/myvault? Now, I was never sure whether this would work 100% reliably when I modified the vault on both macs since the last sync. Unless I modify the vault on both macs since the last sync, this is supposed to work w/o any information loss, right? Then I use chronosync to sync the vault files in /Users/uname/vaultsync on both macs. ![]() Users/uname/Library/Application Support/1Password 4/Dataīoth macs also sync their vault to another folder (folder sync), say:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |