fyi: Crashplan having a sale currently: https://www.crashplan.com/bigsale/
How the Sale works -
On Friday, Nov. 23 at 6:00AM CST, CrashPlan 1-year plans will be FREE. Every two hours after that, the price will steadily increase until Monday Nov. 26, 2:00PM CST, when your purchase will be discounted 42%. The discount will remain at 42% until the sale ends, 11:59PM CST Monday.


Glacier sounds pretty cool if your backup storage needs are relatively small. Doing some rough calculations, Glacier would cost about $370/year for 3TB of data. iDrive is $375/year for up to 10TB of data (not counting the discount). Considering JavaJones' current usage and needs, plus the greatly discounted 2 years of service, I don't think Glacier would offer him any benefit over iDrive.

First off I get notifications for updates to the client but trying to use the built-in update function never works. It downloads to 100%, then just sits there and never applies an update. This may be a security setting issue on my end. It's a minor but consistent annoyance. Downloading the application from their server manually and then just reinstalling it seems to work fine to update though.
Last but not least if you're still interested in iDrive after my concerns expressed above, and if you don't need 10TB of space like I do, this deal might be more of interest (I haven't tested it to see if it's still live):
https://www.idrive.com/idrive/deals/pd/backupreview

The Continuous Data Protection feature allows IDrive to automatically recognize the changes to files present in your backup-set and back them up in real-time...What's odd is that this indicates the technology I'm talking about *does* exist in iDrive, it's just not used for the main backup. So why not just use this Continuous Data Protection *instead* of the main backup? Well, the big limitation is it does not consider or backup files larger than 500MB. As their FAQ indicates:
CDP is not a replacement for the traditional schedule backup feature but works along with the scheduled backup to provide timely protection for your data.
So clearly CrashPlan is doing something wrong, wrong, wrong.Java? :-)
I'm fairly certain there are more effective approaches, such as using the NTFS file table to look for changed files, doing active file system monitoring (performance considerations?)If I were to design a backup solution, I'd definitely use a combination of USN Journal scanning, if available, on program start-up, combined with filesystem notification events.
I *have* seen them fix one or two issues I had, for example with auto-update not working, so that's encouraging. And supposedly they're working on better change detection and stuff. So we'll see...
Using Amazon Glacier or Google Nearline is cost prohibitive, but they're getting there. I would love to see a service using Nearline with some deduplication and a lean client. I have nothing against Java per se, but CrashPlan clearly hasn't optimized their client for memory usage.Kinda impossible to do for Java. You need to reserve a heap that's large enough to handle your largest theoretical load, plus some extra for garbage collection bookkeeping. This can be grown dynamically, but I don't think the JVM ever shrinks the operating system allocated heap. Makes sense for server loads, isn't always a nice feature on client machines though.
Kinda impossible to do for Java. You need to reserve a heap that's large enough to handle your largest theoretical load, plus some extra for garbage collection bookkeeping. This can be grown dynamically, but I don't think the JVM ever shrinks the operating system allocated heap. Makes sense for server loads, isn't always a nice feature on client machines though.
Original address: https://www.donationcoder.com/forum/index.php?topic=26224.0