Skip to main content
Code42 Support

Upgrading Versions 3.6.4.x And 3.6.5 To Version 3.6.5.1

Applies to:
  • CrashPlan PROe

Overview

This tutorial describes how to upgrade your Code42 environment from versions 3.6.4.1, 3.6.4.3, and 3.6.5 to version 3.6.5.1 of the Code42 platform.

Affected Code42 Platform components

The upgrade to version 3.6.5.1 includes the following upgrades. View 3.6.5.1 release notes for details.

Upgraded Not Upgraded
  • Enterprise server
  • CrashPlan app*
  • CrashPlan mobile app

* There is no CrashPlan app upgrade from version 3.6.5 to 3.6.5.1. Upgrading from version 3.6.4.1 or 3.6.4.3 does include a CrashPlan app upgrade.

Version compatibility

Code42 platform version 3.6.5.1 is compatible with the following components.

Component Compatible Versions
Code42 Code42 server 3.6.5.1
Code42 app

All operating systems:

  • 3.6.5
  • 3.6.4
  • 3.6.3
CrashPlan mobile app
  • Android: 3.5.4
  • iOS:
    • 3.5.5
    • 3.5.4
  • Windows Phone: 3.5.4

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 authority server first.

Managed appliance Upgrades
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.

Server memory considerations

We recommend that enterprise servers have 4 GB of memory before upgrading to 3.6.5.1.

Upgrading your devices

Devices with the Code42 app upgrade automatically once the administrator enables the device upgrade. We recommend running the upgrade on a single Code42 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 authority server before your devices can upgrade. When the authority server has restarted, devices reconnect to the upgraded authority server at a randomized interval of 1-15 minutes. Devices download their upgrades from the authority server over TCP port 4280 and upgrade themselves automatically. The randomized re-connect interval means that, after the authority 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.

Upgrading your mobile devices

There is no upgrade to mobile devices in version 3.6.5.1.

Upgrade instructions

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 3.6.5.1.

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 3.6.5.1.

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 3.6.5.1.

If you have any questions about upgrading your Code42 environment, please contact our Customer Champions.