Skip to main content
Code42 Support

Upgrading Version 4.1.6.3 To 4.2.3.1

Applies to:
  • CrashPlan PROe

Overview

This tutorial describes what to expect when you upgrade your Code42 environment from version 4.1.6.3 to version 4.2.3.1 of the Code42 platform. Links to specific upgrade instructions are listed at the end of this article.

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.

Affected Code42 Platform components

The upgrade from version 4.1.6.3 to 4.2.3.1 includes changes to the following components. View Code42 platform version 4.2 release notes for details.

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

Version compatibility

Code42 platform version 4.2.3.1 is compatible with the following components.

Component Compatible Versions
Code42 server 4.2.3.1*
Code42 app

All operating systems:

  • 4.2.0*
  • 3.7
  • 3.6.4
CrashPlan mobile app
  • Android:
    • 4.2.1
    • 4.2.0
    • 3.5.4
  • iOS:
    • 4.2.0
    • 3.5.5
SharePlan app
  • Windows:
    • 4.2.0*
    • 4.1.6
  • Mac:
    • 4.2.0*
    • 4.1.6
SharePlan mobile app
  • Android:
    • 4.2.1
    • 4.2.0*
    • 4.1.6
  • iOS:
    • 4.2.0*
    • 4.1.6

* Indicates this version is bundled with Code42 platform version 4.2.3.1

Before upgrading to version 4.2.3.1

Version 4.2.0 introduced changes to the Code42 platform that have implications for the upgrade process.

Reverting or recovering from this upgrade
After upgrading to version 4.2.3.1, you cannot revert or "roll back" your Code42 environment to a previous version.

Make sure all Store Points are online

Version 4.2.0 introduced changes to data storage in your Code42 environment. To ensure that these changes are made during the upgrade, all store points must be connected before you upgrade from 4.1.6.3 to version 4.2.3.1. If all store points are not connected before you upgrade, the enterprise server will not start after the upgrade, and you must contact our Customer Champions to proceed.

Connect all Store points
Before upgrading, all store points in your Code42 environment must be online and visible to the Code42 server on which they reside. If any store points are not connected, the Code42 server will not start after the upgrade, and you must contact our Customer Champions for Code42 for Enterprise support or CrashPlan PRO support to proceed.

Disable LDAP sync

Known issue in version 4.2.3
Version 4.2.3 of the Code42 platform is affected by a known issue related to LDAP sync. In certain circumstances, this issue can cause data loss.

We recommend that you:

  1. Disable LDAP sync before upgrading to version 4.2.3.
  2. Enable LDAP sync only after upgrading to version 4.3.4 or later.

Migrate 32-bit Windows Enterprise Servers to 64-bit Windows

You cannot upgrade a 32-bit Windows Code42 server to version 4.2 or later. To use version 4.2 or later of the Code42 server on Windows, you must move your 32-bit Windows Code42 server to a supported operating system.

Back up the syslog configuration

Enterprise servers configured to use syslog only

If your enterprise server is configured to send logs to a syslog server, make a backup copy of the conf_base.groovy file, which contains the syslog settings. You will use this file to reconfigure syslog after the upgrade is complete.

The location of conf_base.groovy varies based on the operating system:

  • Linux: /var/opt/proserver/conf
    Applies to Code42 servers installed as root on Ubuntu
  • Windows: C:\ProgramData\PROServer\conf
  • OS X: /Library/Application Support/CrashPlan/PROServer/conf

After the upgrade is complete, place the conf_base.groovy file back in its original location.

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.

Longer upgrade process
The upgrade to version 4.2.3.1 may take significantly longer than most enterprise server upgrades. Depending on the size of your environment, upgrading each enterprise server may take as long as 45 to 60 minutes.

Upgrading your devices

Upgrading your Code42 servers to version 4.2.3.1 does not upgrade your CrashPlan app devices. To automatically upgrade your devices, we recommend continuing to upgrade to a later version of the Code42 platform.

Upgrading the SharePlan App on Windows

When upgrading the SharePlan app on Windows devices, the automatic upgrade may take up to 15 minutes to complete. You can restart the SharePlan app service on the affected device to complete the upgrade immediately.

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