About Crashplan
Updated June 18, 2024 15:54 OverviewIf the CrashPlan app:Does not open when launchedCloses abruptly while backing up filesOpens, but displays the message: Cannot connect to background service ...you might have one of the following situations:You are using an unsupported version of CrashPlan or installing CrashPlan on an unsupported operating system.In this situation, the CrashPlan app may not run because it is in an unsupported state. To resolve, upgrade to a supported version of the CrashPlan app and make sure you are running a supported operating system.The memory settings are inadequate (applies to Windows, Mac, and Linux)In this situation, there is not enough memory allocated to the CrashPlan app. To correct the problem, follow the steps below in Solution for any supported system to reinstall the CrashPlan app and adjust your CrashPlan app memory settings.Solution for supported systemsFollow these directions if you encounter the issues described in the Overview and run a supported CrashPlan app on a supported Windows, Mac, or Linux system.By default, memory allocation is dynamically set to use 25% of the physical memory on the device. However, to correct performance problems, you may need to assign more or less system memory.Step 3: Open the CrashPlan appIf 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 of the above-described symptoms reoccurs after following Steps 1 and 2, then contact our technical support team.Step 4: Update the CrashPlan app memory settingsDetermine how much memory your CrashPlan app needs:Backup selection sizeMemory setting (MB)1.5 TB or 1.5 million files15362 TB or 2 million files20482.5 TB or 2.5 million files25603 TB or 3 million files30724 TB or 4 millions files4096Use the keyboard shortcut for your operating system:Windows: Ctrl+Shift+CMac: Option+Command+CLinux: Ctrl+Shift+CThe command-line area opens.Enter the command:java mx nnnn,restartwhere nnnn is the number for 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 of the above-described symptoms reoccurs after following Steps 1 and 2, then contact our technical support team.Step 5: Reconnect your backupIf the CrashPlan app opened successfully, follow the instructions in Replace your device using CrashPlan to reconnect your newly installed CrashPlan app to the backup archives created by the previous installation.
Key features of the Crashplan that are enabled through these drivers include:
- CrashPlan for MSPs One Pager - CrashPlan
- SOLVED CrashPlan not connected to CrashPlan Central
- CrashPlan 6.8.3 : r/Crashplan - Reddit
- CrashPlan commands – CrashPlan Help Center
- SOLVED CrashPlan not connected to CrashPLan Central
- Malware scan of crashplan-x64_4.4.1_win.exe (CrashPlan
- Two-Factor Authentication for CrashPlan – CrashPlan
3: (Optional) Manually start a user profile backupTo immediately start a user profile backup for a device, use the steps for the CrashPlan console or the CrashPlan app:From the CrashPlan consoleOpen the CrashPlan console.Press Ctrl+Shift+X.The CrashPlan console command-line area opens.Enter: cc migration.backup.run Replace with the GUID of the device containing the user profile data you want to back up.Press Enter.The USMT backup runs in the background of the CrashPlan app and a folder named "user_settings" is added to the backup selection, which contains the device's .MIG files.From the CrashPlan appOpen the CrashPlan app.Open CrashPlan Commands using one of the following methods:Double-click the CrashPlan logo in the upper-left corner.Enter the keyboard shortcut for your operating system:Windows: Ctrl+Shift+CMac: Option+Command+CLinux: Ctrl+Shift+CEnter: migration.backup.runPress Enter.The USMT backup runs in the background of the CrashPlan app and a folder named "user_settings" is added to the backup selection, which contains the device's .MIG files.Step 4: Confirm user profiles are backed upTo confirm that all devices being migrated or upgraded have completed a user profile backup:From the CrashPlan console, select Administration > Status > Reporting.(Optional) On the Device Status tab, enter search criteria to filter for specific devices.Click Run Report.Click the column selector icon and select User Profile Status.In the User Profile Status column, confirm the devices display the status Created, Backed Up.For devices that do not display the status Created, Backed Up, use the report results to help you determine if there is a problem with USMT, or with the CrashPlan app backup:Created: the .MIG file was successfully created by ScanState, but the backup status is unavailable. The backup status may be unavailable soon after initially enabling user profile status backup, or for devices using CrashPlan app version 6.7.0 and earlier.Created, Not backed Up: the .MIG file was successfully created by ScanState, but it is not backed up by the CrashPlan app.Failed: the .MIG file failed to be created by ScanState.N/A: Indicates either:The device has not reported a success or failure message.User Profile Backup is not enabled for this device's organization.This is a non-Windows device.Step 5: Prepare new devicesPrepare your new device. Your preparations may include:Re-imaging the
