- CrashPlan PROe
- Code42 CrashPlan (previously CrashPlan PROe)
Version 5.1 of the Code42 platform contains a number of new features, as well as fixes and enhancements. Highlights include:
- New CrashPlan app replace device wizard
- Updated CrashPlan notification area (Windows) and menu bar (OS X) interface for quick access to CrashPlan settings
- Refreshed, modern CrashPlan user interface for Linux
- Schedule-based bandwidth management
- New tools to monitor and manage user devices:
- New Code42 app for Splunk
The following components received updates in version 5.1:
- Code42 server for private cloud environments
- CrashPlan apps for Windows, OS X, and Linux
To upgrade your Code42 environment, see our upgrade instructions.
CrashPlan App Replace Device Wizard
CrashPlan app version 5.1 introduces a new replace device wizard to make it even easier for users to transfer files and update settings from a previous device.
Updated CrashPlan Notification Area And Menu Bar Apps
In CrashPlan app version 5.1, the Code42 CrashPlan icon in the notification area (Windows) and menu bar (OS X) has a new design, offering quick access to basic CrashPlan functions such as viewing backup status and starting or pausing a backup.
Refreshed, Modern CrashPlan User Interface For Linux
Joining the CrashPlan app improvements released for Windows and OS X devices in version 5.0, version 5.1 brings Linux users an overhauled user interface, making it even easier to manage and use CrashPlan for backup and recovery. See Changes To The Code42 CrashPlan App In Version 5.x for complete details.
Schedule-Based Bandwidth Management
New scheduled sending limits allow administrators to specify different data transfer rates for peak and off-peak business hours.
Enhanced Indexing And File Search
Endpoint monitoring leverages the CrashPlan app to monitor user devices for potential security problems or data leaks resulting from removable media, third-party cloud storage apps, unusual restore activity, and more. Administrators can view these events in real-time via the new Security web app.
Code42 Reporting Web App
The Code42 platform now features a Reporting web app, which enables administrators to easily search and view the backup status of users and devices.
The Code42 server contains a new command to export a sanitized version of the database, which removes all sensitive information. This enables administrators to quickly and easily provide Code42 Customer Champions data for troubleshooting, without exposing any sensitive or personally-identifiable information.
Fixes And Enhancements
- Security updates.
- Performance and stability improvements.
- Code42 server version 5.1 does not support SharePlan. Do not upgrade to version 5.1 if you wish to continue using any remaining SharePlan subscriptions. See SharePlan End Of Sale And End Of Support for additional details.
- The minimum required Java version for the Code42 server is now 1.8.
- Java is now bundled with the OS X Code42 server installer.
- Corrects an issue that could cause balancing archives from a Windows storage server to a master server in the same destination to fail.
- Improvements to server-to-server sync processes.
- Corrects LinkedIn link in the footer of emails sent from the Code42 server.
- In Code42 environments with more than one destination, devices can now back up normally to other destinations if the master server is offered as a destination but has no store points.
- Corrects a connectivity issue introduced in version 5.0.1 for provider storage environments using non-routable IP addresses for both the primary and secondary addresses. Under these circumstances, the on-premises master server can once again communicate with the Code42 cloud destination.
- Administrators no longer need to manually download upgrade files to upgrade from CrashPlan app version 4.x to 5.x.
- Configuring backup inclusions in the administration console to include
:allusersnow correctly applies the backup file selection to new users.
- Improved Korean translations.
- Corrects an issue introduced in version 5.0.1 in which removing a backup set from a device via the administration console did not correctly remove the backup set.
- Improved performance when exporting and downloading a CSV file with a large dataset from the administration console.
- Corrects an issue introduced in version 5.0.1 in which performing multiple searches from the Search box sometimes displayed results from a previous search.
- Removes the Sign up for an account option from the administration console sign in screen.
- Corrects an issue in which some users were unable to reset passwords via the administration console sign in screen when using Internet Explorer 10 or 11.
- Corrects an issue introduced in version 4.2 in which Use default archive encryption setting did not stay locked when an administrator locked the setting.
- When an administrator locks backup set settings in the administration console, the File Selection for the backup set now correctly displays a lock icon.
- Selecting Print from an action menu now correctly prints all items when the list is longer than one page.
- Moving a child organization to a different parent organization now more clearly indicates that the child organization does not inherit the Device Backup Default settings from the new parent organization.
- Organizations with multiple LDAP servers can now manually add users to the Code42 environment if one LDAP server is offline.
- In provider storage environments, web restores are now included in the Restore column count on the Device Details screen.
- Corrects an issue introduced for provider storage environments in version 5.0 in which restores made to a different device than the source backup device did not appear in the organization’s Restore History.
- Enabling archive key password security is no longer allowed from the administration console for users in organizations that use SSO. Instead, users are instructed to enable archive key password from the CrashPlan app. This prevents a known issue that could lead to the archive becoming inaccessible.
- Corrects an issue introduced in version 5.0 which could allow users to make changes to locked backup sets.
- Corrects an issue in which the the web-enabled licensing store could switch to the local licensing screen.
- Corrects a rare issue in which scrolling could stop working in specific circumstances.
- Improves instructions to more clearly indicate the correct syntax for custom file inclusions and exclusions.
- When manually entering a specific file path for included or excluded files, a backslash (\) is no longer allowed as a file path separator. Instead, use a forward slash (/).
Code42 server version 5.1.2 is bundled with both version 4.5.2 and 5.1.2 of the CrashPlan app.
- Security updates.
- Performance and stability improvements.
- After adopting a computer, CrashPlan now automatically updates the backup file selection to include the default backup file selection of the user's Organization. This ensures the new computer is protected. Like earlier versions of the CrashPlan app, the previous computer's file selection is also transferred as part of the adoption.
- Improvements to the CrashPlan app upgrade process.
- Windows users now have the ability to choose to restore files with original or current user permissions.
- The default backup set name now displays correctly in the CrashPlan app when the device name is locked in the administration console.
- Corrects an issue introduced in version 4.4 in which entering an incorrect archive key password required restarting the CrashPlan app in order to to re-enter the password.
- Improvements to logging.
- Corrects an issue for per user CrashPlan app installations in which the backup progress never reached 100% under certain circumstances.
- The CrashPlan app now displays fewer confirmation dialogs when installing per user on Windows devices.
- Corrects an issue introduced in version 4.4.1 in which the OS X CrashPlan apps customized to use SSO did not always display the Log in with Single Sign-On link on the sign in screen.
- Improves logging when restoring files backed up from an OS X device to a Windows device.
- CrashPlan apps installed per user that also use LDAP deferred passwords now start backing up automatically, without requiring the user to sign in first.
- When the CrashPlan app is installed per user in a non-default location on a Windows device, the CrashPlan tray app now opens correctly.
- Corrects an issue introduced in CrashPlan app version 4.5.0 in which the backup To Do list could incorrectly include files that haven't changed since the last backup.
- Corrects an issue introduced in version 4.4.1 in which OS X v10.8.5 devices could see repeated error messages in the system.log.
- Fixes a rare issue in which archive maintenance might not finish properly if a new version of a file was created with a timestamp older than the previous most recent version. This typically occurred if the device's time and date were manually changed to a time in the past.
- Fewer confirmation messages appear when uninstalling the Windows CrashPlan app.
Version 5.1.2 (also includes all fixes listed above for version 4.5.2)
- Numerous user interface fixes and updates.
- The CrashPlan app for Windows now uses a natively precompiled Java service, which does not require the Java Virtual Machine (JVM) to run.
- Improves accuracy of the backup status icons next to each destination.
- The CrashPlan app can no longer be administered from another device (sometimes referred to as "headless" operation). CrashPlan can only be controlled directly from the device running the CrashPlan app, or from the administration console.
- Improves compatibility for IPv6 literal hostnames.
- Bandwidth settings in Device Preferences > Network > Bandwidth LAN/WAN now correctly label the away and present values.
- Devices running the 64-bit version of Windows XP Professional are no longer allowed to upgrade to CrashPlan app version 5.x.
- Selecting a folder from the Downloads menu now displays the contents of the downloaded folder instead of opening the parent folder.
- When an administrator does not offer Local folders as a backup destination, the CrashPlan app no longer requires a restart to remove the Add Local Destination option.
- Users can no longer run multiple instances of the CrashPlan app on the same device at the same time.
- Changing the name of the default backup set now saves the new name when a user is deauthorized, instead of switching back to “Default.”
- Upgrading the CrashPlan app from version 4.4.1 on OS X 10.11 devices no longer requires restarting the device in order to start the upgraded CrashPlan app.
- Corrects an issue on Windows devices in which more than one CrashPlan icon could appear in the notification area.
- Corrects an issue for SSO environments which required some users to click OK multiple times to close the Single Sign-On window after selecting an SSO provider.
- Corrects an issue introduced in version 5.0.1 of the CrashPlan app in which backups might not start automatically if using a deferred custom LDAP installation.
If you have modified the CrashPlan app's text or images, these modifications are lost when you upgrade from version 4.x to version 5.1 of the CrashPlan app.
Announcing Linux Kernel 2.6.31 Retirement
CrashPlan app version 4.5.0 requires Linux kernel version 2.6.32 or later. Additionally, Code42 is retiring support for all distributions running kernel version 2.6.31 or earlier, such as:
- Red Hat Enterprise Linux 5
- CentOS 5
- Ubuntu 6, 7, 8, and 9
- Debian 5
As of November 30, 2015, the CrashPlan app will not automatically upgrade to version 4.5.0 on devices running kernel version 2.6.31 or earlier. CrashPlan app version 4.4.1 is the last supported version for kernels 2.6.31 and earlier. See Linux CrashPlan App Version 4.5 Cannot Back Up for more details.
Code42 server version 220.127.116.11 is compatible with the following components.
Windows and OS X:
|CrashPlan mobile app||
* Indicates this version is bundled with Code42 server version 18.104.22.168.
All storage servers in your Code42 environment must use the same Code42 server software version as your master server. For provider storage compatibility information, see the Code42 Public Cloud Version Policy.
Maintenance Update 22.214.171.124
We recommend all Code42 environments running version 5.1.2 or earlier upgrade to version 126.96.36.199 for critical security updates.
Version 188.8.131.52 contains the following fix for customers upgrading from version 5.1.2. If you are upgrading from an earlier version, see the complete list of features, fixes, and enhancements introduced in version 5.1.
- Corrects a security vulnerability that could allow unauthorized remote code execution.
- When the CrashPlan app is installed per user on a Windows device, executing the
shutdowncommand from the CrashPlan CLI requires the user to sign out of Windows and sign in again in order to restart CrashPlan.
- Moving a child organization to a different parent organization causes the child organization to inherit scheduled bandwidth settings from the parent organization, but not inherit any other Device Backup Default settings.
- On Linux devices with Java 1.6, attempting to upgrade CrashPlan app version 4.3 to version 4.4 or 4.5 fails in some circumstances, and may download multiple copies of the upgrade file. To correct this issue, install Java 1.7, then uninstall and reinstall the CrashPlan app.
- On slower network connections, administrators attempting to upload the Code42 server upgrade file to the master server may see the administration console session time out before the upgrade completes. To correct this issue, open the administration console CLI and enter
prop.set c42.auth.token.timeout 5400000. This temporarily increases the authorization token limit to 90 minutes.
- In the File Search web app, searching between two dates does not include results that match the end date. For example, to search for files modified between 6/10 and 6/16, enter an end date of 6/17.
- When the CrashPlan app is installed with user privileges on a Linux device, users may be required to manually start the CrashPlan service after restarting the device.
- On Windows devices, the CrashPlan service does not start if the user selects the default installation method (for everyone) but then navigates back in the installation wizard and changes to a per user installation. To correct this issue, uninstall the CrashPlan app and reinstall per user.
- Devices running Windows Server 2012 R2 do not upgrade to the CrashPlan app version 4.5.2 when installed per user. To use the CrashPlan app on Windows Server 2012 R2, use the default (for everyone) installation method.
- In some cases, the administration console can incorrectly display a sending limit of 0.00 Mbps for device backups. This does not reflect the actual state of device backups; devices still back up at the defined rate, but the Devices > Network summary may display the rate as 0.00 Mbps.
- While upgrading the CrashPlan app from the administration console, a message says the CrashPlan app will be upgraded to an earlier version. This is only a UI issue. Devices upgrade to the correct version of the CrashPlan app (4.x or 5.x) in use by each organization.