Cloud Backup Review, IDrive vs Cloudberry

My desktop running Windows Vista Ultimate is already backed up thoroughly by a command-line script that I start every night when I go to sleep.  The script shuts down certain processes (e.g. FTP server, open TrueCrypt volumes, KeePass password vault) and copies all important files to other local hard disks.  

I also need a cloud backup, though, in case of a disaster like a fire, flood, theft, vandalism, sinkhole, asteroid, apocalypse, whatever, because all of my hard disks are in the same building.  A close friend did have a fire and lost everything. What the fire doesn't get, the filthy, soaking, ash-filled water does.  In my view everyone needs a cloud backup these days, and maybe it's the other local disks that are unnecessarily redundant.  I have 62,000 files to upload, totaling 7+ GB, including a 3GB TrueCrypt volume file.

Because I already have a time-tested command line backup script, I want my cloud backup to fit in and be part of it. At the least, the script should be able to start the cloud backup from the command line, know when it's done, and preferably log any errors that occur.  Then, when the cloud backup is done, the script can perhaps do other cleanup tasks and shut down the computer, or put it to sleep, or get going on other things that it needs to do.

At least two cloud backup offerings seem to have a sufficiently robust command-line interface and with "chunk" backup capabilities (more later): IDrive and CloudBerry.

IDrive is a complete backup solution, offering an installed application program, a web-based interface, a command-line interface, and storage.  Backups are physically kept on IDrive's own web servers.  The Basic Plan is FREE, with 5 GB file storage space and another 5 GB of "sync" space (files kept automatically in sync.).  You can also get "credits" for referring IDrive to others.  


I did that and used the free plan for my 7 GB for a whole year, before something failed and I needed help.  Since then I have upgraded to IDrive Personal, with 1000 GB of storage, which cost me $39.95 for the first year.  That's not expensive, and it's my impression that cloud backup prices are going down, so I doubt that cost will go up much.

Features important to me:

• Incremental backup is standard, of course.  Only new or updated files are sent to the cloud.
• "Chunk" backup for large files allows backup of only the parts of the file that have changed.  Automatic in IDrive.
• Command line interface.
• Data transmission and file storage are both encrypted.

Concerns:

• The IDrive Application program failed this month, and I was unable to get it going again without help.  The online chat support did the trick, but the technician went so fast that I was unable to see what s/he did.  I believe that s/he changed permissions in c:\Program Files (x86)\IDriveWindows and c:\ProgramData\IDrive, then did something with the VSS Service.  I asked the tech what s/he did, and got an answer like "fixed your computer," for which s/he gets a "D" for customer communication.  My concern is that it may fail again after some Microsoft update.
• The command line interface utility that comes with the newest IDrive download doesn't work on Windows.  Log in fails.  I use an older one that does work.
• For file encryption, you get a choice of a default key or a private key.  A year ago I chose the default, but suddenly this month the program demanded my private key.  Since I didn't have one, my data was lost and I had to upload the whole 7 GB again.  Now I do have a private key, but will it always work?

Validation:  After the most-recent backup I downloaded the 3GB Truecrypt container file and compared it bit-by-bit with the original here, using the comp utility.  There were no differences.  Further, I was able to open that downloaded file with TrueCrypt, highly unlikely if the file was corrupted at all.

CloudBerry is a front end application program for use with any number of cloud storage space vendors.  Its most robust implementation, though, is with Amazon S3 storage, and that is how I am using it because I need some features only available with Amazon S3.  For desktop (or laptop) use, there is a Freeware version called CloudBerry Explorer which does have some command line functionality, but I don't know how much, and I don't know if it handles "chunks."

I am have just purchased CloudBerry Backup (for Windows Desktop), a "Pro" version, for $29.99 plus $6.00 for an annual update service.  I'm happy to pay that. The Amazon S3 storage cost is trivial for my 7 GB:  The first 5 GB is free for 12 months, and prices thereafter are 3 cents per GB per month, at most. That will be $0.21 per month, or less than $3.00 per year. There are also transaction fees (for GET and PUT requests).  In this first month my Amazon S3 bill is so far $0.34 (34 cents), most of which is transaction fees for the initial upload of files.  I'll be happy to pay the Amazon costs too.

Features important to me:

• Incremental backup is standard, as with IDrive.  Only new or updated files are sent to the cloud unless a full backup is specifically ordered.
• "Chunk" backup of huge files is available with Amazon S3, and it is possible to configure the size of the chunks.
• Command line interface.
• Data transmission and file storage can both be encrypted.

Concerns:

• Amazon S3 is complicated, and you have to sign up for that separately.  I recommend sticking with as many defaults as possible.  I tried Google Cloud too, and it is simpler, but fewer features are available.
• The CloudBerry command line interface CBB.exe has many, many commands, a confusing array in fact.  Further, when starting a backup with a pre-existing backup plan, CBB simply starts another program, CBBackupPlan, and then quits, so the batch script can only know when the actual backup is done by looping, waiting for CBBackupPlan to disappear.  I'll be happy to supply that code or the whole script if anyone wants it.  It's all in CMD command line language.
• When performing a backup, the progress reports on the screen are mostly nonsensical.  It pulls up a list of 1000 files are a time, and sort of tells you how it's doing with that 1000. The Overall Progress bar shows about 33% most of the time, for some reason.  The backup works, so it doesn't really matter, and it does show a count of files uploaded, so if you know how many there are, you can figure progress yourself. 

