tag:blogger.com,1999:blog-6811336968619276420.post5901264481811760126..comments2024-01-15T23:42:40.807+10:00Comments on H. Mijail's Blog: CrashPlan limitationsHoracio Mijailhttp://www.blogger.com/profile/10941261506308268725noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6811336968619276420.post-29456764299643298122018-01-18T21:43:12.896+10:002018-01-18T21:43:12.896+10:00Also related with the different states in which Cr...Also related with the different states in which CrashPlan can be: in some of those states, you just can't restore files! You are recommended to use a friend's computer, or at the very least play with the computer backup ID during the restore and then readopt the "old" backup! [1]<br /><br />This is crazy, and makes me gain new appreciation for how transparent Apple has managed Horacio Mijailhttps://www.blogger.com/profile/10941261506308268725noreply@blogger.comtag:blogger.com,1999:blog-6811336968619276420.post-36575308147118098532018-01-18T20:43:35.996+10:002018-01-18T20:43:35.996+10:00Another problem with CrashPlan: even though it has...Another problem with CrashPlan: even though it has a promising feature to stop backups while on battery power, it is full of cop outs. Turns out that CrashPlan has a number of states, and while it might not technically be *backing up*, it might still be synchronizing data with the servers or "maintaining backup files" or whatever while on battery power, and using up to 40% of CPU - withHoracio Mijailhttps://www.blogger.com/profile/10941261506308268725noreply@blogger.com