Messages

Ok, I understand now that the overhead is intrinsic and is no "problem" of Espionage. Thanks for the clarification.

The past days I tested ZumoDrive, SugarSync and Dropbox. It seems that only Dropbox is working properly with Espionage. Here is the test "scenario": I created a test folder with a test file ("Hello world"), encrypted  and uploaded it to the three services. I then unlocked the folder and changed the text file ("Hello World" --> "Hello Planet"). Afterwards I tested how long each of the three services needed to upload the changes from the Espionage's built-in backup feature. Note: I have a low bandwith, everything takes quite a while here...

Dropbox only needed a minute or so.
Zumodrive and Sugarsync needed over an hour...

My conclusion: There are cloud storage solutions which can't' just upload only the changed parts of a file or folder. They always upload everything all over again, which renders them unusable with Espionage. The only service I found which worked nicely was Dropbox. They also explain this behavior in their help section (https://www.dropbox.com/help/8). I guess Dropbox suits my requirements the most.

Christian

I've done some testing and experimenting. Besides Jungledisk I tried other cloud storage solutions, such as Zumodrive, because Jungledsik still gave me troubles. Zumodrive is somewhat similiar to Dropbox, but has the advantage of selecting the folders you want to backup to the cloud. I then pointed the built-in backup feature of Espionage to the mapped Zumodrive - very convenient. When the automatic backup is initiated, the data is cached by the Zumodrive software and the data is then uploaded to the cloud. I noticed the following. If I encrypt a folder with 1,2MB content. The data uploaded to the cloud is approx. 109MB. How can this be, with a folder being only 1,2MB large?
If the backup has completed and I unlock the folder, change nothing and lock it again, there is again approx. 100MB transferred.
Could you please help me with this?

Christian

Hi Greg,

thank you for your assistance. I tried the tipps you suggested (entering the piece of code in terminal), yet the problem persists.
It might have something to do with the way Jungledisk treats uploads to amazon S3 (Jungledisk is a amazon S3 client). It seems to be unable to upload only those parts wich have been changed.... However, you can modify the jungledisk subscription to improve the upload mechanism (uploading only the parts of a file which have changed). I modified my subscription and am now testing how it works. I will tell you how it turns out.

Cheers,
Christian

Hello,

I've recently purchased Espionage and I am quite happy with the program. Yet, I have some troubles (I think) with the built-in backup functionality. Everytime a backup is performed there is way more traffic than expected. Info: I am backing up to a Jungledisk share, which is accessed just like a mapped network drive.
Problem description:
I unlock a folder and change a file, size 0,5MB. Upon locking the folder, the backup procedure is triggered and the changes are sent to the mapped jungledisk drive. However, instead of 0,5MB or 8MB (the sparsebundle size) the Jungledisk monitor shows 117MB(!) being transferred.

Could you please help me resolve this issue?

Christian