CrashPlan is brilliant. Don’t let me tell you though. Bing! it and decide. Anyway you will find it you have to back up a large number of files, say in the region of 200,000 then you will need some more memory assigned to the Java Virtual Machine that runs CrashPlan. I am talking about windows here and this is the info I got back from support. You may find this useful if after a while CrashPlan seems to bomb out or keep on preserving with something and not really getting anywhere, i.e. constant file analysis or so on.
Here is the info:
Running Notepad or any other text-editor as an Admin, edit the CrashPlan engine’s CrashPlanService.ini file to allow it to use more java memory:
- Stop the backup engine: http://support.crashplan.com/doku.php/how_to/stop_and_start_engine
- Locate the Notepad program, right-click and Launch as Administrator
- Go to File > Open, and navigate to C:\Program Files\CrashPlan\CrashPlanService.ini
- Find the following line in the file: -Xmx512m
- Edit to something larger such as 640, 768, 896, or 1024. E.g.: -Xmx1024m
- Start the backup engine.
This sets the maximum amount of memory that CrashPlan can use. CrashPlan will not use that much until it needs it. I would recommend starting out setting it to 768, and go higher only if you continue experiencing problems. You can set it as high as 2048 on 32-bit systems, or even higher on 64-bit systems.