![]() If Explorer is not used, the updated file does not sync to computer 2 for a time ranging from tens of minutes to never. #Box sync folder change manual#Both odrive’s interface and looking at the cloud storage directly via the provider web interface show the updated file.ģ: Computer 2 sees the change only by manually browsing to the local synced folder in Windows Explorer or in some cases after a manual odrive refresh is issued. We’ve seen this problem occur when all odrive storage is on local disks for both computers 1 and 2.ġ: Computer 1 changes a file in a local, encrypted odrive folder.Ģ: Changes are synced by odrive within a small (<3 sec) time to the cloud provider. That’s a killer business feature of odrive: not only does odrive allow businesses to use any storage provider without installing multiple interface tools, but it supports zero knowledge The flow is largely as you outline. With a fast connection, syncs rarely take more than 30 Indeed we are using encryption on all affected shares. None of the provider’s own apps from Box, Google, Amazon, or Dropbox suffer from this problem. In this case, a manual right click-sync command in the folder in question is required before odrive actually syncs,įor now, we’ve given up on odrive for work purposes where maintaining timely synchronization is a requirement. At the upper end, we’ve gone for over a week without odrive grabbing the modified remote file. At the lower end of the range, it takes hours to a day for odrive to pick up a single modified file remote in a small (<15 total files/folders) share. Browsing to the specific local shared folder in Windows Explorer is usually enough to trigger an odrive sync but this is not an acceptable option for production work.Ī computer with a large number of files (100K - 100M+) synced via odrive is another matter entirely. #Box sync folder change Pc#A PC with only a few odrive managed shares usually but not always syncs within 10 minutes without needing to manually navigate to the odrive folder. Even with the latest (Win v5354) client, there are significant delays in syncing files. This issue has become a showstopper for us. Default would use the existing odrive priority system. Low priority folders would only sync if no other upload/downloads were in process. Changes to a high priority folder would take the next available sync slot. If odrive is running on a server containing both types of storage buckets with active uploads in process from each, the files in the small bucket are often delayed in uploading for long times while other folders are processed.Ī useful option for this type of situation would be the ability to assign variable sync priorities to each odrive folder. The data are updated more frequently, usually multiple times an hour. Other shares are far smaller and contain “hot” data that need to be accessed by multiple users frequently. These contain files that we are migrating from local storage to the cloud and are - obviously - not all needed at any one time.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |