Skip to main content
Code42 Support

Upgrade 3.2.1.1 to 3.2.1.2

Applies to:
  • CrashPlan PROe

Overview

The upgrade from 3.2.1.1 to 3.2.1.2 is a server-side upgrade only. There is no associated CrashPlan app upgrade. View 3.2.1.2 release notes.

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 apps can connect to your master server on TCP 4280 for download of client upgrade files.
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.

Version compatibility

The upgrade from 3.2.1.1 to 3.2.1.2 is enterprise server upgrade only. View 3.2.1.2 release notes.

enterprise server version 3.2.1.2 is compatible with CrashPlan app version 3.2.1.

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

We always recommend testing the upgrade before deploying to your production environment. Please follow the steps below to perform a test 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. The upgrade test requires one test machine or VM.

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 Code42 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 Code42 apps and storage servers.

Test the Enterprise Server upgrade

  1. Install enterprise server version 3.2.1.1 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 point, disable Accept New Devices.
  4. Create a new store point on your test enterprise server.
  5. Install PROe Client version 3.2.1 on the same test enterprise server.
    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 the built in authentication.
  7. Back up a small amount of data to the test enterprise server.
  8. Download the upgrade file for your platform.
  9. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade to apply the enterprise server upgrade.

Verify the test server upgrade

After the upgrade completes:

  • You are able to sign into the test master server's administration console.
  • 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 CrashPlan app is connected to the test master server.
  • You are able to back up and restore files from the test CrashPlan app.

Multi-server environments

If you have a multi-server CrashPlan PROe environment, please follow these steps to test your enterprise server upgrade. The upgrade test requires two test machines or VMs and a fully closed, private network.

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 Code42 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 Code42 apps and storage servers.

Test the Enterprise Server upgrade

  1. Install enterprise server version 3.2.1.1 on the two test machines.
  2. Import the database dump created in Step 2 above into your test master server.
  3. On your test master server:
    1. Confirm that the primary and secondary network addresses of your master server work on the private network. They should work if you followed the steps in the section above.
    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 enterprise server, import the database you dumped in Step 2 above for your storage server.
  5. Verify that the test enterprise servers are able to communicate. From the master server's 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.2.1 on one of the test enterprise servers.
    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 Code42 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 enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade to apply the enterprise server upgrade.
  12. Repeat steps 13 & 14 to upgrade your test storage server.

Verify the server upgrade test

After the upgrade completes, clear your browser cache and sign in to the master server's administration console to verify the upgrade test. Verify the following:

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

What's next?

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 our Customer Champions for Code42 for Enterprise support or CrashPlan for Small Business (previously CrashPlan PRO) support:

3.2.1.1 installers

Upgrading your production environment

1. prepare your production environment

  1. Review the Licensing screen to verify that your support license is current.
  2. Dump your master server's database from Settings > Server > Action Menu > Dump Database.

2. upgrade your servers

  1. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  2. (For multi-server environments) Repeat steps 2-5 on each of your Storage servers to upgrade your Storage server(s).
  3. After the server restart completes, clear your browser's cache and sign in to the console.
  4. Verify the following:
    • You are able to sign in to the master server's admin console.
    • Under Settings > Server, the current version number is 3.2.1.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.
    • (For multi-server environments) Your Storage servers are online and connected to the Master server.
    • Your PROe Client devices are able to reconnect to the master server.
    • You are able to back up and restore files from a PROe Client device.

Upgrade files

Troubleshooting

What if the enterprise server 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 our Customer Champions at Code42 for Enterprise support or CrashPlan for Small Business support:

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

  • Was this article helpful?