Skip to main content
Code42 Support

Upgrade PROe Version 3.5.1.x to 3.5.3.2

Applies to:
  • CrashPlan PROe

Overview

This tutorial describes how to upgrade your Code42 environment from enterprise server version 3.5.1.x to version 3.5.3.2.

Before you begin

  1. Verify that your support is up to date from the console's Licensing screen.
    Only environments under current support and maintenance are able to upgrade.
  2. Test the software upgrade before upgrading your production environment.
  3. Always dump your PROe Server database(s) before attempting to upgrade.
  4. Verify that your PROe Client devices can connect to your Master server on TCP 4280 for download of client upgrade files.

Proe managed appliance customers

Managed appliance Upgrades
If your master 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.

Version compatibility

The upgrade from 3.5.1.x to 3.5.3.2 is a PROe Client and PROe Server upgrade. View 3.5.3 and 3.5.2 release notes.

PROe Server version 3.5.3.2 is compatible with:

  • PROe Client versions 3.5.3, 3.5.2 and 3.4.1
  • PROe Mobile versions:
    • Android: 3.4.1.1
    • iOS: 3.4.0
    • Windows Phone: 3.3.4.0

There is no upgrade path from PROe Server version 3.5.3 to 3.5.3.2. View 3.5.3.2 release notes for additional details.

What to expect

When you apply the upgrade, the PROe Server service shuts down and performs the upgrade tasks. When the upgrade tasks are complete, the PROe Server service starts up automatically.

Upgrade the Master server first. Most 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 and the nature of the specific upgrade.

Proe client upgrades

Devices with the CrashPlan app upgrade automatically once the administrator enables the device upgrade. We recommend running the upgrade on a single CrashPlan app device before enabling automatic upgrades for all of your devices. Please review Best Practices for Upgrading Your Devices prior to upgrading.

Once you enable device auto-upgrade, you must restart your master server before your devices can upgrade. When the master server has restarted, devices reconnect to the upgraded master server at a randomized interval of 1-15 minutes. Devices download their upgrades from the master server over TCP port 4280 and upgrade themselves automatically. The randomized re-connect interval means that, after the master server comes back online, there may be a delay before all devices have successfully upgraded.

Performing sequential upgrades

When performing multiple upgrades in sequence, we recommend that you allow time for devices to complete one upgrade before beginning a later upgrade.

Testing the upgrade

Single server environments

If you have a single CrashPlan PROe Server in your environment, please follow these steps to test your PROe Server and PROe Client upgrades. You'll need one test machine or VM to complete the upgrade test.

  1. On your production Master server, dump the database.
  2. On your test machine, completely disconnect from any network connectivity.
    This is to prevent your test server from sending alert emails to users or administrators.
  3. Install PROe Server version 3.5.1.1 on the test machine.
  4. Import the database dump created in Step 1 into your test Master server.
  5. On your test server's existing store points, disable Accept New Devices.
  6. Create a new store point on your test server.
  7. Install PROe Client (same version as your production environment) on the same test machine.
    Customized PROe Client installers should not be used for the upgrade test.
  8. Once the PROe Client's installation completes, register the PROe Client under a new user account.
    If your environment uses LDAP or SSO to authenticate users, register the user in an org that uses CrashPlan PROe's built in authentication.
  9. Back up a small amount of data to the test PROe Server.
  10. From the test PROe Server's admin console, apply the PROe Server upgrade.
  11. The PROe Server restarts after successfully upgrading and asks if you want to upgrade all of your PROe Clients now or later. Click No, upgrade later.
  12. Verify the following:
    • You are able to sign into the test Master's admin console.
    • Under Settings > Server, the PROe Server's current version number is 3.5.3.2.
    • You are able to view the details of an org, a user and a device. You can also do spot checks of various configuration screens if you'd like, but verifying an org, user and device's details provides good coverage.
    • Your test PROe Client is connected to the test Master.
  13. Once you've verified the PROe Server upgrade, initiate the PROe Client upgrade for your test device:
    1. Navigate to the test device's Device Details pane.
    2. From the Action Menu, select Upgrade.
    3. Confirm that you are ready to upgrade your test device.
      The upgrade command is sent to the device immediately and the device begins the upgrade process.
  14. Verify the PROe Client upgrade:
    • The console displays a “success” message in the lower left corner.
    • Launch the PROe Client and go to Settings > Account to verify that the version number is 3.5.3.
    • You are able to back up and restore files from the test PROe Client.
If the upgrade test passes all verification steps, then proceed with upgrading your production environment.
If any verification steps fail during the upgrade test, cease further upgrade operations. Please send the following information to support for assistance:
  • Archive of PROe Server log files, including the upgrade log
  • Archive of PROe Client log files
  • Copy of the database dump created in step 1

Multi-server environments

