Skip to main content
Code42 Support

Upgrading Your Single-Server Environment From Version 4.2.x To 4.2.3.1

Applies to:
  • CrashPlan PROe

Overview

This article describes how to upgrade your single-server environment from version 4.2.0, 4.2.1, 4.2.2, or 4.2.3 to version 4.2.3.1 of the Code42 platform.

For multi-server environments, see Upgrading Your Multi-Server Environment From Version 4.2.x To 4.2.3.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

  1. Review the general instructions at Upgrading Version 4.2.x To 4.2.3.1.
  2. 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.
  3. Make sure that your host server meets the enterprise server requirements.
  4. (OS X) If your host server is running Java 6, upgrade to Oracle Java Development Kit (JDK) 7.
  5. Verify that your devices can connect to your master server on TCP port 4280 to download the device upgrade files.
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:

4.2.0 to 4.2.3.1

MD5 checksums

4.2.1 to 4.2.3.1

MD5 checksums

4.2.2 to 4.2.3.1

MD5 checksums

4.2.3 to 4.2.3.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.
    Clearing the cache ensures that you can access 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.2.3.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 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.

Troubleshooting the upgrade

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