Skip to main content

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise

Incydr, no.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, no.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Upgrade your multi-server Code42 environment

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise

Incydr, no.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, no.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

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.

Managed authority server upgrades
If your authority server is managed or monitored by Code42, our Customer Champions work with you to upgrade your Code42 environment. Do not attempt to upgrade your environment on your own.

Considerations

  • When you apply the upgrade, the Code42 server service shuts down and performs the upgrade tasks. When the upgrade tasks are complete, the Code42 server service starts up automatically.
  • Most Code42 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.

Before you begin

To avoid security risks, keep your operating system updated.

  1. 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.
  2. From the Code42 console Subscriptions screen, verify that your Code42 environment licenses are valid and up-to-date.
  3. Make sure that your host server meets the Code42 server requirements.
Test the upgrade
We strongly recommend that you perform the following upgrade steps in a test Code42 environment before upgrading your production Code42 environment.

Step 1: Prepare your Code42 environment

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

H2 database steps 

  1. Sign in to your Code42 console for each Code42 server you need to upgrade.
  2. Dump your Code42 server's database: 
    1. Navigate to Administration > Settings > Server.
    2. From the action menu, select Dump Database.
  3. 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).
  4. In the Code42 console on the authority server, go to Administration > Settings > Server, then disable Auto-upgrade devices.

PostgreSQL database steps 

  1. Back up your database through PostgreSQL
  2. 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.
  3. Sign in to the Code42 console on the authority server.
  4. In Administration > 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:

  1. Sign in to the Code42 console on your authority server.
  2. Go to Administration > Settings > Server.
  3. Enable or disable Auto-upgrade storage servers, then click Save.
  4. 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

  1. Sign in to the Code42 console of your authority server.
  2. Navigate to Administration > Settings > Server.
  3. From the action menu, select Upgrade.
  4. 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).
  5. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The authority server restarts after successfully upgrading.
  6. Clear your browser cache to ensure that you access the new version of the Code42 console the next time you connect.
  7. After the authority server restarts, sign in to the Code42 console.
    The message Server Upgrade Complete appears.
  8. When prompted, click No, I'll Upgrade Later to postpone upgrading all client devices.
  9. Verify the following:
    • Under Administration 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. 

Authority servers and storage servers require separate upgrade files
Beginning in Code42 server version 8.2.6, there are separate upgrade files for authority servers and storage servers. You must download the correct upgrade file for each Code42 server. Accidentally applying the authority server upgrade file to a storage server results in an error and requires you to uninstall and reinstall the storage server.
  1. Sign in to the Code42 console on your storage server.
  2. Navigate to Administration > Settings > Server.
  3. From the action menu, select Upgrade.
  4. Locate and upload the upgrade file:
    • Version 8.2.6 or later
      There are separate authority server and storage server upgrade files. Select the storage server upgrade file for your operating system (Windows or Linux). If you select the authority server upgrade file by mistake, it can disable the storage server. To correct the problem, see Storage server becomes an authority server after upgrade below.  
    • Version 7.0.5 and earlier
      There is a single upgrade file. Select the upgrade file for your operating system (Windows or Linux).
  5. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The storage server restarts after successfully upgrading.
  6. Clear your browser cache to ensure that you access the new version of the Code42 console the next time you connect.
  7. After the storage server restarts, sign in to the Code42 console.
  8. Double-click the Code42 logo in the upper left to access the Code42 console command-line interface.
  9. 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.
  10. Enter this command to sync your storage server with your authority server:
    node.sync
    
  11. 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
      
  12. 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.
  13. Verify the following:
    • You are able to sign in to the storage server's Code42 console.
    • Under Administration > Settings > Server, the Current server version displays the new Code42 server version.
    • User devices are able to reconnect, back up, and restore.

Next steps

If the new Code42 server version introduced a new Code42 app version, upgrade the Code42 apps in your Code42 environment.

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:

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

  1. From the Code42 console, check the available storage space on your Code42 server(s).
  2. 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 version 7.0.5 or earlier.

Problem

When you navigate to Administration > 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

Recommended solution

Instead of performing a manual upgrade, auto-upgrade the storage servers:

  1. Sign in to the Code42 console on your authority server.
  2. Go to Administration > Settings > Server.
  3. Select Auto-upgrade storage servers
  4. Click Save.
  5. Restart the storage servers to start the upgrade right away.

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.

Storage server becomes an authority server after upgrade

This problem occurs when accidentally using the authority server upgrade file to manually upgrade a storage server.

Problem

If you upload the authority server upgrade file instead of the storage server upgrade file, the storage server is converted to an authority server after the upgrade. When you view the storage server in the Code42 console, you see that the server settings displayed are for an authority server instead of a storage server. Review upgrade logs to see the storage server conversion to an authority server. 

Solution

For every affected storage server, uninstall the storage server and reinstall it:

  1. Ensure that your authority server is already upgraded to version 8.2.6 or later.
  2. Uninstall the storage server using the same version software as your authority server.
  3. Reinstall the storage server using the the same version software as your authority server.
  4. Sync the storage server with the authority server:
    1. Sign in to the Code42 console on the storage server.
    2. Double-click the logo in the upper-left corner of the Code42 console.
      The Code42 console command-line interface appears.
    3. Enter the commandnode.sync 
      The storage server synchronizes with the authority server.

If you are still experiencing problems, contact our Customer Champions for support.

  • Was this article helpful?