If you have a multi-server CrashPlan PROe environment, please follow these steps to test your PROe Server upgrade. You will need two test machines or VMs and a fully closed, private network to complete the test.

  1. On your production Master server, dump the database.
  2. Choose one of your storage servers to use in the upgrade test. Dump the database of the chosen production Storage server.
  3. Set up a closed, private network with no outside connectivity.
    This is to prevent your test servers from sending alert emails to users or administrators.
  4. Install PROe Server (your current production version) on two test machines.
  5. Import the database dump created in Step 1 into your test Master server.
  6. On your test Master server:
    1. Change the Primary and Secondary network addresses of your Master server to work on the private network.
    2. On existing store points, disable Accept New Devices.
    3. Create a new store point on your test server.
    4. Change the Primary and Secondary network addresses of your test Storage server to work on the private network.
  7. On the second test machine, import the database for your Storage server.
  8. Verify that the test servers are able to communicate. From the Master's admin console, go to Destinations > Servers. The test Storage server's status should be online.
  9. (For LDAP or SSO environments only) Create a test org that does not use LDAP authentication.
    For testing PROe Client backup, restore and upgrade without connectivity to the LDAP server.
  10. Install PROe Client (same version as your production environment) on one of the test machines.
    Customized PROe Client installers should not be used for the upgrade test.
  11. Once the PROe Client's installation completes, register the PROe Client under a new user account.
    If your environment uses LDAP or SSO to authenticate users, register the user in an org that uses CrashPlan PROe's built in authentication.
  12. Verify that the test PROe Client is connected to the test Master server.
  13. Back up a small amount of data to the test PROe Server.
  14. From the test Master PROe Server's admin console, apply the upgrade.
  15. If automatic server upgrades are disabled in your environment, you must manually apply the upgrade to the test Storage server.

To verify that the upgrade test was successful, check the following:

  • You are able to sign into the test Master's admin console.
  • Under Settings > Server, the PROe Server's current version number is 3.5.3.2.
  • You are able to view the details of an org, a user and a device. You can also do spot checks of various configuration screens if you'd like, but verifying an org, user and device's details provides good coverage.
  • The test Storage server is online and connected to the test Master server.
  • The test PROe Client is connected to the test Master server.
  • The test PROe Client successfully upgraded to version 3.5.3.
  • You are able to back up and restore files from the test PROe Client.

Upgrading your production environment

Steps

  1. Review the Best Practices article for Upgrading Your Devices.
  2. Verify your environment is still under support from the Licensing screen.
  3. Dump your Master server's database from Settings > Server > Action Menu > Dump Database.
  4. Download the upgrade file(s) for your PROe Server platform(s).
  5. For multi-server environments with automatic storage server upgrades enabled:
    The automatic storage server upgrade occurs only for storage servers on the same platform as the Master server. In mixed platform server environments, you must place the upgrade file(s) for any other storage server platforms into the following directory on the Master server:
    • Linux Master server: /opt/proserver/upgrade or /home/userName/proserver/server/upgrade
    • Mac Master server: /Applications/PROServer.app/Content/Resources/Java/upgrade
    • Windows Master server: C:\Program Files\CrashPlan\upgrade
  6. Designate an existing PROe Client to upgrade first as a test.
  7. Apply the PROe Server upgrade from Settings > Server > Action Menu > Upgrade
  8. The PROe Server restarts after successfully upgrading and asks if you want to upgrade all of your PROe Client devices now or later. Click No, I'll upgrade later.
  9. Verify the following:
    • You are able to sign into the Master's admin console.
    • Under Settings > Server, the PROe Server's current version number is 3.5.3.2.
    • You are able to view the details of an org, a user and a device. You can also do spot checks of various configuration screens if you'd like, but verifying an org, user and device's details provides good coverage.
    • Your test PROe Client is connected to the test Master.
  10. Once you've verified the PROe Server upgrade, initiate the PROe Client upgrade for the test device selected under step 7:
    1. Navigate to the test device's Device Details pane.
    2. From the Action Menu, select Upgrade.
    3. Confirm that you are ready to upgrade your test device.
      The upgrade command is sent to the device immediately and the device begins the upgrade process.
  11. Verify the PROe Client upgrade:
    • The console displays a “success” message in the lower left corner.
    • Launch the PROe Client and go to Settings > Account to verify that the version number is 3.5.3.
    • You are able to back up and restore files from the test PROe Client.
  12. When you are ready to upgrade the rest of your PROe Client devices, enable Auto-upgrade devices to upgrade all of your PROe Client devices:
    1. From the console, go to Settings > Server.
    2. Enable Auto-upgrade devices.
    3. Confirm that you'd like to upgrade all your PROe Client devices now and click OK.

Upgrade files

MD5 checksums

Troubleshooting

What if the upgrade fails?

First, your server is ok. The internal database is protected during upgrades which allows us to restore the server to working order. As soon as a problem is detected, stop what you're doing immediately. Gather the following materials and submit them to support:

Providing all of these materials at once is the fastest way to guarantee a swift resolution.

How do I verify that my devices upgraded?

The best way to verify that all your devices have upgraded is via the API. There are examples in our API documentation.

Why would a device fail to upgrade and how do I fix it?

The most common reason a device fails to upgrade is because it cannot download it's update from the server — almost always a connection issue. Please verify that your devices are able to connect to your Master server on TCP 4280. Use telnet to verify:

telnet <SERVER HOST NAME or IP> 4280

If necessary, you can review the device's service.log for the host it's attempting to use. The device attempts to download a ”.jar” file, which is a string you can search for in the log.

The device can download the jar, what's next?

Please send the device's log files to PROe Support for review. Failures to remotely upgrade are very serious and we need to understand what happened.

If you cannot wait to diagnose the problem and a small number of devices are affected, the fastest fix is to simply uninstall the PROe Client software and install the latest version.

  • Was this article helpful?