Upgrade your single-server Code42 environment

Overview

This article describes how to upgrade your single-server Code42 environment to a new Code42 server version.

For multi-server environments, see Upgrade your multi-server Code42 environment.

Considerations

Before you begin

To avoid security risks, keep your operating system updated.

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.
From the Code42 console Subscriptions screen, verify that your Code42 environment licenses are valid and up-to-date.
Make sure that your host server meets the Code42 server requirements.

Step 1: Prepare your Code42 environment

Before you upgrade, dump the database as a fallback in case of an upgrade problem, and disable the Auto-upgrade devices setting as a precaution to prevent devices from upgrading unintentionally. Follow the steps for your database type:

H2 database: This is the default database that's built into the authority server.
PostgreSQL database: Use this set of steps if your authority server has been configured to use an external PostgreSQL database.

H2 database steps

Sign in to your Code42 server's Code42 console.
Dump your Code42 server's database:
1. Navigate to Settings > Server.
2. From the action menu, select Dump Database.
Verify that the database dump was successful:
1. From the action menu, select Import Database.
  You see a list of dump files identified by timestamps in their filenames.
2. Find the file with the current date and time that ends in .sql.gz. This indicates that the database dump completed successfully.
  - If the file extension ends in .sql, database dumps aren’t completing successfully. Contact our Customer Champions for support. We strongly recommend that you do not upgrade your Code42 server until you have a current database dump file.
  - If you don't see a new dump file, click Cancel, wait 10 seconds and then select Import Database again.
3. When the new dump file is present, click Cancel (not Submit).
In Settings > Server, disable Auto-upgrade devices.

PostgreSQL database steps

Back up your database through PostgreSQL.
Verify that the backup completed successfully. We strongly recommend that you do not upgrade your Code42 server until you have a current database dump file.
Sign in to your Code42 server's Code42 console.
In Settings > Server, disable Auto-upgrade devices.

Step 2: Upgrade your Code42 server

Sign in to the Code42 console of your Code42 server.
Navigate to Settings > Server.
From the action menu, select Upgrade.
Locate and select the upgrade file.
- Version 8.2.6 or later
  There are separate authority server and storage server upgrade files. Select the authority server upgrade file for your operating system (Windows or Linux).
- Version 7.0.5 and earlier
  There is a single upgrade file. Select the upgrade file for your operating system (Windows or Linux).
Review the End User License Agreement and click I AGREE to proceed with the upgrade.
The Code42 server restarts.

How do I know the upgrade is complete?
Once you can access the Code42 console again, the Code42 server upgrade is complete. Depending on the size of your Code42 environment and the server version you are upgrading to, it may take an hour or more to complete a server upgrade.

Clear your browser cache to ensure that you access the new version of the Code42 console the next time you connect.
After the Code42 server restarts, sign in to the Code42 console.
The message Server Upgrade Complete appears.
When prompted, click No, I'll Upgrade Later to postpone upgrading all client devices.

Step 3 (optional): Additional ways to verify server upgrade was successful

Once you can access the Code42 console again, your server has been successfully upgraded.

However, you can also verify your Code42 server has been upgraded by checking the com_backup42_app.log.0:

Open the com_backup42_app.log.0 log, which is located in the following log directory on the host server:

Use a textual search tool (for example grep on Linux/Unix) to search for the keyword "READY".
Look for the following message to verify your Code42 server's upgrade is complete:

Code42 Enterprise Server READY

We also recommend you check 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.

Next steps

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 support.

Error: Invalid_file or unable to read properties

If the Code42 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:

Stop the Code42 server service.
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
Remove all files from the /upgrade folder.
Start the Code42 server service.
Download the upgrade file (not an installation file):
1. Find the upgrade instructions for your version.
2. Locate and click the appropriate download link.
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.