Skip to main content
Code42 Support

Upgrade PROe Version 3.5.3.2 to 3.5.4

Applies to:
  • CrashPlan PROe

Overview

This tutorial describes how to upgrade your Code42 environment from enterprise server version 3.5.3.2 to enterprise server version 3.5.4. It is a server only upgrade.

Before You Begin

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

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.3.2 to 3.5.4 is a Code42 environment-only upgrade. View 3.5.4 release notes.

Note: These instructions cover version 3.5.3.2 to 3.5.4 only. If you are upgrading from 3.5.3, please see the 3.5.3 to 3.5.4 upgrade instructions.

Enterprise server version 3.5.4 is compatible with:

  • CrashPlan app versions 3.5.3, 3.5.2 and 3.4.1
  • CrashPlan mobile app versions:
    • Android: 3.5.4, 3.4.1.1
    • iOS: 3.5.4, 3.4.0
    • Windows Phone: 3.5.4, 3.3.4.0

What To Expect

When you apply the upgrade, the enterprise server service shuts down and performs the upgrade tasks. When the upgrade tasks are complete, the enterprise 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.

Testing The Upgrade

Single Server Environments

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

Prepare The Enterprise Server

  1. Write down the current primary and secondary network addresses from the production enterprise server's administration console.
  2. On your production enterprise server, dump the database.
  3. Disconnect your test enterprise server from your production network.
    This is to prevent your test enterprise server from interacting with devices or sending alert emails to users or administrators.
  4. If the primary network address of the production enterprise server is an IP address, then you must set the IP address of the test machine to the same value. It is therefore critical that you completely disconnect the test machine from your production network, as suggested above, to prevent the test machine from interacting with any CrashPlan apps or storage servers.
  5. If the primary network address is a hostname rather than an IP address, you must edit the hosts file on your test machine so that the hostname entered as the primary network address in the administration console points to the IP address of the test machine:
    • An example entry might read :
      • myserver.example.com    192.0.2.101
    • As an alternative, you may change the IP address of the test machine to be identical to the IP address of the production enterprise server. As already stated, it is important to isolate the test machine from your production network, to prevent the test machine from interacting with CrashPlan apps and storage servers.

Test The Enterprise Server Upgrade

  1. Install PROe Server version 3.5.3.2 on the test machine.
  2. Import the database dump created in Step 1 into your test master server.
  3. On your test enterprise server's existing store points, disable Accept New Devices.
  4. Create a new store point on your test enterprise server.
  5. Install PROe Client version 3.5.3 on the same test machine.
    Customized CrashPlan app installers should not be used for the upgrade test.
  6. Once the CrashPlan app's installation completes, register the CrashPlan app under a new user account.
    If your Code42 environment uses LDAP or SSO to authenticate users, register the user in an org that uses built in authentication.
  7. Back up a small amount of data to test the enterprise server.
  8. From the test enterprise server's administration console, apply the Code42 environment upgrade.
    The Code42 environment restarts after successfully upgrading.
  9. After the upgrade completes, clear your browser cache and sign into the administration console.
  10. Verify the following:
    • You are able to sign into the test master server's administration console.
    • Under Settings > Server, the enterprise server's current version number is 3.5.4.
    • 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 CrashPlan app is connected to the test master server.
    • You are able to back up and restore files from the test CrashPlan app.
 

If the upgrade test passes all verification steps, then proceed with upgrading your production Code42 environment.

If any verification steps fail during the upgrade test, cease further upgrade operations. Please send the following information to Customer Champions for assistance:

Multi-Server Environments

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

Prepare The Enterprise Servers

Complete the following steps for your master server and for one of your storage servers:

  1. Write down the current primary and secondary network addresses from the production enterprise server's administration console.
  2. On your production enterprise server, dump the database.
  3. Disconnect your test enterprise server from your production network.
    This is to prevent your test enterprise server from interacting with devices or sending alert emails to users or administrators.
  4. If the primary network address of the production enterprise server is an IP address, then you must set the IP address of the test machine to the same value. It is therefore critical that you completely disconnect the test machine from your production network, as suggested above, to prevent the test machine from interacting with any CrashPlan apps or storage servers.
  5. If the primary network address is a hostname rather than an IP address, you must edit the hosts file on your test machine so that the hostname entered as the primary network address in the administration console points to the IP address of the test machine:
    • An example entry might read :
      • myserver.example.com    192.0.2.101
    • As an alternative, you may change the IP address of the test machine to be identical to the IP address of the production enterprise server. As already stated, it is important to isolate the test machine from your production network, to prevent the test machine from interacting with CrashPlan apps and storage servers.

Test The Enterprise Server Upgrade

  1. Install PROe Server version 3.5.3.2 on two test machines.
  2. Import the database dump created in Step 1 into your test master server.
  3. 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 enterprise server.
    4. Change the Primary and Secondary network addresses of your test storage server to work on the private network.
  4. On the second test machine, import the database for your storage server.
  5. Verify that the test enterprise servers are able to communicate. From the master servers administration console, go to Destinations > Servers. The test storage server's status should be online.
  6. (For LDAP or SSO environments only) Create a test org that does not use LDAP authentication.
    For testing CrashPlan app backup, restore and upgrade without connectivity to the LDAP server.
  7. Install PROe Client version 3.5.3 on one of the test machines.
    Customized CrashPlan app installers should not be used for the upgrade test.
  8. Once the CrashPlan app's installation completes, register the CrashPlan app under a new user account.
    If your environment uses LDAP or SSO to authenticate users, register the user in an org that uses built in authentication.
  9. Verify that the test CrashPlan app is connected to the test master server.
  10. Back up a small amount of data to the test enterprise server.
  11. From the test master server's administration console, apply the enterprise server upgrade.
  12. If automatic server upgrades are disabled in your Code42 environment, you must manually apply the upgrade to the test storage server.
  13. After the upgrade completes, clear your browser cache and sign into the master server's administration console to verify the upgrade test.
 

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

  • You are able to sign into the test master server's administration console.
  • Under Settings > Server, the enterprise server's current version number is 3.5.4.
  • 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 CrashPlan app is connected to the test master server.
  • You are able to back up and restore files from the test CrashPlan app.
 

Upgrading Your Production Environment

Steps

  1. Verify your Code42 environment is still under support from the Licensing screen.
  2. Dump your master server's database from Settings > Server > Action Menu > Dump Database.
  3. Download the upgrade file(s) for your PROe Server platform(s).
  4. For multi-server environments with automatic storage server upgrades enabled:
    The automatic storage server upgrade occurs only for storage server on the same platform as the master server. In mixed platform Code42 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
  5. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
    The enterprise server restarts after successfully upgrading.
  6. After the enterprise server restart completes, clear your browser's cache and sign into the administration console.
  7. Verify the following:
    • You are able to sign into the master server's administration console.
    • Under Settings > Server, the enterprise server's current version number is 3.5.4.
    • 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 CrashPlan app devices are able to reconnect to the master server.
    • You are able to back up and restore files from a CrashPlan app device.

Upgrade Files

MD5 checksums

Troubleshooting

What if the upgrade fails?

First, your enterprise server is ok. The internal database is protected during upgrades which allows us to restore the enterprise 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.