- CrashPlan PROe
This tutorial describes how to upgrade your Code42 environment from enterprise server version 18.104.22.168 to version 4.1.6.
Affected Code42 Platform components
The upgrade from 22.214.171.124 to 4.1.6 includes the following upgrades. View 4.1.6 release notes for details.
Code42 platform version 4.1.6 is compatible with the following components.
|Code42 Code42 server||4.1.6*|
All operating systems:
|CrashPlan mobile app||
|SharePlan mobile app||
* Indicates this version is bundled with Code42 platform version 4.1.6
What to expect
Change for custom roles
In 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.
Upgrading your server
When you apply the upgrade, the enterprise server service shuts down and performs the upgrade tasks. When the upgrade tasks are complete, the enterprise server service starts up automatically.
Most server upgrades take 5-10 minutes to complete; however, upgrades in larger environments may take 15-30 minutes or more, depending on the size of the environment.
If you have more than one Code42 server, upgrade the master server first.
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.
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.
Upgrading your devices
Devices with the CrashPlan app or SharePlan app upgrade automatically once you enable the device upgrade. We recommend testing the upgrade on a single CrashPlan app or SharePlan app device before enabling automatic upgrades for all of your devices. Please review Best Practices for Upgrading Your Devices prior to upgrading.
Once you enable device auto-upgrade, you must restart your master server before your devices can upgrade. When the master server has restarted, devices reconnect to the upgraded master server at a randomized interval of 1–15 minutes. Devices download their upgrades from the master server over TCP port 4280 and upgrade themselves automatically. The randomized re-connect interval means that after the master server comes back online, there may be a delay before all devices have successfully upgraded.
Upgrading your mobile devices
Mobile devices do not automatically upgrade from the master server. Depending on your environment, either:
- Instruct your users to update the CrashPlan mobile app or SharePlan mobile app from their devices' app store.
- Configure your mobile device management tool to push an upgrade to your managed devices.
If you have only one enterprise server, read the full instructions at Upgrading Your Single-Server Environment From Version 126.96.36.199 To Version 4.1.6.
If you have more than one enterprise server, read the full instructions at Upgrading Your Multi-Server Environment From Version 188.8.131.52 To Version 4.1.6.
Troubleshooting your upgrade
If you encounter issues during the upgrade process, troubleshooting information, including what information to provide to a Customer Champions when reporting upgrade issues, is available in Troubleshooting The Upgrade From Version 184.108.40.206 To Version 4.1.6.
If you have any questions about upgrading your Code42 environment, please contact our Customer Champions.