CrashPlan PRO Upgrades

Update from 3.8.2010 or 3.8.2010.1 to 3.8.2010.2

This article walks you through upgrading CrashPlan PRO to the latest version. You must be running the previous version for these instructions to work.

• Previous versions of installers

If you have an older version of CrashPlan PRO, please see Upgrade Older CrashPlan PRO Version.

1. Test the upgrade in a non-production environment.
2. Export your PRO Server database from Settings > Dump Database.
3. Make sure your firewall is open on the following ports for client download:
   • Mac, Windows, Linux, Solaris: 4280
   • VMware: 8080
4. Quit PRO Server Monitor UI, if it is running.

VMware users: Upgrade to version 11.5.2009 or newer before migrating to a native platform.

We encourage you to test the upgrade before applying. This is a simple test designed to take less than 15 minutes.

Follow these guidelines to test the upgrade:

• Install the previous version of PRO Server (11.5.2009) on a test server.
• Install a test client and connect it to the test server.
• Import your database (from the nightly database dump) into the test server.
• Apply upgrade to the test server.
• Verify that you are able to log into the PRO Server and that 3.8.2010 appears on the Home page of the admin console.

• The server on which you are testing does not know it is a test, which means it is able to send reports and notifications. If you do not want to receive them, be sure to disconnect the server from the live network.
• For master/slave configurations, testing the master is sufficient.

Choose the correct upgrade file for your PRO Server. Do not extract the downloaded file!!!

• Windows Upgrade
• VMware Upgrade
• Mac Upgrade
• Solaris Upgrade
• Linux Upgrade
• MD5 checksums

1. From the Support screen in the PRO Server Web Console, click Upgrade in the left menu.
2. Browse to the downloaded upgrade file and then click Save.
3. PRO Server begins upgrading itself.
4. Your PRO Clients upgrade themselves automatically.

Apply this upgrade only on PRO Servers running 3.8.2010 or 3.8.2010.1.

Follow these steps to perform the 3.8.2010.2 update:

1. Dump the database.
2. Quit PRO Server Monitor, if it is running.
3. Download the upgrade file.
4. Apply upgrade.
5. For 3.8.2010 only: After the update completes, dump the database again.
   Because there are database changes when going from 3.8.2010 to 3.8.2010.2, dumps created before the update can no longer be used.
6. When the update has taken affect, the Home page of the PRO Server's web admin displays version 3.8.2010.2.

NOTE: When upgrading from 3.8.2010 to 3.8.2010.2 - The Space-Used graphs in the admin console will appear empty until the nightly jobs run the next evening. This is a display issue only and has no impact on the actual storage or archives.

Read the Troubleshooting section for help.

Choose the correct upgrade file for your PRO Server. Do not extract the downloaded file!!!

• Windows Upgrade
• Linux Upgrade
• Mac Upgrade
• Solaris Upgrade

Follow these instructions only if your current version of CrashPlan PRO is 6.11.2009 or older. View server's version from Home screen.

• To bring your server fully up to date, you must apply every previous upgrade in order.
• For each upgrade, follow the instructions in Before You Begin.

Upgrading Instructions for Multi-Server Environments

• Windows Upgrade
• VMware Upgrade
• Mac Upgrade
• Solaris Upgrade
• Linux Upgrade

• Windows Upgrade
• VMware Upgrade
• Mac Upgrade
• Solaris Upgrade
• Linux Upgrade

• Windows Upgrade
• VMware Upgrade
• Mac Upgrade
• Solaris Upgrade
• Linux Upgrade

• Windows Upgrade
• VMware Upgrade
• Mac Upgrade
• Solaris Upgrade
• Linux Upgrade

• Windows Upgrade
• VMware Upgrade
• Mac Upgrade
• Linux Upgrade

Contact Support for notes before applying the upgrade.

• Mac Upgrade
• VMware Upgrade

First — your server is ok.

The internal database is protected during upgrades which allows us to restore the server to working order. As soon as a problem is detected stop what you're doing immediately. Gather these materials and submit them to support:

• Your upgrade.log. You'll find it in your main PRO Server directory at this path:

  upgrade/upgrade.log

• An archive of all normal pro server log files
• A copy of the db dump you made before attempting the upgrade OR the latest dump made before the upgrade
• A description of what was done and what you are seeing now

Providing all of these materials at once is the fastest way to guarantee a swift resolution.

Clients will connect to your new server, detect that an upgrade is required and download their update. You can view a client's current version by viewing a user's list of computers.

When it comes time to monitor the clients and make sure they're ok, the easiest way is with the report Organizations > Show All Users… sort by Last Backup. Clients that don't upgrade will quickly fall behind and come to the top of the list.

The most common problem (>95%) is an inability to download their update from the server — most likely a connection issue. Please review the appropriate client download port for your platform in the upgrade instructions and make sure the affected clients can connect on that port. Use telnet to verify.

If necessary you can review the client's service.log for the url it's attempting to use. It's trying to download a ”.jar” file, which is a string you can search for in the log.

Please send your client logs to pro support for review. Failures to remotely upgrade are very serious and we need to understand what happened.

If you cannot wait to see what happened and you're dealing with a small number of affected clients then the fastest fix is to simply reinstall using the latest version. BE SURE to not delete the computers identity during uninstall.