I’m an avid user of Time Machine to keep all of my media (most importantly, digital pictures dating back 15 years, and scanned images dating back nearly 20 years) backed up and safe, but a few months ago I started to consider the possible issues of having a backup sitting right next to the source.
In a situation of hardware failure on our iMac, the Time Machine backup is indispensable - simply fix the hard drive, and restore.
However, in a situation of double-hardware failure (unlikely, but possible), corruption (again, unlikely, but possible), or (hopefully never) catastrophic loss of our household contents, a local-based backup is going to prove rather useless. I needed an off-site backup solution to complement the local backups. Risking nearly two decades of memories simply calls for more than a lackadaisical approach to backing up.
My current webhost provides me with an unbelievable amount of disk space and the logical solution was to simply backup to this otherwise underutilized space, but simply compressing everything up into a huge archive and FTP’ing the files to the server seemed like a pain in the ass, and since it wasn’t easily automated, it was prone to being forgotten and as the months pass by could still result in file loss.
Enter “Twin”, by App4Mac. It seemed perfect, and in testing the feature-limited free version, it also seemed to actually work. It was straightforward to setup, was highly automated, and was able to utilize my wasted server space as an off-site backup destination. It was exactly what I wanted.
I was a little put off by the nearly $80 price tag, but I tweeted the developer and was sent back a “20% off” discount code which took a bit of the sting away from the purchase, so I took the dive.
The problem is that although it seemed to handle the small amount of files in the demo version, once I was registered and I set Twin loose with my 60 gig iPhoto library, things started going horribly wrong. The first failure was a result of me pausing the backup (using the server applications pause feature) since I needed the bandwidth for something else, except when I went to continue the backup the server crashed. 30 Gigs of upload wasted.
The second failure happened after about 40 gigs of the backup had completed. Starting from scratch.
The third failure happened after about 50 gigs of the backup had completed. Once again, starting from scratch.
You see, aside from the fact that the program doesn’t seem to be able to reliably handle large backups (as is evident from the crashes), it also can’t recover gracefully from said crashes - if a backup is not completed to 100% (a process that can take a very long time with a slow DSL upstream connection handling 60 gigs of upstream content), the program simply orphans everything that was backed up to the point of the failure and wants to start all over again when you restart.
Ridiculous you might say, but after discussing the problem with the developer, confirmed. Apparently no interim index of check files are written during the backup, and if it fails to complete for any reason whatsoever, you loose everything. Checking my server I can confirm that my last backup attempt successfully transferred just over 50 gigs (spanning the period of numerous days worth of saturated upstream transfer) and the files are there, but there is absolutely no way to re-associate those files to Twin and make it continue where it left off. Even if I attempted to manually handle the files that it did manage to backup it would prove infuriating since Twin aggravates files into batches, ZIP’s them, splits then as required, and (I understand) renames the source files to fit it’s own backup schema.
There is a feature to “recover an orphaned backup”, however again, it only works if the backup in question was 100% completed (at least once) to begin with, and then the Server app somehow lost it’s configuration of such.
So, after wasting over 120 gigs of bandwidth, I’ve given up. The developer did last respond saying a future version will address this issue, but when I inquired as to the anticipated release date of the new version, I received no response. I’m considering asking for a refund and looking for an alternative backup solution that does what I need, but I can’t seem to find anything else that handles things quite the same way Twin does - this is of course why I bought it to begin with.
The only good part of the story is that I have an ISP that offers me a generous 250gb/Month allowance so these failures aren’t going to cost me an arm and a leg in overage charges, but I still can’t help but feel a bit ripped off.