We had a machine with a very large backup set (~3TB) with some large DV files (~4GB). For a while our backups were running fine but recently whenever we tried launching the Crashplan GUI it would run for a little bit, hang and then finally crash. Nothing showed up in the Windows event log (boo!) but Crashplan does have its own logging mechanism which on our machine was in C:\ProgramData\CrashPlan\log.
The service.log.0 file was giving us:
java.lang.UnsatisfiedLinkError: Unable to load library 'cpnative64': The specified module could not be found.
Unfortunately there were zero search results for that. Looking a little deeper in that log we found:
...ERROR QPub-BackupMgr backup42.service.backup.BackupController] OutOfMemoryError occurred...RESTARTING! ...snip... oomStack=java.lang.OutOfMemoryError: Java heap space
Searching for that error lead me to this post which explains how to increase the amount of memory that Java is able to use. On our machine the file to edit was c:\Program Files\CrashPlan\CrashPlanService.ini. In the Virtual Machine Parameters we tried increasing the parameter -Xmx from 512 to 2048 and although that delayed the crash it still happened. Our machine has 16GB of RAM so we kicked it up to 4096 and (crossing my fingers right now) it seems to be running just fine now.
(This is Crashplan 3.2.1)
Thanks for posting this Chris, I’m experiencing the very same issues on 1 of my 2 servers. Both are 2k8 x64 w/ 2gb ram. The one with problems is trying to backup a terrabyte worth of photos. I’ve yet to increase the RAM in these VM’s but after applying your -xmx tweak straight to 4096 CP Pro seems to be working alright now.
I know I’m hitting the swap file now, but at least it’s working again. Thank you so much for taking the time to post your fix! Aloha, Rick