Always Remember: With Gusto Comes Data Loss.

Proper CrashPlan Memory Allocation

Below are the instructions for allocating additional memory for CrashPlan Clients. This becomes necessary as the client is expected to backup larger datasets. This holds true for all versions of the client (Plus, PRO, PROe). Please reference the chart below for the values you should be setting.

+--------------------------------+
|  BACKUP SIZE  |  RAM REQUIRED  |
|---------------|----------------|
|    <=500 GB   |      512 MB    |
|---------------|----------------|
|   .5-1 TB     |      768 MB    |
|---------------|----------------|
|    1-3 TB     |     1024 MB    |
|---------------|----------------|
|    3-5 TB     |     2048 MB    |
|---------------|----------------|
|    >=5 TB     |     2560 MB    |
+---------------|----------------+

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.crashplan.engine.plist
2.  Run this command to edit the backup engine:
sudo nano /Library/LaunchDaemons/com.crashplan.engine.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

-Xmx512m
4.  Edit that line to something larger (the value from the chart above) E.g.:
-Xmx1024m
5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

 

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

 

7.  Start the backup engine by typing:
sudo launchctl load /Library/LaunchDaemons/com.crashplan.engine.plist

Resolving Common Problems in CrashPlan PROe

This post is going to cover resolutions for some common CrashPlan problems you may encounter. I am assuming you have at least a basic level of familiarity with the Command Line interface. If this is not the case, I’d suggest asking for help from someone who does. Unless otherwise stated, these fixes should work for any version of CrashPlan (CP+, CPP, CPPe). I have written these in the order in which you should attempt them, unless you have evidence directing you past a certain step.

CrashPlan Client Constantly Crashing

Common Cause: CrashPlan backup engine is running out of memory.
Resolution: Edit the CrashPlan engine’s com.crashplan.engine.plist (“the plist file”) file to allow it to use more java memory. You will need to use Terminal for this, and edit the file using the ‘sudo’ command.
1.  Stop the backup engine by typing this into the Terminal application:
sudo launchctl unload /Library/LaunchDaemons/com.crashplan.engine.plist

2.  Run this command to edit the backup engine:

sudo nano /Library/LaunchDaemons/com.crashplan.engine.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

-Xmx512m

4.  Edit that line to something larger such as 640, 768, 896, or 1024. E.g.:

-Xmx1024m

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 increase it above 1024 if you have a really large file-selection.

5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

7.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.engine.plist

 

CrashPlan PROe Server Not Running

Common Cause: This can happen for any number of reasons.

Resolution: Manually stop and restart the LaunchDaemon.

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.proserver.engine.plist

2.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist

The server should start running and be accessible within 30 seconds. If this does not resolve the issue, continue down this page for further steps to try.

 

CrashPlan PROe Server Not Starting

Common Cause: CrashPlan PROe Server engine is running out of memory.

Resolution: Edit the CrashPlan engine’s com.crashplan.proserver.plist (“the plist file”) file to allow it to use more java memory. You will need to use Terminal for this, and edit the file using the ‘sudo’ command.

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.proserver.engine.plist

2.  Run this command to edit the backup engine:

sudo nano /Library/LaunchDaemons/com.crashplan.proserver.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

-Xss128k

4.  Edit that line to:

-Xss256k

This sets the maximum amount of memory that CrashPlan PROe Server can use. CrashPlan will not use that much until it needs it. Do not excede 256 1024 as, at the time of this writing, CrashPlan has not verified that the program is stable beyond that.

5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

7.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist

 

CrashPlan PROe Server Not Starting

Common Cause: CrashPlan PROe Server engine is having trouble reading Java. This is most common directly after an update to the server.

Resolution: Edit the CrashPlan engine’s com.crashplan.proserver.plist (“the plist file”) file to allow it to use a specific Java engine. You will need to use Terminal for this, and edit the file using the ‘sudo’ command.

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.proserver.engine.plist

2.  Run this command to edit the backup engine:

sudo nano /Library/LaunchDaemons/com.crashplan.proserver.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

<string>/usr/bin/java</string>

4.  Edit that line to:

<string>/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Commands/java</string>
This specifies the exact Java Virtual Machine that CrashPlan should use, rather than using the more common default setting.

5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

7.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist
If this does not resolve the issue, be sure to change the line back to its original settings from Step 3.