Skip to main content
Code42 Support

Upgrade Version 3.6.3.1 To 3.6.4.1

Applies to:
  • CrashPlan PROe

Overview

This tutorial describes how to upgrade your Code42 environment from enterprise server version 3.6.3.1 to version 3.6.4.1.

Affected components

The upgrade from 3.6.3.1 to 3.6.4.1 includes the following upgrades. View 3.6.4 release notes for details.

Upgraded Not Upgraded
  • Enterprise server
  • CrashPlan app
  • CrashPlan mobile app (iOS)

CrashPlan mobile app (Android, Windows Phone)

Version compatibility

CrashPlan for Business version 3.6.4.1 is compatible with the following components.

Component Compatible Versions
Code42 Code42 server

3.6.4.1

CrashPlan app

All operating systems:

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

If you have more than one Code42 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.

Upgrading your devices

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 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 CrashPlan devices from 3.6.3

When the CrashPlan app is upgraded from version 3.6.3 to a later version, the CrashPlan app may display the following Software Update prompt on computers running OS X:
To open "java," you need a Java SE 6 runtime.
Would you like to install one now?

You can instruct users to dismiss this prompt by clicking Not Now. See our troubleshooting article for additional details.

Upgrading your mobile devices

Mobile devices do not automatically upgrade from the authority 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.

Upgrade instructions

If you have only one enterprise server, read the full instructions at Upgrading Your Single-Server Environment From Version 3.6.3.1 To Version 3.6.4.1.

If you have more than one enterprise server, read the full instructions at Upgrading Your Multi-Server Environment From Version 3.6.3.1 To Version 3.6.4.1.

Troubleshooting your upgrade

If you encounter issues during the upgrade process, troubleshooting information, including what information to provide to a Customer Champion when reporting upgrade issues, is available in Troubleshooting The Upgrade From Version 3.6.3.1 To Version 3.6.4.1.

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