Who is this article for?
CrashPlan for Enterprise, no.
Code42 for Enterprise, yes.
CrashPlan for Small Business, yes.
This article applies to on-premises authority server version 3.
This tutorial describes how to upgrade your Code42 environment from versions 188.8.131.52, 184.108.40.206, and 3.6.5 to version 220.127.116.11 of the Code42 platform.
Affected Code42 Platform components
The upgrade to version 18.104.22.168 includes the following upgrades. View 22.214.171.124 release notes for details.
- Enterprise server
- CrashPlan app*
* There is no CrashPlan app upgrade from version 3.6.5 to 126.96.36.199. Upgrading from version 188.8.131.52 or 184.108.40.206 does include a CrashPlan app upgrade.
Code42 platform version 220.127.116.11 is compatible with the following components.
All operating systems:
What to expect
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 and the nature of the specific upgrade.
If you have more than one enterprise 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.
Server memory considerations
We recommend that enterprise servers have 4 GB of memory before upgrading to 18.104.22.168.
Upgrading your devices
There is no device upgrade from 3.6.5 to 22.214.171.124. The CrashPlan app remains on version 3.6.5. Upgrades from 126.96.36.199 and 188.8.131.52 do contain CrashPlan app upgrades (to version 3.6.5).
Devices with the CrashPlan app upgrade automatically once the administrator enables the device upgrade. We recommend running the upgrade on a single CrashPlan 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.
Performing sequential upgrades
When performing multiple upgrades in sequence, we recommend that you allow time for devices to complete one upgrade before beginning a later upgrade.
If you have only one enterprise server, read the full instructions at Upgrading Your Single-Server Environment From Versions 3.6.4.x And 3.6.5 To Version 184.108.40.206.
If you have more than one enterprise server, read the full instructions at Upgrading Your Multi-Server Environment From Versions 3.6.4.x And 3.6.5 To Version 220.127.116.11.
Troubleshooting your upgrade
If you encounter issues during the upgrade process, troubleshooting information, including what information to provide to our Customer Champions when reporting upgrade issues, is available in Troubleshooting The Upgrade From Versions 3.6.4.x And 3.6.5 To Version 18.104.22.168.
If you have any questions about upgrading your Code42 environment, please contact our Customer Champions.