Validation:  I have several times downloaded the 3GB Truecrypt file and compared it with the original from my computer. There were no differences.  Further, I was able to open that downloaded file with TrueCrypt, highly unlikely if the file was corrupted at all.

Some speed comparisons:

First, I am using a DSL connection to the internet, with 26Mbps download and about 0.9Mbps upload.  

• For both CloudBerry and IDrive, the upload time for my full 7GB is almost a day. I hope not to do a full backup very often!
• I have one 3GB encrypted file which downloads in 21 minutes with CloudBerry and 71 minutes with IDrive. Big difference.
• Smaller files download in no time, of course, and both providers make file selection and destination selection easy.
• Daily incremental backups take about 9 minutes with CloudBerry and 21 minutes with IDrive. Also a big difference, but I'm asleep anyway.

A SERIOUS CAUTION ABOUT CLOUD BACKUP:  If you end up needing it, you will be required to supply passwords.  In the case of Cloudberry, for example, you may need a password to access the CloudBerry program on a new computer, and if you use Amazon S3 services for storage, CloudBerry will ask you for a lot of information.  You will need your Access Key ID (long), your Secret Access Key (longer yet), the Encryption Password, and possibly the name of your Amazon S3 Bucket.  

For any other storage provider you will need similar information.  For IDrive you need at least the IDrive Password, and also the Private Encryption Key if you have chosen your own.

Obviously, it's no good backing that stuff up on the cloud with everything else!  It's inaccessible.  These passwords and keys will not change often, and you should have them offsite, far away from your computers.  I keep mine on a gold archival DVD in a safe deposit box.  A thumb drive might be more convenient in the future, but there are folks who believe that thumb drives are not a good archival medium.  My next computer will have a Blu-Ray (and DVD/CD) drive anyway. But I might keep a thumb drive in the safe box too, as backup.  :-)

Just sayin'

Truecrypt Forks

January 25, 2015:

As everyone knows, the anonymous creators of Truecrypt have declared it unsupported and hinted that it might be defective. While no one believes that Truecrypt has a security hole (see Gibson for example), and an initial audit did not find one, everyone wants to find a supported substitute.

I use Truecrypt encrypted container files to encrypt sensitive data on my Windows systems.  A container is a file which can be mounted as if it were a separate unencrypted volume.   Truecrypt can also encrypt entire disk volumes, though I do not use that mode, because of the complication and because containers are so easily backed up with full encryption to multiple destinations including the Cloud, Blu-Ray discs, hard discs, and thumb drives.

Requirements:

• To reduce the likelihood of a hole or a back door, the software must be open source.  This rules out all commercial encryption software.
• It must support some kind of portable encrypted containers.
• It should have a credible support team.

BitLocker is not a candidate because it is not open source and does not conveniently produce encrypted containers.

In my search for a Truecrypt substitute, here is what I found today. Things are moving fast, so this may not hold true for long:

https://ciphershed.org/	US, UK, Germany, Asia	Available as pre-alpha release
https://truecrypt.ch/	Switzerland	Downloads Truecrypt 7.1a
https://veracrypt.codeplex.com/	France	Rev 1.0f-1 downloaded and working

CipherShed is currently in a pre-alpha release only, apparently using some Truecrypt code and some new code. They caution against using it in production. Purportedly it will eventually all be new code, and with a team to support it. Currently I'll stick with Truecrypt 7.1a until (1) a problem is discovered in it, or (2) CipherShed or some other supported program is available.

Truecrypt.ch (also called TCnext) seems to be two Swiss guys who want to fork Truecrypt but, for now, are simply offering Truecrypt 7.1a, the final good release, on a download site. I suspect they are watching CipherShed and may eventually support that.

Veracrypt is the only fork currently available as an official release, and is a modest modification of the original Truecrypt open-source code. Apparently it is mostly written and supported by one Frenchman, Idrassi, and long-term support may be dependent on him, though there is a lively discussion board.

I have installed it, to discover that opening a container takes a long time, but he defends that as necessary to defeat a brute force attack.  In that respect, he believes that Veracrypt is quite superior to Truecrypt.  That judgment is above my pay grade.  Otherwise it walks and talks just like Truecrypt.  I have not tried any command-line arguments yet - I use those a lot in Truecrypt.

The delay on opening is dependent on a particular iteration count, and there is discussion about allowing the user to trade off password length versus iteration count, so that a longer password could result in a shorter opening time.

Veracrypt containers are not compatible with Truecrypt containers, but Veracrypt does have a Truecrypt mode.  I tried that and it did successfully open a Truecrypt container. I didn't try modifying the files in that container.

I recommend tuning in to those sites from time to time, to keep abreast of their progress.  I may or may not blog about it again.