Skip to main content
Contact Support

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, no.

CrashPlan for Enterprise, no.

Code42 for Enterprise, yes.

CrashPlan for Small Business, yes.

This article applies to on-premises authority server version 3.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Upgrading Your Multi-Server Environment To Version 3.6.3.2

  1. Last updated
  2. Save as PDF

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, no.

CrashPlan for Enterprise, no.

Code42 for Enterprise, yes.

CrashPlan for Small Business, yes.

This article applies to on-premises authority server version 3.

Overview

This tutorial describes how to upgrade your multi-server environment from enterprise server version 3.6.3.1 to version 3.6.3.2.

Before you begin

  1. Review the general instructions at Upgrade Version 3.6.3.1 To 3.6.3.2.
  2. Verify that your support is up to date from the administration console Licensing screen.
    Only environments under current support and maintenance are able to upgrade.
  3. Test the software upgrade before upgrading your production environment.
  4. Always dump your enterprise server database(s) before attempting to upgrade.
  5. Verify that your devices can connect to your master server on TCP 4280 to download the CrashPlan app upgrade files.
Managed appliance Upgrades
If your master 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.

Upgrade & installation files

You can retrieve upgrade files here:

MD5 checksums

In order to prepare a test environment, you will need installation files for the previous version of CrashPlan PROe.

Test the upgrade

The upgrade test requires two test servers or VMs, two test CrashPlan app devices, and a fully closed, private network.

Test the Enterprise Servers

Set up the test Enterprise Servers

Create your test environment from your production environment with the following steps:

  1. Write down the current primary and secondary network addresses from the production enterprise server's Code42 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 CrashPlan 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 Code42 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 CrashPlan apps and storage servers.

Prepare the test Enterprise Servers and CrashPlan App devices

  1. Install enterprise server version version 3.6.3.1 on two test servers.
  2. Import the database dump created in Step 1 into your test master server.
  3. On your test master server:
    1. Change the Primary and Secondary network addresses of your master server to work on the private network.
    2. On existing store points, disable Accept New Devices.
    3. Create a new store point on your test master 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 server, import the database 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. Install CrashPlan app version 3.6.3 on one of the test clients.
    CustomizedCrashPlan app installers should not be used for the upgrade test.
  7. Once the CrashPlan app installation completes, register the device under a new user account.
    If your environment uses LDAP or SSO to authenticate users, register the user in an organization that uses built-in authentication.
  8. Verify that the test device is connected to the test master server.
  9. Back up a small amount of data to the test enterprise server.
  10. Download the appropriate upgrade file for your master server.

Upgrade the test Master Server

  1. Sign in to the administration console on your master server.
  2. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  3. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The enterprise server restarts after successfully upgrading.

Upgrade the test Storage Server

  1. Sign in to the administration console on your storage server.
  2. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  3. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The enterprise server restarts after successfully upgrading.
  4. After the server restart completes, clear your browser's cache and sign in to the console.
  5. Double-click the Code42 logo in the upper left to access the administration console command-line interface.
  6. Enter this command to confirm the upgrade was successful:
    version
    The administration console returns the current version number, 3.6.3.2.
  7. Enter this command to sync your storage server with your master server:
    node.sync
  8. 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:
    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
  9. Enter this command to restart your storage server after the node sync command has completed:
    node.restart
    The storage server restarts.

Verify the test Enterprise Server upgrade

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.6.3.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, a user, and a device provides good coverage.
  • The test storage server is online and connected to the test master server.
  • The test device is connected to the test master server.
  • You are able to back up and restore files from the test device.

Next steps

If the test in your upgrade environment passes all verification steps, then proceed with upgrading your production environment.

If any verification steps fail during the upgrade test, stop all upgrade operations. Please send the following information to our Customer Champions for assistance:

  • Archive of enterprise server log files, including the upgrade log
  • Archive of CrashPlan app log files
  • Copy of the database dump created during the test process

Perform the upgrade

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.
  3. Download the upgrade file(s) for your enterprise server platform(s).
  4. Test the upgrade as described above.
  5. If you have enabled automatic storage server upgrades:
    The automatic storage server upgrade occurs only for storage servers on the same platform as the master server. In mixed platform server environments, you must place the upgrade file(s) for any other storage server platforms into the following directory on the master server:
Operating System Location
Windows C:\Program Files\CrashPlan\upgrade
OS X /Applications/PROServer.app/Content/Resources/Java/upgrade
Linux (installed as root) /opt/proserver/upgrade
Linux (installed as user) /home/userName/proserver/server/upgrade

Upgrade your servers

Master Server

  1. Sign in to the administration console on your master server
  2. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  3. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The enterprise server restarts after successfully upgrading.
  4. Verify the following:
    • You are able to sign in to the master server's administration console.
    • Under Settings > Server, the current version number is 3.6.3.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.
    • Your CrashPlan app devices are able to reconnect.
    • You are able to back up and restore files from a CrashPlan app device.
Version Incompatibility
After upgrading your master server to version 3.6.3.2, your storage servers (on version 3.6.3.1) will be unable to connect to it until they are upgraded to version 3.6.3.2.

Storage Server

  1. Sign in to the administration console on your storage server.
  2. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  3. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The enterprise server restarts after successfully upgrading.
  4. After the server restart completes, clear your browser's cache and sign in to the administration console.
  5. Double-click the Code42 logo in the upper left to access the administration console command-line interface.
  6. Enter this command to confirm the upgrade was successful:
    version
    The administration console returns the current version number, 3.6.3.2.
  7. Enter this command to sync your storage server with your master server:
    node.sync
  8. 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:
    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
  9. Enter this command to restart your storage server after the node sync command has completed:
    node.restart
    The storage server restarts.
  10. Verify the following:
    • You are able to sign in to the storage server's administration console.
    • Under Settings > Server, the current server version is 3.6.3.2.
    • Your CrashPlan app devices are able to reconnect.
    • You are able to back up and restore files from a CrashPlan app device.

Troubleshooting the upgrade

For information on resolving upgrade issues, read the full article at Troubleshooting The Upgrade To Version 3.6.3.2.