this way your the only one with access to it because your the only one with the key! the only downfall of idrive sync is NO easy support for Linux yet.Ĭlick to expand.I don't know what providers you know of, but a 250MB file size limit is not common, even with free accounts. idrivesync also lets you use your own private encryption key during sign up.
Not many cloud storage providers allow files over 250mb for free, Dropbox Offers 2GB, idrivesync offers 10GB for free without file size restrictions.
You can create your container right inside your Dropbox folder it will upload during creation which cuts time down because its uploading as its being created, When you Mount your TC container it is only mounted on your machine, your dropbox will not upload the modified encrypted content until it detects the change after you Close the Container and TC writes the modification timestamp, then only the modified contents you added will be uploaded, no need to reup your entire container just the modified parts upload on their own after you close your container. which would be basically null in this case anyways because your using cloud storage. This is why your date never uploads when you change the content in your Truecrypt container, it is not a security feature unless you dont want the container to tell when it was last accessed/modified.
"Preserve modification timestamp of file containers" I have a few different schemes that are recommended, depending on what exactly you're looking to do.Īn easy way is go to Truecrypt settings, uncheck What is the size of the overall dataset you're looking to back up? And what is the typical file size? And how quickly does the data set grow? Do you have constantly changing files and folders that you are looking to have easy access to, on the go? Or are you just looking for a secure way to backup important files to cloud storage in the (hopefully unlikely) event that your local hard drives fail? My question is, what exactly are you trying to do? There are really too many variables to offer a one-size-fits-all solution. But if you're trying to dynamically and constantly backup a entire folder structure that is always changing, then it's a bit more difficult. If you're simply looking to have offsite storage for files that won't change, then you shouldn't have a problem with TC volumes. The main thing is, what are your purposes, and what are you personally willing to put up with. The answer is (as with pretty much everything else): it depends. I understand completely where you're coming from, and I'm with you on the having to replace old volumes with larger ones.