Who is this article for?
CrashPlan for Small Business, no.
Code42 for Enterprise, yes.
Link: Product plans and features.
This article describes how to upgrade the Code42 servers in your Code42 environment to version 5.3.1, and to perform associated CrashPlan app upgrades. The steps below apply to upgrades from 5.1.x, 5.2.x, and 5.3.0.
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 upgrade from version 5.1.x, 5.2.x, and 5.3.0 to 5.3.1 includes changes to the following components. View Code42 platform version 5.3.1 release notes for details.
Code42 server version 5.3.1 is compatible with the following components.
Windows, Mac, and Linux:
All storage servers in your Code42 environment must use the same Code42 server software version as your authority server.
- If the File Selection setting is locked in the Code42 console (Settings > Device Backup > Backup), you must take action to ensure all Code42 app devices are using version 4.5.2 or later before upgrading to Code42 server version 5.3.1.
- Use the Device Status Report to view devices' Code42 app version.
- If upgrades are required, see Upgrading CrashPlan Devices In Your Code42 Environment.
- Beginning with version 5.3.0 of the Code42 platform, the Code42 app is no longer bundled with the Code42 server. Compatible Code42 app versions are available for download from the new App Downloads screen in the Code42 console. See Adding Clients To Your Code42 environment for more details.
Do not make any configuration changes to Code42 for Enterprise settings in the Code42 console while upgrading your Code42 server. As a best practice, wait 24 hours after pushing any configuration changes to Code42 for Enterprise apps before you upgrade the Code42 server, and wait 24 hours after the server upgrade completes before changing any settings. Contact our Customer Champions for support if you have any questions.
- After the Code42 server upgrade completes, you may need to refresh the Code42 console to see the new App Downloads screen.
- Depending on your browser's cache settings, you may be prompted to upgrade clients after the Code42 server upgrade completes. Ignore this prompt; client upgrades are managed from the new App Downloads screen beginning in version 5.3.
- In very rare cases, using the version 5.3.x Code42 console to push version retention setting changes to offline devices can cause corrupt file versions to be backed up once the device comes back online. To avoid potential problems, Code42 recommends either: making changes to version retention settings from the Code42 console before upgrading to version 5.3.x, or making changes to version retention settings from the Code42 app on individual devices. Alternatively, upgrade to version 5.4.0 (which corrects this issue) instead of 5.3.x.
If you have any questions about upgrading your Code42 environment, or if you need assistance troubleshooting the upgrade, contact our Customer Champions for support.
Step 1: Download the upgrade file
Download the upgrade file for your server operating system. If your Code42 environment has Code42 servers running on different operating systems, download the upgrade file for each operating system:
Step 2: Upgrade your Code42 Servers
Follow our instructions to upgrade the Code42 servers in your Code42 environment: