Skip to main content
Code42 Support

Upgrade your multi-server Code42 environment

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

This tutorial describes how to upgrade your multi-server Code42 environment to a new Code42 server version.

For single-server environments, see Upgrading Your Single-Server Code42 Environment.

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.

Considerations

  • When you apply the upgrade, the Code42 server service shuts down and performs the upgrade tasks. When the upgrade tasks are complete, the Code42 server service starts up automatically.
  • Most Code42 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.

Before you begin

To avoid security risks, keep your operating system updated.

  1. Download the upgrade files for your host server's operating system:
    1. Find the upgrade instructions for your version.
    2. Near the bottom of the instructions, locate and click the appropriate download link.
  2. From the administration console Licensing screen, verify that your Code42 environment licenses are valid and up-to-date.
  3. Make sure that your host server meets the Code42 server requirements.
Test the upgrade
We strongly recommend that you perform the following upgrade steps in a test Code42 environment before upgrading your production Code42 environment.

Step 1: Prepare your Code42 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.

Step 2: 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 on the master server, storage servers are automatically upgraded after the master server is upgraded.

Automatic Storage Server upgrades
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 downtime, 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 a different operating system than your master server, place the upgrade file(s) for each host server's 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 3: 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 select 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 to ensure that you access the new version of the administration console the next time you connect.
  7. After the master server restarts, sign in to the administration console.
    The message Server Upgrade Complete appears.
  8. When prompted, click No, I'll Upgrade Later to postpone upgrading all client devices.
  9. Verify the following:
    • Under Settings > Server, the Current server version displays the new Code42 server version.
    • You are able to view the details of any organization, any user, and any device.
    • User devices are able to reconnect, back up, and restore.

Step 4: 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 to ensure that you access the new version of the administration console the next time you connect.
  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 match the new Code42 server version.
  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 Code42 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. After the node.sync command is complete, enter this command from the administration console command-line interface to restart your storage server:
    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 displays the new Code42 server version.
    • User devices are able to reconnect, back up, and restore.

Next steps

If the new Code42 server version introduced a new Code42 app version, upgrade the CrashPlan devices in your Code42 environment.

Troubleshooting the upgrade

Authority server does not successfully upgrade

If your authority server upgrade fails, your authority server is still recoverable. The internal database is protected during upgrades, which allows our Customer Champions to restore the server to working order.

As soon you notice a problem, stop upgrading immediately and contact our Customer Champions for Code42 for Enterprise support.

Error: Invalid_file or unable to read properties

If the administration console or log viewer displays the following error message after attempting to upgrade your Code42 server, there are several possible causes.

Error processing upgrade: INVALID_FILE - Unable to read properties,
file=/Applications/PROServer.app/Contents/Resources/Java/upgrade/1386428616401/upgrade.properties

Cause: Invalid upgrade file

One common cause is using an invalid upgrade file, such as:

  • Using a corrupt upgrade file
  • Using an upgrade file for the wrong version
  • Using an installation file instead of an upgrade file

To resolve this error:

  1. Stop the Code42 server service.
  2. Navigate to the Code42 server /upgrade folder on your file system:
    • 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
  3. Remove all files from the /upgrade folder.
  4. Start the Code42 server service.
  5. Download the upgrade file (not an installation file):
    1. Find the upgrade instructions for your version.
    2. Near the bottom of the instructions, locate and click the appropriate download link.
  6. Apply the upgrade as described in the upgrade instructions above.

Cause: Insufficient space on a Code42 server

Another common cause is a Code42 server running low on storage space.

To resolve this error:

  1. From the administration console, check the available storage space on your Code42 server(s).
  2. If possible, add storage space or reclaim storage space in use.

Error during upgrade file upload

This issue can occur when upgrading a Code42 server to version 5.1.1 or earlier.

If the upgrade file does not finish uploading to the Code42 server within 30 minutes, the administration console authorization token expires, causing the upload to fail. An expired token can cause either of the following behaviors:

  • During the upload, the following error appears:
    "Error processing upgrade: INVALID_TOKEN - Expired token"
  • When you accept the End User License Agreement, a "System error" message briefly appears in the lower left corner of the administration console before you are signed out.

If you encounter this issue, temporarily increase the authorization token limit from 30 minutes to 90 minutes:

  1. Double-click the Code42 logo in the upper left corner of the administration console to open the command-line interface (CLI).
  2. Enter the following command to increase the timeout value to 5,400,000 milliseconds (90 minutes):
    prop.set c42.auth.token.timeout 5400000

When the Code42 server restarts to perform the upgrade, the authorization token limit resets to 30 minutes.

Administration console inaccessible after upgrade

Windows-based Code42 servers version 5.3.x and earlier only

In certain circumstances, the administration console may be inaccessible after a Windows Code42 server is upgraded. This issue occurs when necessary files are locked by the operating system during the upgrade process, and is most commonly experienced on Windows servers that do not meet the system requirements for Code42 servers. The upgrade will succeed when Windows releases the locked files.

To resolve the issue, attempt the upgrade again on the affected Code42 server:

  1. Uninstall the newer version of the Code42 server.
  2. Install the older version of the Code42 server.
  3. Import the database dump you made before attempting the upgrade.
  4. Perform the upgrade to the newer version of the Code42 server.