Skip to main content
Code42 Support

Upgrading Your Single-Server Environment From Version 4.2.3.x To 4.3.4.1

Applies to:
  • CrashPlan PROe

Overview

This article describes how to upgrade your single-server environment from versions 4.2.3 or 4.2.3.1 to version 4.3.4.1 of the Code42 platform.

For multi-server environments, see Upgrading Your Multi-Server Environment From Version 4.2.3.x To 4.3.4.1.

Considerations

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.

Before you begin

Review the general instructions at Upgrade Version 4.2.3.x To 4.3.4.1.

  1. From the administration console Licensing screen, verify that your support is up-to-date.
    Only environments under current support and maintenance are able to upgrade.
  2. Make sure that your host server meets the enterprise server requirements.
  3. (OS X) If your host server is running Java 6, upgrade to Oracle Java Development Kit (JDK) 7.
  4. Verify that your devices can download the device upgrade files from your enterprise server.
    Depending on whether your enterprise server is configured to require SSL, devices connect on TCP 4285 (for HTTPS) or TCP 4280 (HTTP).
  5. (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 as a reference when you 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
Test the upgrade
We strongly recommend that you perform the upgrade in a test Code42 environment before upgrading your production Code42 environment.
Wait at least 24 hours before upgrading
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.

Step 1: Download upgrade and installation files

Download the upgrade file for your server operating system:

Version 4.2.3 to 4.3.4.1

MD5 checksums

Version 4.2.3.1 to 4.3.4.1

MD5 checksums

Step 2: Prepare your production environment

  1. Sign in to your enterprise server's administration console.
  2. Dump your enterprise server's database:
    1. Navigate to Settings > Server.
    2. From the action menu, select Dump Database.
  3. In Settings > Server, disable Auto-upgrade devices.
    See Best Practices For Upgrading Your Devices for more details.

Step 3: Upgrade your Enterprise Server

  1. Sign in to the administration console of your enterprise server.
  2. Navigate to Settings > Server.
  3. From the action menu, select Upgrade.
  4. Locate and upload the upgrade file.
  5. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The enterprise server restarts after successfully upgrading.
  6. Clear your browser cache to use the newest version of the administration console.
  7. After the enterprise server restarts, sign in to the administration console.
    The message "Server Upgrade Complete" appears.
  8. Click No, I'll Upgrade Later to postpone upgrading all client devices.
  9. Verify the following:
    • Under Settings > Server, the Current server version is 4.3.4.1.
    • You are able to view the details of an organization, a user, and a device. You can also do spot checks of various configuration screens, but verifying an organization, user, and device's details provides good coverage.
    • Your devices are able to reconnect to the enterprise server.
    • You are able to back up and restore, or sync and share, files from your devices.
  10. (Syslog only) If your enterprise server was configured to send logs to a syslog server, use system properties to configure syslog settings.
    Use the backed up copy of the conf_base.groovy file as a reference.

Step 4: Upgrade your devices

  1. After the enterprise server upgrade is complete, test the CrashPlan app or SharePlan app upgrade for one existing device:
    1. In the administration console, go to Devices > Overview.
    2. Click the name of the device.
    3. From the action menu, select Upgrade.
    4. Click Upgrade to upgrade the device.
      The upgrade command is sent to the device immediately and the device begins the upgrade process. When the upgrade is complete, the administration console displays a “success” message in the lower left corner.
  2. Verify the test device upgrade:
    1. Launch the CrashPlan app or SharePlan app on the device and verify the version number.
    2. Confirm that you are able to back up and restore, or sync and share, files from the test device.
  3. When you are ready to upgrade the rest of your Code42 environment's devices:
    1. Sign in to the master server's administration console.
    2. From Settings > Server, enable Auto-upgrade devices.
    3. Click Save.
      A confirmation message appears.
    4. Click Restart.

Step 5: Upgrade 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.

Troubleshooting the upgrade

For help resolving upgrade issues, see Troubleshooting The Upgrade From Version 4.2.3.x To Version 4.3.4.1. If you need further assistance troubleshooting the upgrade, contact our Customer Champions.