
Vincent: But you know what the funniest thing about Europe is?
Jules: What?
Vincent: It’s the little differences. I mean, they got the same shit over there that we got here, but it’s just – it’s just there it’s a little different.
When I decided to switch from Mozy to Carbonite as my backup provider, I knew some things would be different, and I even tried my best to spot the differences and deal with them appropriately. So far I have not come accross anything which would make me regret my decision, but there are a few “rough edges” which are worth pointing out for anyone considering a similar move. Stay with me …
To backup all files doesn’t actually mean *all* files
In Mozy, when you added a particular folder to a backup set, all files and folders within were backed-up, no worries; Carbonite, on the other hand, handles this a bit differently: there are certain file types which are not backed-up by default, even though the folder where they are stored shows-up as “green” (backup current) in the status. Things like movie files (avi, wmv, mpeg) and executables (exe, com) for example will not be backed-up.
But not to worry, there’s an easy workaround: to add a given file type to the list of what is backed-up by default, say AVI files, you just right-click on any one such file and select the context menu entry “Carbonite” in explorer; you’ll see the grayed message “Files of this type are not backed up”; just select “Properties” and in the “Details” group, check the option for “Back up files of this type” (you could also just back up that one file, but that’s not likely to be what you want done).
The description of this process is available in the Carbonite FAQ, under the topic [Windows] Backing Up Files That Are Excluded By Default.
Also, there’s a handy list of folders and file types which the default configuration will not back up listed under the topic [Windows] File Types Excluded from Backup. In the interest of documentation, I’ll reproduce the list of file extensions here: (I don’t care much for the folders, as I manage my backup folders manually, instead of accepting the default settings)
|
.113;
|
.$$;
|
.$DB;
|
.ABF;
|
.ABK;
|
.AFM;
|
.ANI;
|
.ANN;
|
.BAC;
|
.BAK;
|
.BCK;
|
.BCM;
|
.BDB;
|
|
.BDF;
|
.BKF;
|
.BKP;
|
.BMK;
|
.BSC;
|
.CAB;
|
.CF1;
|
.CHM;
|
.CHQ;
|
.CHW;
|
.CNT;
|
.COM;
|
.CPL;
|
|
.FFL;
|
.CUR;
|
.DEV;
|
.DFONT;
|
.DLL;
|
.DMP;
|
.DRV;
|
.DRV;
|
.DVD;
|
.EOT;
|
.EVT;
|
.EXE;
|
.FFA;
|
|
.FFO;
|
.FFX;
|
.FNT;
|
.FON;
|
.FTG;
|
.FTS;
|
.FXP;
|
.GID;
|
.GRP;
|
.HLP;
|
.HXI;
|
.HXQ;
|
.HXR;
|
|
.HXS;
|
.ICO;
|
.IDB;
|
.IDX;
|
.ILK;
|
.IMG;
|
.INF;
|
.INI;
|
.INS;
|
.IPF;
|
.ISO;
|
.ISP;
|
.ITS;
|
|
.JAR;
|
.JSE;
|
.KBD;
|
.KEXT;
|
.KEY;
|
.LEX;
|
.LIB;
|
.LNK;
|
.LOG;
|
.LWFN;
|
.MSC;
|
.MSI;
|
.MSM;
|
|
.MSP;
|
.MST;
|
.NCB;
|
.NT;
|
.OBJ;
|
.OBS;
|
.OCX;
|
.OLD;
|
.OST;
|
.OTF;
|
.PCH;
|
.PF;
|
.PFA;
|
|
.PFB;
|
.PFM;
|
.PLIST;
|
.PNF;
|
.POL;
|
.PREF;
|
.PRF;
|
.PRG;
|
.PRN;
|
.PWL;
|
.RDB;
|
.REG;
|
.REG;
|
|
.RLL;
|
.ROX;
|
.SBR;
|
.SCF;
|
.SCR;
|
.SDB;
|
.SHB;
|
.SUIT;
|
.SWF;
|
.SWP;
|
.SYS;
|
.THEME;
|
.TMP;
|
|
.TMS;
|
.TTC;
|
.TTF;
|
.V2I;
|
.VBE;
|
.VGA;
|
.VGD;
|
.VHD;
|
.VMC;
|
.VMDK;
|
.VMSD;
|
.VMSN;
|
.VMX;
|
|
.VXD;
|
.WIN;
|
.WPK;
|
The downside to managing your own encryption keys
Every backup which leaves your machine and goes into storage “somewhere in the cloud” must only leave the premisses encrypted; both Mozy and Carbonite do this well. By default the key used to encrypt your backups will be managed by the service provider, so in the event that you need to restore data, all you have to do is login into the provider’s website and start the process. The downside being that in the event of a security breach at the provider, they have both your data as well as the key to decrypt it.
For the most paranoid among us the only acceptable option is to manage your own key. That means, there is no key stored at the service provider, and they have no way of decrypting your data, even if they wanted to, even if they were compelled by law enforcement. And the downside is that if you (the user) is sloppy in safekeeping your encryption key, you might one day discover that disaster had struck and you have no way to get back to your data.
With that caveat in mind, I’ll be quick to admit to being paranoid and managing my own keys. With Mozy that meant that when you restored data over the web, in bulk or one file at a time, you’d receive back encrypted files, and after downloading them you had to decrypt them using a utility supplied and your own personal encryption key. The trouble with carbonite is that it won’t allow you to download individual files or folders if your encryption key is not managed by the system. I’m contacting customer support regarding this issue and will post here any updates or workarounds.
Bandwidth throttling will bite you
Bandwidth doesn’t come cheap, and so everyone throttles it, that’s just the way it is; just because you’ve got a nice 10Mbps internet connection, don’t expect to be able to backup at anywhere near that speed. For a start, your home connection might be asynchronous, meaning you have different rates for download and upload – usually upload, which is what a domestic user does less, is a much lower speed than upload. For instance, a “normal” ADSL connection in this neck of woods is 3Mbps advertised, and if you read the fine print, it’s 3Mbps down, 1Mbps up, maximum.

That said, you won’t get the maximum upload speed for your connection either. Consider all the internet nodes between your house and the Carbonite servers and there’s lots of places for congestion to happen, and you’re bound to the slowest of the nodes. Now assuming that everything is OK in the network and there’s little congestion, you still have to content with all other Carbonite customers running backups at the same time, and that’s the throttling I’m interested here: a limitation on your maximum upload speed imposed by your backup provider.
The stated throttling policy by Carbonite is as follows:
- The first 35GB of data can achieve upload speeds of up to 2 mbps (megabits per second).
- Between 35GB – 200GB of data can have the upload speeds reach up to 512 kbps (kilobits per second).
- 200GB or more of data can be uploaded at up to 100 kbps (kilobits per second).
Mozy, on the other hand, apparently don’t throttle it’s backups, and I can attest as a user with a backup set in the order of just under 100GB that Mozy was much faster to upload the same set of data. This throttling is actually my biggest gripe with Carbonite thus far.