CrashPlan headup: > 1TB of backup data

[haysclark]

This is not an issue with the CrashPlan container; however, I found this issue difficult to track down so I thought I would share my issue and my solution.

Simply, be aware that if you are backing up over 1million files or 1TB of data you might find CrashPlan crashing abruptly. If your CrashPlan account is setup with "Backup to run: Always" you might find CrashPlan endlessly restarting every 2 minutes or so. Unfortunately, the stderr/stdout logs are not much help because they are misleading, and the 'docker logs' seem to only collect noVNC information.

So, IF you are close or over 1TB or data check out this article.
https://support.code42.com/CrashPlan/4/Troubleshooting/Adjusting_CrashPlan_Settings_For_Memory_Usage_With_Large_Backups

To fix this issue by increasing your Java memory size, simply edit the /config/bin/run.conf file on your Docker host to something like this:

SRV_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx3072m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false"
GUI_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanDesktop -DappBaseName=CrashPlan -Xms20m -Xmx3072m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false"

It looks like only GUI_JAVA_OPTS is utilized by the current container, but I updated both options just to be sure. The solution above will only have you covered until you hit 3TB. Just read the article for alternative solutions or keep feeding JAVA more memory.

Hope that helps someone. 😄

[mnestor]

Thank you! I couldn't figure out what was going on.

So I have 8.5TB of data but only within about 200k files. Is 3GB going to be enough? Not sure I have enough memory to give it more. I'll report back in 3 months when it might be finished 😄