Upgrade your multi-server Code42 environment
Who is this article for?
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.
Considerations
Before you begin
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: 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 console for each Code42 server you need to upgrade.
- Dump your Code42 server's database:
- Navigate to Administration > Settings > Server.
- From the action menu, select Dump Database.
- Verify that the database dump was successful:
- From the action menu, select Import Database.
You see a list of dump files identified by timestamps in their filenames. - 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.
- When the new dump file is present, click Cancel (not Submit).
- From the action menu, select Import Database.
- In the Code42 console on the authority server, go to Administration > 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 the Code42 console on the authority server.
- 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.
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 Administration > 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
- Linux: /opt/proserver/upgrade
Step 3: Upgrade your authority server
- Sign in to the Code42 console of your authority server.
- Navigate to Administration > 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).
- Version 8.2.6 or later
- 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 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.
- Sign in to the Code42 console on your storage server.
- Navigate to Administration > Settings > Server.
- From the action menu, select Upgrade.
- 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).
- Version 8.2.6 or later
- 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).- 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
- Linux: /var/log/proserver
- 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
- Check the progress of
- 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 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
Troubleshooting the upgrade
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.
Recommended solution
Instead of performing a manual upgrade, auto-upgrade the storage servers:
- Sign in to the Code42 console on your authority server.
- Go to Administration > Settings > Server.
- Select Auto-upgrade storage servers.
- Click Save.
- 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:
- Ensure that your authority server is already upgraded to version 8.2.6 or later.
- Uninstall the storage server using the same version software as your authority server.
- Reinstall the storage server using the the same version software as your authority server.
- Sync the storage server with the authority server:
- Sign in to the Code42 console on the storage server.
- Double-click the logo in the upper-left corner of the Code42 console.
The Code42 console command-line interface appears. - Enter the command:
node.sync
The storage server synchronizes with the authority server.
If you are still experiencing problems, contact our Customer Champions for support.