- CrashPlan PROe
This article describes how to upgrade the enterprise servers in your Code42 environment from version 220.127.116.11 to version 18.104.22.168, and to perform associated CrashPlan app upgrades.
If your master server is a Code42 managed appliance, our Customer Champions work with you to upgrade your Code42 environment. Do not attempt to upgrade your environment on your own.
Affected Code42 Platform components
The upgrade from version 22.214.171.124 to 126.96.36.199 includes changes to the following components. View Code42 Platform Version 188.8.131.52 Release Notes (From 184.108.40.206) for details.
||None—all components are upgraded.|
Code42 platform version 220.127.116.11 is compatible with the following components.
All operating systems:
|CrashPlan mobile app||
|SharePlan mobile app||
* Indicates this version is bundled with Code42 platform version 18.104.22.168
Considerations for upgrading to version 22.214.171.124
Cannot revert upgrade to version 4.2.x
Version 4.2.0 introduced changes to the Code42 platform that have implications for the upgrade process.
After upgrading to version 126.96.36.199, you cannot revert or "roll back" your Code42 environment to a previous version.
Make sure all Store Points are online
Version 4.2.0 introduced changes to data storage in your Code42 environment. To ensure that these changes are made during the upgrade, all store points must be connected before you upgrade to version 188.8.131.52. If all store points are not connected before you upgrade, the enterprise server will not start after the upgrade, and you must contact our Customer Champions to proceed.
Before upgrading, all store points in your Code42 environment must be online and visible to the Code42 server on which they reside. If any store points are not connected, the Code42 server will not start after the upgrade, and you must contact our Customer Champions for Code42 for Enterprise support or CrashPlan PRO support to proceed.
Disable LDAP sync
Version 4.2.3 of the Code42 platform is affected by a known issue related to LDAP sync. In certain circumstances, this issue can cause data loss.
We recommend that you:
Minimum Oracle Java version
Enterprise server version 184.108.40.206 requires Oracle Java 7 or later to run. Depending on your host server operating system, you may need to update Oracle Java on your enterprise servers (as described in the upgrade instructions below) before upgrading to version 220.127.116.11.
Change for custom roles
After version 4.1.6, the ability to restore data from the CrashPlan app has been moved to a user permission, cpd.restore. As part of the upgrade process, your custom roles will be updated to reflect this change. Specifically, all custom roles that contain the permission cpd.login will also have the new permission cpd.restore.
For more information on custom roles, see Best Practices For Custom Roles & Permissions.
No upgrade for OS X CrashPlan Apps
Due to a known issue, upgrade resources for OS X CrashPlan apps are not included. To upgrade your OS X devices, continue upgrading your Code42 environment to version 5.1.2.
Back up the syslog configuration
Enterprise servers configured to use syslog only
If your enterprise server is configured to send logs to a syslog server, make a backup copy of the conf_base.groovy file, which contains the syslog settings. You will use this file to reconfigure syslog after the upgrade is complete.
The location of conf_base.groovy varies based on the operating system:
- Linux: /var/opt/proserver/conf
Applies to Code42 servers installed as root on Ubuntu
- Windows: C:\ProgramData\PROServer\conf
- OS X: /Library/Application Support/CrashPlan/PROServer/conf
After the upgrade is complete, place the conf_base.groovy file back in its original location.
Upgrading Linux Enterprise Servers
If you upgrade a Linux enterprise server that does not have the unzip utility, the upgrade process will log several failed attempts to run unzip. However, the upgrade process will complete successfully using a Java unzip utility instead, so the log entries are not a cause for concern.
If you have any questions about upgrading your Code42 environment, or if you need assistance troubleshooting the upgrade, contact our Customer Champions.
Step 1: Confirm the Java version of your Enterprise Servers
For each enterprise server in your environment:
- Confirm that the installed Java version is Java 7.
If your enterprise servers use an earlier version of Java, the upgrade fails. We recommend using the latest release within Java 7.
- If the installed version of Java is earlier than Java 7, upgrade your enterprise server to Java 7.
Step 2: Download the upgrade file
Download the upgrade file for your server operating system. If your Code42 environment has enterprise servers running on different operating systems, download the upgrade file for each operating system:
Step 2: Upgrade your Enterprise Servers
Follow our instructions to upgrade the enterprise servers in your Code42 environment:
Step 3: Upgrade your CrashPlan devices
Follow our instructions to upgrade CrashPlan devices in your Code42 environment.
Step 4: Continue upgrading to a later version
Version 18.104.22.168 is affected by several issues that are resolved in later versions. Code42 strongly recommends that you continue upgrading to version 5.1.2.