{"id":11746,"date":"2011-05-30T04:00:17","date_gmt":"2011-05-30T11:00:17","guid":{"rendered":"http:\/\/pindelski.org\/Photography\/?p=11746"},"modified":"2011-06-20T07:15:19","modified_gmt":"2011-06-20T14:15:19","slug":"crashplan-part-iv","status":"publish","type":"post","link":"https:\/\/pindelski.org\/Photography\/2011\/05\/30\/crashplan-part-iv\/","title":{"rendered":"CrashPlan – Part IV"},"content":{"rendered":"

Finally uploaded.<\/i><\/p>\n

After two weeks of uploading, some 170gB – comprising my user settings and Lightroom catalog – have been uploaded to CrashPlan’s servers. I first wrote about this cloud storage service here<\/a>.<\/p>\n

\"\"<\/p>\n

100%! Two weeks of uploading ….<\/i><\/center><\/p>\n

Hereafter, uploads will be limited to incremental changes as new photos are added to Lightroom.<\/p>\n

So how well does recovery work? Click on the ‘Restore’ icon and this is what you see (CrashPlan uses East coast time):<\/p>\n

\"\"<\/center><\/p>\n

Note that you can recover at any date – just like in Apple’s Time Machine.<\/p>\n

The first, unnamed, dropdown is the User’s directory, which CrashPlan uploads by default. The second, ‘HackPro HD’ contains only those directories elected when the upload commenced. In my case, that means my Lightroom catalog:<\/p>\n

\"\"<\/center><\/p>\n

Drill down and you get to the catalog of Pictures:<\/p>\n

\"\"<\/center><\/p>\n

One more step and you see the actual RAW, TIF or JPG files:<\/p>\n

\"\"<\/center><\/p>\n

Check the files to recover and you see this:<\/p>\n

\"\"<\/center><\/p>\n

I clicked on ‘Click here to download your restored files’ and the 12.5mB RAW file was deposited on the HackPro’s Desktop in 24 seconds, using my 10 mb\/s broadband connection. That’s 0.52 mBytes\/second compared to the theoretical maximum of 1.25 mB\/s (10 megabits equal 1.25 megabytes and the line is 10 megabits\/second). Not bad. The Desktop is a good destination as there’s no risk of overwriting your Lightroom catalog.<\/p>\n

A couple of clicks and the file is in Photoshop, ready for processing:<\/p>\n

\"\"<\/p>\n

File restored from CrashPlan’s cloud server. G1, kit lens @ 30mm, 1\/320, f\/5.6, ISO 100.<\/i><\/center><\/p>\n

You can also restore the sidecar file with all the processing data, to avoid having to reprocess the picture.<\/p>\n

Restored Zip files remain separately available for 24 hrs – the original RAW (or whatever) file remains untouched:<\/p>\n

\"\"<\/center><\/p>\n

The only anomaly encountered so far is the wildly erratic reporting of upload status. I asked for daily email updates and got them at inconsistent times. That’s troubling, as inconsistency is the last thing I want from a cloud backup service, but the files appear properly uploaded and easily restored:<\/p>\n

\"\"<\/p>\n

Erratic reporting from CrashPlan.<\/i><\/center><\/p>\n

A check of files in my HackPro Lightroom and the CrashPlan directories confirms a like file count.<\/p>\n

So, for $50 a year with currently unlimited data volumes, CrashPlan looks to be a useful supplementary backup plan. Just don’t make it your primary one. Are you about to trust all your pictures solely to a fragile ‘cloud’, where you have no independent verification of the adequacy of procedures or the financial solvency of the business?<\/p>\n

Finally, recalling my earlier mantra that the only valid backup plan is one which has the qualities of paranoia and mistrust at its core, I made a reminder in iCal to prompt me to do a test restore of a file monthly. That way I get some comfort that the cloud database is not corrupted. It takes seconds to do.<\/p>\n

\"\"<\/center><\/p>\n

Update June 13, 2011:<\/b><\/p>\n

With incremental upgrades to my Lightroom catalog on the HackPro work machine being conferred faultlessly, and automatically, in the CrashPlan cloud storage database, I have signed up for 3 years for a total of $119.99:<\/p>\n

\"\"<\/center><\/p>\n

In Part V<\/a> I look at backing up additional files and at how best to backup applications.<\/p>\n","protected":false},"excerpt":{"rendered":"

Finally uploaded. After two weeks of uploading, some 170gB – comprising my user settings and Lightroom catalog – have been uploaded to CrashPlan’s servers. I first wrote about this cloud storage service here. 100%! Two weeks of uploading …. Hereafter, uploads will be limited to incremental changes as new photos are added to Lightroom. So … Continue reading CrashPlan – Part IV<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-11746","post","type-post","status-publish","format-standard","hentry","category-sofware"],"_links":{"self":[{"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/posts\/11746","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/comments?post=11746"}],"version-history":[{"count":32,"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/posts\/11746\/revisions"}],"predecessor-version":[{"id":11767,"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/posts\/11746\/revisions\/11767"}],"wp:attachment":[{"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/media?parent=11746"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/categories?post=11746"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pindelski.org\/Photography\/wp-json\/wp\/v2\/tags?post=11746"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}