Skip to main content
Code42 Support

Upgrading Your Multi-Server Environment From Version 4.1.6.3 To 4.2.3.1

Applies to:
  • CrashPlan PROe

Overview

This tutorial describes how to upgrade your multi-server environment from version 4.1.6.3 to version 4.2.3.1 of the Code42 platform.

For single-server environments, see Upgrading Your Single-Server Environment From Version 4.1.6.3 To 4.2.3.1.

Considerations

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.
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 Upgrade Version 4.1.6.3 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 servers meet the enterprise server requirements.
  4. (Windows) If a host server is running 32-bit Windows, move the enterprise server to a supported operating system.
    Enterprise server version 4.2.0 and later does not support 32-bit Windows operating systems.
  5. (OS X) If a host server is running Java 6, upgrade to Oracle Java Development Kit (JDK) 7.
  6. (Syslog only) If an enterprise server is configured to send logs to a syslog server, back up the syslog configuration file.
  7. 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.
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 for Small Business support to proceed.

Step 1: Download upgrade and installation files

Download the upgrade file for your server operating system. If your Code42 environment has enterprise servers running on different operating systems, download the upgrade file for each operating system:

MD5 checksums

Step 2: Prepare your production environment

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

Step 3: Choose a Storage Server upgrade method

The storage servers in your Code42 environment can be upgraded automatically or manually. When Auto-upgrade storage servers is enabled in the master server administration console, storage servers are automatically upgraded after the master server is upgraded.

Automatic Storage Server upgrades recommended
We recommend using the automatic storage server upgrade method to save time and reduce the possibility for human error. However, if you want to tightly control when individual storage servers are upgraded to manage down time, do not use the automatic upgrade method.

Enable or disable automatic storage server upgrades:

  1. Sign in to the administration console on your master server.
  2. Go to Settings > Server.
  3. Enable or disable Auto-upgrade storage servers, then click Save.
  4. If you enabled Auto-upgrade storage servers and one or more of your storage servers are running on an operating system that differs from your master server, place the upgrade file(s) for each operating system in the appropriate directory on the master server:
    • Linux: /opt/proserver/upgrade
      Applies to Code42 servers installed as root on Ubuntu
    • Windows: C:\Program Files\CrashPlan PROe Server\upgrade
    • OS X: /Applications/PROServer.app/Content/Resources/Java/upgrade

Step 4: Upgrade your Master Server

  1. Sign in to the administration console of your master 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 master 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 master 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, a user, and device provides good coverage.
    • Your devices are able to reconnect.
    • You are able to back up and restore, or sync and share, files from your devices.
  10. (Syslog only) If your master server was configured to send logs to a syslog server, place the configuration file that you backed up in its original location, then restart the master server.

Step 5: Upgrade your Storage Servers

Manual storage server upgrades only; skip this step if you enabled automatic storage server upgrades.

For each storage server in your Code42 environment:

  1. Sign in to the administration console on your storage 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 storage 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 storage server restarts, sign in to the administration console.
  8. Double-click the Code42 logo in the upper left to access the administration console command-line interface.
  9. Enter this command to confirm the upgrade was successful:
    version
    The administration console returns the current version number, which should be 4.2.3.1.
  10. Enter this command to sync your storage server with your master server:
    node.sync
  11. Wait for the node.sync command to complete (roughly 1 hour).
    1. Check the progress of node.sync by viewing logs (com.backup42.app.log) in one of two ways:
      • View logs in the administration console at Settings> Server > System Logs.
      • View logs on your enterprise server using a command line utility, such as tail:
        • Linux: /var/log/proserver
          Applies to Code42 servers installed as root on Ubuntu
        • Windows: C:\Program Files\CrashPlan PROe Server\logs
        • OS X: /Library/Logs/PROServer
    2. Watch the log for text including SYNCHRONIZE:: Sync complete
      Example:
      [06.13.14 10:54:22.018 INFO BWQ-NodeSyncService: com.code42.server.sync.NodeSyncEndCmd ] SYNCHRONIZE:: Sync complete at 2014-06-13T10:54:22:000
      
  12. Enter this command to restart your storage server after the node.sync command has completed:
    node.restart
    The storage server restarts.
  13. Verify the following:
    • You are able to sign in to the storage server's administration console.
    • Under Settings > Server, the Current server version is 4.2.3.1.
    • Your devices are able to reconnect.
    • You are able to back up and restore, or sync and share, files from your devices.
  14. (Syslog only) If your storage server was configured to send logs to a syslog server, place the configuration file that you backed up in its original location, then restart the storage server.

Step 6: Upgrade your devices

  1. After the enterprise server upgrades are complete, test the CrashPlan app or SharePlan app upgrade for one existing device:
    1. In the master server's 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:
    • Launch the CrashPlan app or SharePlan app on the device and verify the version number.
    • Confirm that you are able to back up or sync 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 7: 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.1.6.3 To Version 4.2.3.1. If you need further assistance troubleshooting the upgrade, contact our Customer Champions.