Who is this article for?
CrashPlan for Small Business, no.
Code42 for Enterprise, yes.
Link: Product plans and features.
This tutorial describes what to expect when you upgrade your Code42 environment from version 4.2.3 or 184.108.40.206 to version 220.127.116.11 of the Code42 platform. Links to specific upgrade instructions are listed at the end of this article.
If your authority 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 upgrades from version 4.2.3 and 18.104.22.168 to 22.214.171.124 include changes to the following components. View Code42 platform version 4.3 release notes for details.
Code42 platform version 126.96.36.199 is compatible with the following components.
All operating systems:
|SharePlan mobile app||
* Indicates this version is bundled with Code42 platform version 188.8.131.52
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. If you have more than one enterprise server, upgrade the master server first.
Most enterprise 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 recently upgraded to version 4.2.x from an earlier version, wait 24 hours after upgrading your authority server and all storage servers before upgrading to another version. This waiting period ensures that all post-upgrade migration processes are complete before you start another upgrade.
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.
Upgrade and troubleshooting instructions
If you have any questions about upgrading your Code42 environment, or if you need assistance troubleshooting the upgrade, contact our Customer Champions.