- CrashPlan PRO
- CrashPlan PROe
- Code42 CrashPlan (previously CrashPlan PROe)
In many cases, the CrashPlan app's default memory setting supports backing up as much as 1 TB (1,024 GB) of data or as many as 1 million files. However, you may need to assign additional system memory if the CrashPlan app:
- Does not open when launched
- Opens, but displays the message: Unable to connect to the backup engine, retry?
- Closes abruptly while backing up files
This article describes how to diagnose and fix the problem on a 64-bit system to resume successful backups.
- 64-bit CrashPlan app running on 64-bit Windows
- CrashPlan app running on OS X
- CrashPlan app running on Linux
If your CrashPlan app and operating system do not match any of the above, or if you are unsure, see CrashPlan Does Not Run.
Recommended solution for 64-bit systems
If your operating system is 64-bit Windows, OS X, or Linux, follow the instructions below to resolve the issue.
Step 1: Completely uninstall the CrashPlan app
- Open the Control Panel, and select:
- Windows 7/8/10: Uninstall a Program
- Vista: Programs and Features
- Windows XP: Add/Remove Programs
- Select your CrashPlan product (CrashPlan PRO or Code42 for Enterprise), and choose Uninstall.
You may be prompted that another user on the device is signed in. If another user is signed in, it may prevent the CrashPlan app from uninstalling completely. Code42 recommends coordinating with other users to ensure all users are signed out of the account before continuing.
If the uninstallation fails, follow Microsoft's instructions to fix problems that block programs from being installed or removed.
- Remove the following directory from your device:
- If installed for all users:
- Windows Vista, 7, 8, Server 2008, and Server 2012: C:\ProgramData\CrashPlan
- Windows XP: C:\Documents and Settings\All Users\Application Data\CrashPlan
- If installed per user:
- If installed for all users:
- Open the Finder.
- Press Command-Shift-G
A dialog box appears: Go to the folder.
- Paste this text into the dialog box:
- Installed for everyone: /Library/Application Support/CrashPlan/Uninstall.app
- Installed per user: ~/Library/Application Support/CrashPlan/Uninstall.app
- Click Go.
- Double-click Uninstall.
- Follow the prompts to complete the uninstall process.
- Remove the following directory from your system:
- Installed for all users: /Library/Application Support/CrashPlan
- Installed per user: ~/Library/Application Support/CrashPlan
- Download the latest version of CrashPlan for Linux:
- Uncompress the TGZ file to Downloads.
- Open Terminal and enter:
- Press Enter.
- Then enter:
sudo ./uninstall.sh -i /usr/local/crashplan
- Press Enter.
- At the prompt, type YES to uninstall and press Enter.
- Remove the following directory from your system: /var/lib/crashplan
Step 2: Reinstall the CrashPlan app
- Download the latest version of CrashPlan for your operating system:
- Once the download completes, unzip the installer.
- Run the CrashPlan Installer:
- Windows: Double-click the CrashPlan EXE file.
- OS X: Double-click the CrashPlan DMG file, then double-click Install CrashPlan.
- Linux: Run the install.sh shell script.
- Follow the prompts to complete the installation.
- Once the installation is complete, choose Existing Account on the sign in screen and enter your CrashPlan account information.
Additional installation information is available in the Installing CrashPlan article.
Step 3: Open the CrashPlan app
- If the CrashPlan app opens, continue to Step 4 to update memory settings in the CrashPlan app.
If the CrashPlan app does not open, or if any one of the above-described symptoms reoccurs after following Steps 1 and 2, then contact our Customer Champions for Code42 for Enterprise support or CrashPlan PRO support.
Step 4: Update CrashPlan memory settings
- Determine how much memory your CrashPlan app needs:
|Backup Selection Size||Recommended Memory Setting (MB)|
|1.5 TB or 1.5 million files||1536|
|2 TB or 2 million files||2048|
|2.5 TB or 2.5 million files||2560|
|3 TB or 3 million files||
- Double-click the CrashPlan logo in the upper-right corner of the CrashPlan app.
The CrashPlan command-line area opens.
- Enter the command:
java mx nnnn,restart
where nnnn is the new memory setting.
- Press Enter.
The CrashPlan app closes. The CrashPlan service stops. Then the CrashPlan service restarts.
- Open the CrashPlan app.
- If the CrashPlan app opens successfully, continue to Step 5.
- If the CrashPlan app does not open, or if any one of the above-described symptoms reoccurs after following Steps 1 and 2, then contact our Customer Champions for Code42 for Enterprise support or CrashPlan PRO support.
Step 5: Reconnect your backup with adoption
If the CrashPlan app opened successfully, you must now reconnect your CrashPlan app to the backup archives created before the symptoms occurred.
- In the Continue Backup message, click Adopt.
I don't see the option to Adopt.
- Select the computer that you want to adopt. You can identify which computer to adopt in three different ways:
- Computer name
- Time of last backup
- Archive size
- Enter your Email and Password again and click Sign In.
The Adoption Complete! message displays.
After adopting a previous computer, a scan launches to compare the contents of your backup file selection against your existing backup archive. It may look like your files are backing up again, and the estimated time to complete may seem unusually long. However, CrashPlan uses data de-duplication to identify what is already backed up. CrashPlan will only back up what has changed (For example: folder paths if files have moved, new files). This is a normal part of CrashPlan's operation, but if you are concerned, there are several ways to confirm that your backup isn't starting over.