Upgrade your multi-server Code42 environment

Overview

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

For single-server environments, see Upgrade your single-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 authority server's Code42 console.
Dump your authority 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 the authority server Code42 console, go to Settings > Server, then 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: 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 authority server, storage servers are automatically upgraded after the authority 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:

Sign in to the Code42 console on your authority server.
Go to Settings > Server.
Enable or disable Auto-upgrade storage servers, then click Save.
If you enabled Auto-upgrade storage servers and one or more of your storage servers are running on a different operating system than your authority server, place the upgrade file(s) for each host server's operating system in the appropriate directory on the authority server:
- Linux: /opt/proserver/upgrade
  Applies to Code42 servers installed as root on Ubuntu
- Windows: C:\Program Files\CrashPlan PROe Server\upgrade

Step 3: Upgrade your authority server

Sign in to the Code42 console of your authority server.
Navigate to Settings > Server.
From the action menu, select Upgrade.
Locate and select the upgrade file.
Review the End User License Agreement and click I AGREE to proceed with the upgrade.
The authority server restarts after successfully upgrading.
Clear your browser cache to ensure that you access the new version of the Code42 console the next time you connect.
After the authority 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.
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.

Upgrade storage servers to version 8.2.5 or later
Do not use these manual steps to upgrade storage servers to version 8.2.5 or later. Instead, we recommend you upgrade storage servers using automatic upgrade.

When upgrading storage servers to version 8.2.5 or later from storage servers version 7.0.5 or earlier, you must enable Auto-upgrade storage servers as described in Step 2 above and allow storage servers to auto-upgrade. If you do not, and instead attempt to perform a manual storage server upgrade using the following steps, you will encounter an error. For more information, see the Storage server is not accessible section below.

For each storage server in your Code42 environment:

Sign in to the Code42 console on your storage server.
Navigate to Settings > Server.
From the action menu, select Upgrade.
Locate and upload the upgrade file.
Review the End User License Agreement and click I AGREE to proceed with the upgrade.
The storage server restarts after successfully upgrading.
Clear your browser cache to ensure that you access the new version of the Code42 console the next time you connect.
After the storage server restarts, sign in to the Code42 console.
Double-click the Code42 logo in the upper left to access the Code42 console command-line interface.
Enter this command to confirm the upgrade was successful:
```
version
```
The Code42 console returns the current version number, which should match the new Code42 server version.
Enter this command to sync your storage server with your authority server:
```
node.sync
```
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 Code42 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
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
```
After the node.sync command is complete, enter this command from the Code42 console command-line interface to restart your storage server:
```
node.restart
```
The storage server restarts.
Verify the following:
- You are able to sign in to the storage server's Code42 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

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.

To resolve this error:

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

Storage server is not accessible

This problem occurs when performing a manual upgrade of your storage servers to version 8.2.5 or later from storage servers version 7.0.5 or earlier.

Problem

When you navigate to Settings > Server and select the action menu, the Upgrade option is grayed-out.

You also find that if you go to a storage server details page, a banner at the top states the storage server is not accessible.

This server is not accessible message

Alternative solution

Access the Code42 console command-line interface on the authority server and execute the node.upgrade guid=<GUID> CLI command for each storage server. To obtain the GUID for each storage server, go to the storage server details page and see the number that appears below the storage server name.