You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Block-level sync for VeraCrypt not working post 83.4.152 update
Greetings all,
After DB auto-updated to 83.4.152, I noticed that the block-level syncing doesn't seem to be detecting changes anymore for my VeraCrypt container.
Before the update, everytime I di...
Hi all, we've brought this to our team and wanted to follow up.
While we've presented a workaround: either by turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension, we want to be transparent about our current priorities and unfortunately, this means that we won't be able to delve deeply into this in the near future.
We're still tracking these reports, and will make sure to inform you right away of any changes.
Thanks for understanding .
I am having the same problem. I have a Truecrypt and over it has stopped syncing and the date doesnt change on the encrypted folder and online the version history doesnt record any new version unless I change the name of the file.
I will probably wait a couple of weeks but if not fixed change to another provider
GH
I am also having the same problem. I've been using Truecrypt and Dropbox for years (and only on 1 PC), and Dropbox used to upload my changes automatically when I dismounted the Truecrypt volume at the end of a day's work.
But, for the last few days, it has either failed to recognise that there have been any changes, or, if it does recognise changes, it renames the up-to-date version on my hard drive as a conflicted version, then starts to download the old version to my hard drive, whilst uploading the "conflicted" version. And as both files are quite large, this takes several hours, and the upload speed slows right down to somewhere between 1 KB/sec and 100 KB/sec.
Hi JAS37,
Might be more easy, as an workaround, the content get be synced, not the container. :thinking:
I can confirm, I have also reported it, as I personally see this critical.
Здравко schrieb:
Hi JAS37,
Might be more easy, as an workaround, the content get be synced, not the container. :thinking:
This is not even something like a workaround. If you have sensitive data in a container, you don't want to expose that directly to the cloud or whever those files are located. That is why people use containers.
Здравко schrieb:
Hi FatCharlie,
Try using some earlier version you know work. :wink:
Hope this helps to some extent.
I did try version 82.3.133 with block-level syncing (the "Preserve" opiton of veracrypt) without success.
GH74 schrieb:...On Truecrypt go to Settings\Preferences deselect "Preserve modification timestamp of file containers" and do this on all your machines. Now the whole folder will sync and the time stamp of the folder will update. It takes much longer however as it doesnt appear to be using the block level sync...
This of course is something like a workaround, but it is against the concept of block-level-syncing.
What is really frustrating is the fact, that it took me days, not to say weeks, until I discovered that. So all data in the meantime gone. This must not happen to a solution like dropbox!
Jane Fiona : Please give us a statement on: Is it a bug or was the removal of the block-level-sync intended and what will be the next steps?
as I write in my intial post, I believe 81 was last working good, not 82.
when I install 81 it indeed starts syncing again the modified containers, however:for a minute only, until the *#*! autupdater strikes again while it is syncing, updates to 84, which then starts producing conflicting copies, grrrrrrrr
This was NOT solved! All that does is cause Dropbox to sync the entire encrypted volume. It STILL is NOT doing a block-level sync.
R.I.P.
Accepting a loss is truly difficult, but is just another test (understand - like as restrictions, prices and so on). Today we remember not only the who died (understand the usable feature), but also, who led an honorable life (understand efficient syncing). God (understand Dropbox) only gives us trials lesser than our strength and assistance (understand workarounds comming from community mostly) beyond our eyes can see.
You are in our hearts and prayers (understand - hope something will change - resurrection in some future release).
I have contacted support twice but they wont look into it because we are using a third party program "Truecrupt" which in their security page suggest you can use. Given they are not going to look into it there wont be a solution and so we wont be able to use dropbox with encrypted folders.
Thanks GH74. It looks as if I will just have to find another cloud backup service!
I have found a solution that works for Truecrypt and prob Veracrypt. On Truecrypt go to Settings\Preferences deselect "Preserve modification timestamp of file containers" and do this on all your machines. Now the whole folder will sync and the time stamp of the folder will update. It takes much longer however as it doesnt appear to be using the block level sync.
Hope it works for you as well.
