Skip to main content
Code42 Support

Upgrade 3.8.2010.2 To 3.6.1.5

Applies to:
  • CrashPlan PROe

Overview

This tutorial explains how to upgrade your Code42 environment from version 3.8.2010.2 to enterprise server version 3.6.1.5 and CrashPlan app version 3.6.1.4. There are major changes and additions when upgrading from version 3.8.2010.2 to version 3.6.1.5. Changes are documented in the release notes for versions 3.2.1.x, 3.3.x3.4.1.x, 3.5, 3.5.2, 3.5.3, 3.5.4, 3.5.5, and 3.6.1.x.

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.

Before You Begin

Considerations

There are significant changes to the enterprise server between version 3.8.2010.2 and version 3.6.1.5, including changes to the system requirements beginning with version 3.4.1.5. Before you upgrade, check the minimum system requirements and additional notes for version 3.4.1.5.

The Upgrade Process 
The upgrade to version 3.6.1.5 from version 3.8.2010.2 is extremely complex:

  • To avoid the significant labor required to upgrade, Code42 recommends starting with a new environment by performing a fresh installation of version 3.6.1.5. Note that your existing backups and configurations cannot be carried over to a new installation.
  • Please contact our Customer Champions before attempting this upgrade.
  • It is imperative that you read this entire document before attempting to upgrade, and that you follow all instructions exactly.
  • Upgrading to 3.6.1.5 from 3.8.2010.2 requires a significant time commitment. Our PRO engineers take an average of 12 hours or more to complete this process. It is important that you do not underestimate the time required to upgrade.

Upgrading To Current Version

If you plan to upgrade from 3.8.2010.2 to the current version:

  • Perform all incremental upgrades in succession. It is very important that you schedule enough time to upgrade to version 3.6.1.5 within a single day.
  • Delete the upgrade files from your server(s) between upgrade steps. The upgrade files are not automatically removed following the upgrade and you can fill your server's disk if you are performing a large number of upgrades in succession. Upgrade files are located at:
    • Linux/Solaris (default): 
      /opt/proserver/server/upgrade
    • Windows: 
      C:\Program Files CrashPlan PROe Server\Upgrade
    • Mac: 
      /Applications/ PROServer.app/ Contents/Resources/Java/Upgrade
  • Be aware of a change in CrashPlan PROe's licensing rules when upgrading from 3.4.1.5 to 3.5.1.1. Please review information in the 3.4.1.5 to 3.5.1.1 upgrade instructions and the 2013 Licensing FAQs prior to beginning any upgrades to avoid any licensing-related disruptions in service.

Increased Load During Upgrade

The CrashPlan app upgrade process temporarily increases the load on the network and the master server.

For environments with > 1000 users, we recommend increasing the Java memory available to the enterprise server process on all your enterprise servers prior to upgrading. We recommend increasing Java memory to 3.5 GB or more, but do not set Java memory to greater than 50 percent of the total RAM available.

  1. Stop enterprise server(s)
  2. Navigate to the enterprise server's <main application>/bin directory
  3. Open the file proserver in a plain text editor (e.g. Notepad, Notepad++, TextMate, TextWrangler, vi, emacs, nano, pico), with admin privileges.
  4. Find the following line:
    JAVA_OPTS="-Dapp=CPServer -server -XX:+UseAdaptiveGCBoundary -XX:PermSize=256m -XX:MaxPermSize=256m -Xss128k -Dnetworkaddress.cache.ttl=300 -Ddrools.compiler=JANINO -Dfile.encoding=UTF-8 -Xms256m -Xmx1024m"
    
  5. Update to:
    JAVA_OPTS="-Dapp=CPServer -server -XX:+UseAdaptiveGCBoundary -XX:PermSize=256m -XX:MaxPermSize=256m -Xss256k -Dnetworkaddress.cache.ttl=300 -Ddrools.compiler=JANINO -Dfile.encoding=UTF-8 -Xms256m -Xmx3584m"
    
  6. Start enterprise server(s)

Virtualized Environments

If your enterprise server runs within a virtualized environment, please ensure your production VM meets the following specifications before proceeding with the upgrade:

  • < 100 devices and built-in CrashPlan authentication: 2 cores, 4 GB RAM and 20 GB Disk
  • < 500 devices: 4 cores, 8 GB RAM and 40 GB Disk
  • > 500 devices: 8 cores, 16 GB RAM and 80 GB Disk.

Custom Installers And Other Custom Configurations

Installers customized under version 3.8.2010.2 are not compatible with version 3.4.1 and later. This means that upgrades must be coordinated with installer replacement within your enterprise package management software. Existing CrashPlan app installations are unaffected and are automatically upgraded. Contact sales for assistance with customized installers.

If your 3.8.2010.2 environment utilizes customized mail reports, enterprise server property files, CSS, etc., contact our Customer Champion prior to upgrading to discuss your customizations.

LDAP Environments

There are significant changes to how LDAP is configured in version 3.4.1.5. You may need to reconfigure LDAP settings following the upgrade. View Important Notes For LDAP Environments for full details.

You must disable LDAP syncing for all LDAP-enabled orgs for the duration of the upgrade process. Once the upgrade is complete, you may enable LDAP syncing, and then troubleshoot any LDAP-related problems.

Client Auto-Upgrade For 3.8.2010 Clients Requires Port 4280

3.8.2010 client auto-upgrades require port 4280 to be open on the enterprise server unless you modify the configuration files. Changing the configuration files is not in the scope of this document. Please contact PRO Services for help with changing the configuration files, or simply make sure that the CrashPlan apps can reach the server on port 4280.

Storage Servers Require Connectivity To Master Server On Port 4282

If your Code42 environment has storage servers, you must verify that they can initiate a connection to the master server on port 4282 prior to the upgrade. This is required for the initial storage server sync after the upgrade from 3.8.2010.

Upgrade Storage Server In Lockstep With Master Server

For the first upgrade step from 3.8.2010 to 3.3, you must wait for the storage servers to sync and convert before continuing to later versions on any of the servers. We strongly recommend that you do the upgrades in lockstep for all upgrades in the sequence.

Cold Storage And Licensing

In version 3.5 and later, users with archives in cold storage count against the total number of user licenses. Thus, upgrading from version 3.8.2010.2 can cause your Code42 environment to unexpectedly run out of user licenses.

Record All File Inclusions, Exclusions, Hidden, Global, And Cloud Exclusion Rules

Record all file inclusions, exclusions, hidden, global, and cloud exclusion rules, as these may be lost during an upgrade. After the upgrade (but before the clients re-connect) confirm that all default and custom exclusions are present. If this is not completed, archive size may increase dramatically after the upgrade, until file exclusions are restored manually and archive maintenance runs.

Preparation

  1. Verify that your support and maintenance is up to date from the administration console's Licensing screen.
    Only environments under current support and maintenance are able to upgrade.
  2. Confirm your CrashPlan PROe version is 3.8.2010.2.
    If your version number is 3.8.2010.1 or earlier, you must upgrade to version 3.8.2010.2 before proceeding. 
    Find Your Version Number
  3. Optimize your enterprise servers' databases to increase the speed of the upgrade.
  • Dump the enterprise server(s) database for all of your enterprise servers from Settings > action menu > Dump Database
  • Import the database dumps back into their original enterprise servers from Settings > action menu > Import Database or from the Restore Database command line tool.
  1. Increase the Java memory available to the enterprise server(s) process on all your enterprise servers.
  2. Confirm OS compatibility (Release Notes for 3.4.1.5).
  3. Java 1.6.x is required for PROe version 3.4.1.5. Confirm Java version is 1.6.x.
  4. Verify browser compatibility (stable versions only):
  • Chrome version 19+ (recommended)
  • Firefox version 13+
  • Safari version 5+
  • Internet Explorer version 8, 9
    • If you use IE when upgrading your environment, we recommend IE version 9.
    • Disable Compatibility Mode to render pages correctly. IE users may still encounter blank or dimmed pages.
    • Add the master server and storage server hostnames/IP addresses as IE security exceptions.
  1. For environments utilizing LDAP integration for authentication, review Important Notes For LDAP Environments. Additional action is required after successfully upgrading your environment to the current version.

What To Expect

Upgrading CrashPlan PROe from 3.8.2010.2 to 3.6.1.5 requires a multi-step process. You must first upgrade your environment (all servers) from 3.8.2010.2 to 3.3.0.4, then from 3.3.0.4 to 3.4.1.5, and so on. Path:

  1. 3.8.2010.2 to 3.3.0.4
  2. 3.3.0.4 to 3.4.1.5
  3. 3.4.1.5 to 3.5.1.1
  4. 3.5.1.1 to 3.5.3.2
  5. 3.5.3.2 to 3.5.4
  6. 3.5.4 to 3.5.5
  7. 3.5.5 to 3.6.1.5

Client devices automatically upgrade from 3.8.2010 to 3.6.1.5 at the end of the process.

When you apply each upgrade, the enterprise server service shuts down and performs the upgrade tasks. When the upgrade tasks are complete, the enterprise server service starts up automatically. There are two enterprise server restarts during the upgrade from 3.8.2010.2 to 3.4.1.5.

Upgrade the master server first. Most 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.

You must block access from all CrashPlan devices to your master server for the duration of the upgrade process. Once the master server has been upgraded and you unblock client access, your CrashPlan devices automatically reconnect to the upgraded master server at a randomized interval of 1-15 minutes. The randomized re-connect interval means there may be a delay between when you unblock device access and when all devices have successfully upgraded.

Testing The Upgrade

Use A Test Environment 
It is absolutely critical that you first the upgrade to 3.6.1.5 in an isolated test environment before you upgrade your production environment. This particular upgrade is extremely complex and must be handled with the utmost care.

 

Note: The legacy term mount point is used throughout this article. Mount points are referred to as store points in current documentation. 

Single Server Environments

If your CrashPlan PROe environment contains a single enterprise server, please follow these steps to test your enterprise server upgrade. You need one test machine or VM to complete the upgrade test. You apply the test upgrade against a copy of your production master server's database. The enterprise server database dump contains the server's internal configuration information: orgs, users, computers, encryption keys, and reporting data for each account.

  1. Sign in to your 3.8.2010.2 production master server as a SYSADMIN user.
  2. Go to Settings > Dump Database to dump your master server's database. Database dumps for version 3.8.2010.2 are located on each mount point as well as within the application install directories:
    • Mac: /Library/Application Support/CrashPlan/PROServer/dumps
    • Windows XP and Server 2003: C:\Documents and Settings\All Users\Application Data\PROServer\dumps
    • Windows Vista and Server 2008: C:\ProgramData\PROServer\dumps\
    • Linux: /var/opt/proserver/dumps
    • Solaris 10 and OpenSolaris: /var/opt/proserver/dumps
  3. Before proceeding, verify that your database dump has the .sql.gz extension and has a non-zero file size value. 
    If your database dump file does not have the .sql.gz extension or has a zero file size value, cease all upgrade activities and contact our Customer Champions for assistance.
  4. On your test machine, download the following:
    1. Enterprise server version 3.8.2010.2
    2. CrashPlan app version 3.8.2010
    3. Upgrade files 3.8.2010.2 to 3.3.0.4 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    4. Upgrade files 3.3.x to 3.4.1.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    5. Upgrade files 3.4.x to 3.5.1.1 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    6. Upgrade files 3.5.1.x to 3.5.3.2 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    7. Upgrade files 3.5.3.2 to 3.5.4 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    8. Upgrade files 3.5.4 to 3.5.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    9. Upgrade files 3.5.5 to 3.6.1.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
  5. Copy the database dump created in Step 1 to your test machine.
  6. On your test machine, completely disconnect from any network connectivity. 
    This prevent your test server from sending alert emails to users or administrators.
  7. Install enterprise server version 3.8.2010.2 on the test machine.
  8. Import the database dump created in Step 1 into your test master server.
  9. Change the following settings on your test master server:
  10. Install CrashPlan app version 3.8.2010 on your test machine.
  11. Once the CrashPlan app's installation completes, register the CrashPlan app under a new user account.
  12. Back up a small amount of data to the test enterprise server, then disable the CrashPlan app until the after the final upgrade step.
  13. From the test enterprise server's administration console, go to Support > Upgrade and apply the 3.3.0.4 from 3.8.2010.2 upgrade.
  14. Wait a few minutes for the upgrade to complete.
  15. Refresh your browser window to see when the upgrade completes. The sign in screen for a successfully upgraded server looks like this: 
    PROe Login Prompt
  16. Sign in to the administration console as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  17. From the test enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.4.1.5 from 3.3.0.4 upgrade.
  18. Wait a few minutes for the upgrade to complete, then refresh your browser window.
  19. Sign in to the administration console as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  20. From the test enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.1.1  from 3.4.1.x upgrade.
  21. Wait a few minutes for the upgrade to complete, then refresh your browser window.
  22. Sign in to the administration console as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  23. From the test enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.3.2 from 3.5.1.1 upgrade.
  24. Wait a few minutes for the upgrade to complete, then refresh your browser window.
  25. Sign in to the administration console as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  26. From the test enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.4  from 3.5.3.2 upgrade.
  27. Wait a few minutes for the upgrade to complete, then refresh your browser window.
  28. Sign in to the administration console as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  29. From the test enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.5  from 3.5.4 upgrade.
  30. Wait a few minutes for the upgrade to complete, then refresh your browser window.
  31. Sign in to the administration console as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  32. From the test enterprise server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the  3.6.1.5 from 3.5.5 upgrade.

Verify The Upgrade Test

To verify that the test upgrade was successful, check the following:

  • Sign in to the test master server's administration console. Verify that you are able to sign in.
  • Go to Settings > Server > Upgrade and verify that the displayed version number is 3.6.1.5.
  • 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.
  • Start the CrashPlan service.
  • On the test CrashPlan app, go to the Backup screen. Verify your test CrashPlan app is connected to the test master server.
  • On the test CrashPlan app, go to Settings > Account. Verify that the CrashPlan app successfully upgraded to version 3.6.1.
  • You are able to back up and restore files from the test CrashPlan app.

Multi-Server Environments

If your CrashPlan PROe environment contains multiple enterprise servers, please follow these steps to test your enterprise server upgrade. You need two test machines or VMs to complete the upgrade test. You apply the test upgrade against a copy of your production master server's database. The enterprise server database dump contains the server's internal configuration information: orgs, users, computers, encryption keys, and reporting data for each account.

  1. Dump your production master server's database
    1. Sign in to your 3.8.2010.2 production master server as a SYSADMIN user.
    2. Go to Settings > Dump Database to dump your master server's database. Database dumps for version 3.8.2010.2 are located on each mount point as well as within the application install directories:
  • Mac: /Library/Application Support/CrashPlan/PROServer/dumps
  • Windows XP and Server 2003: C:\Documents and Settings\All Users\Application Data\PROServer\dumps
  • Windows Vista and Server 2008: C:\ProgramData\PROServer\dumps\
  • Linux: /var/opt/proserver/dumps
  • Solaris 10 and OpenSolaris: /var/opt/proserver/dumps
  1. Dump your production storage servers' databases
    1. Sign in to one of your 3.8.2010.2 production storage servers as a SYSADMIN user.
    2. Go to Settings > Dump Database to dump the storage server's database.
  2. Before proceeding, verify that your database dumps have the .sql.gz extension and have a non-zero file size value.
    If your database dump files do not have the .sql.gz extension or have a zero file size value, cease all upgrade activities and contact our Customer Champions for assistance.
  3. Download the following to your test master server:
    1. Enterprise server version 3.8.2010.2
    2. CrashPlan app version 3.8.2010
    3. Upgrade files 3.8.2010.2 to 3.3.0.4 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    4. Upgrade files 3.3.x to 3.4.1.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    5. Upgrade files 3.4.x to 3.5.1.1 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    6. Upgrade files 3.5.1.x to 3.5.3.2 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    7. Upgrade files 3.5.3.2 to 3.5.4 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    8. Upgrade files 3.5.4 to 3.5.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    9. Upgrade files 3.5.5 to 3.6.1.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
  4. Download the following to your test storage server (use links in Step 2):
    1. Enterprise server version 3.8.2010.2
    2. Upgrade files 3.8.2010.2 to 3.3.0.4 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    3. Upgrade files 3.3.x to 3.4.1.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    4. Upgrade files 3.4.x to 3.5.1.1 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    5. Upgrade files 3.5.1.x to 3.5.3.2 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    6. Upgrade files 3.5.3.2 to 3.5.4 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    7. Upgrade files 3.5.4 to 3.5.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
    8. Upgrade files 3.5.5 to 3.6.1.5 for your platform:
      Linux | Mac | Solaris | Windows | MD5 checksums
  5. Set up a closed, private network with no outside connectivity. Only the two test machines or VMs should be connected on the closed network.
    This prevents your test servers from sending alert emails to users or administrators.
  6. Prepare the test master server:
    1. Copy the database dump created in Step 1 to your test master server.
    2. Install enterprise server version 3.8.2010.2 on your test master server.
    3. Import the database dump created in Step 1 into your test master server from Settings > Import Database.
    4. Change the following settings on your test master server:
  7. Prepare the test storage server:
    1. Copy the database dump created in Step 2 to your test storage server.
    2. Install enterprise server version 3.8.2010.2 on your test storage server.
    3. Import the database dump created in Step 2 into your test storage server.
    4. Update your test storage server's Primary and Secondary Network Addresses (Settings > Edit Server Settings > Network Addresses) to work on the closed, private network.
  8. Prepare the test CrashPlan app:
    1. Install CrashPlan app version 3.8.2010 on the master server test machine.
    2. Once the CrashPlan app's installation completes, register the CrashPlan app under a new user account.
      If your environment uses LDAP to authenticate users, register the user in an org that uses CrashPlan PROe's built in authentication.
    3. Back up a small amount of data to the test master server, then disable the CrashPlan app until the after the final upgrade step.
  9. Upgrade the test master server:
    1. From the test master server's administration console, go to Support > Upgrade and apply the 3.3.0.4 from 3.8.2010.2 upgrade.
    2. Wait a few minutes for the upgrade to complete.
    3. Refresh your browser window to see when the upgrade completes. The sign in screen for a successfully upgraded server looks like this: 
      PROe Login Prompt
    4. Sign in to the test master server's administration console as a SYSADMIN user.
      If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  10. Upgrade your test storage server to 3.3.0.4:
    1. From the test storage server's administration console, go to Support > Upgrade and apply the 3.3.0.4 from 3.8.2010.2 upgrade.
    2. Wait a few minutes for the upgrade to complete.
    3. Refresh your browser window to see when the upgrade completes.
    4. Sign in to the test storage server's administration console as a SYSADMIN user. 
      If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  11. Upgrade the test master server from 3.3.0.4 to 3.4.1.5. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.4.1.5 from 3.3.0.4 upgrade.
  12. Upgrade the test storage server from 3.3.0.4 to 3.4.1.5. From the test storage server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.4.1.5 from 3.3.0.4 upgrade.
  13. Wait a few minutes for the upgrades to complete, then refresh your browser window(s). Verify that both the master server and storage server upgraded to version 3.4.1.5.
  14. Sign in to the administration console of the test master server as a SYSADMIN user.
    If you are unable to sign in to the administration console following the upgrade, cease all upgrade activities and contact our Customer Champions.
  15. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.1.1  from 3.4.1.x upgrade.
  16. Wait a few minutes for the upgrades to complete, then refresh your browser window(s). Verify that both the master server and storage server upgraded to version 3.5.1.1.
  17. Sign in to the administration console of the test master server as a SYSADMIN user.
  18. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.3.2 from 3.5.1.1 upgrade.
  19. Wait a few minutes for the upgrades to complete, then refresh your browser window(s). Verify that both the master server and storage server upgraded to version 3.5.3.2.
  20. Sign in to the administration console of the test master server as a SYSADMIN user.
  21. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.4  from 3.5.3.2 upgrade.
  22. Wait a few minutes for the upgrades to complete, then refresh your browser window(s). Verify that both the master server and storage server upgraded to version 3.5.4.
  23. Sign in to the administration console of the test master server as a SYSADMIN user.
  24. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the 3.5.5  from 3.5.4 upgrade.
  25. Wait a few minutes for the upgrades to complete, then refresh your browser window(s). Verify that both the master server and storage server upgraded to version 3.5.5.
  26. Sign in to the administration console of the test master server as a SYSADMIN user.
  27. From the test master server's administration console, go to Settings > Server > Action Menu > Upgrade and apply the  3.6.1.5 from 3.5.5 upgrade.

Verify The Upgrade Test

To verify that the test upgrade was successful, check the following:

  • Sign in to the test master server's administration console. Verify that you are able to sign in.
  • Go to Settings > Server > Upgrade and verify that the displayed version number is 3.6.1.5.
  • 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.
  • Go to Destinations > Servers and verify that the test storage server is online and connected to the test master server.
  • Start the CrashPlan service.
  • On the test CrashPlan app, go to the Backup screen. Verify your test CrashPlan app is connected to the test master server.
  • On the test CrashPlan app, go to Settings > Account. Verify that the CrashPlan app successfully upgraded to version 3.6.1.
  • You are able to back up and restore files from the test CrashPlan app.

Performing The Production Upgrade

Setup

Before upgrading your environment, you must make firewall changes to ensure devices running the CrashPlan app upgrade at the proper time.

You must specifically allow each of your storage servers to communicate with the master server during the upgrade process. The upgrade will fail if storage servers are unable to communicate with the master server.

  1. Create a list of all storage servers and their IP addresses.
  2. On your production master server:
    1. Dump your enterprise server(s)'s database
      It is essential that you create a new dump of your enterprise server(s)'s database prior to performing the production upgrade to ensure that you have a current copy of user information and all configurations.
    2. Back up your firewall configuration.
    3. On your master server's firewall, block CrashPlan app devices from accessing the master server. Block TCP port 4282 or 443, whichever port your master server's Primary and Secondary Network Addresses are configured to use. This prevents the CrashPlan app devices from upgrading prematurely - we want the CrashPlan app devices to upgrade after all servers have upgraded successfully to version 3.4.1.5. This example command for an iptables firewall blocks all inbound eth0 connections on TCP 4282:
      iptables -I INPUT -i eth0 -p tcp --dport 4282 -j REJECT
    4. From another host, use telnet to verify that firewall rules reject connections on the backup port 4282 /443. Example commands:
      telnet mymasterserver.example.com 4282
    5. Multi-server environments:
      1. On your master server's firewall, allow communication between the master server and each storage server. The upgrade will fail if storage servers are unable to communicate with the master server. Example command for an iptables firewall:
        iptables -I INPUT -s 10.42.10.42/32 -j ACCEPT #### accept connections from Minneapolis storage server
      2. From your production storage servers, verify that all storage servers are able to communicate with the master server. Example commands run from a storage server:
        telnet mymasterserver.example.com 4282
        telnet mymasterserver.example.com 443
        

Upgrade Your Production Master Server

Upgrading from 3.8.2010.2 to 3.6.1.5 requires a multiple-step process. Steps:

  1. From 3.8.2010.2 to 3.3.0.4
  2. From 3.3.0.4 to 3.4.1.5
  3. From 3.4.1.5 to 3.5.1.1
  4. From 3.5.1.1 to 3.5.3.2
  5. From 3.5.3.2 to 3.5.4
  6. From 3.5.4 to 3.5.5
  7. From 3.5.5. to 3.6.1.5

It is imperative that you test the upgrade prior to upgrading your production environment.

Upgrade Your Master Server From Version 3.8.2010.2 To 3.3.0.4

  1. Download the 3.8.2010.2 to 3.3.0.4 upgrade files for your platform: Linux | Mac | Solaris | Windows | MD5 checksums
  2. Apply the 3.8.2010.2 to 3.3.0.4 upgrade:
    1. Sign in to your master server's administration console
    2. From the main navigation menu, click Support
    3. In the left menu, click Upgrade
    4. Browse to the downloaded upgrade file and click Save
  3. Wait for the upgrade to complete
  4. Verify the master server's upgrade to 3.3.0.4:
  • Sign in to the master server's administration console. Verify that you are able to sign in.
  • Go to Settings > Server and verify that the displayed version number is 3.3.0.4.
  • 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.

If any of the verification steps fail, cease all upgrade activities and contact our Customer Champions.

Multi-server environments: Once your master server has successfully upgraded to 3.3.0.4, repeat the above steps to upgrade your storage servers. When upgrading your storage servers, you must wait for the storage servers to sync and convert before proceeding with further upgrades. Watch the storage server logs with this command to verify the conversion and sync have completed (Linux example provided below. Change the path to your storage server's log to reflect your platform.):

tail -Fn 10000 /var/log/proserver/com*0 | grep -E "(STORAGE NODE CON|StorageNodeS|SHUTDOWN|CPServer star)"

The conversion completes first. Then, the server shuts down and restarts. Finally, the sync completes.

Delete The 3.8.2010.2 To 3.3.0.4 Upgrade File

Once the upgrade to 3.3.0.4 is complete and your environment passes all verification steps, delete the 3.8.2010.2 to 3.3.0.4 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac: /Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • Windows: C:\Program Files\CrashPlan PROe Server\Upgrade

Remove Legacy User Roles

Certain environments may have users assigned to specific legacy roles. There is a known issue during upgrade in those environments. Before proceeding with further upgrades, audit your environment and remove these legacy roles. The legacy roles listed below have no permissions assigned to them, so the roles can be removed safely from your users. The roles must be removed from all users, both active and deactivated.

To audit:

  1. Sign in to the administration console as a user with the SYSADMIN role.
  2. Under Roles, select the Consumer User role.
  3. In the lower-right corner of the administration console, a count of the number of users assigned the selected role is displayed. If this number is greater than 0, you must remove this role from all associated users. Clicking the number displays a list of the users with this role. You should remove the role manually, but if your audit shows that more than 50 users have been assigned the legacy role, you may contact our Customer Champions for assistance in removing the roles.
  4. Select the CONTACT role.
  5. Check the user count to see if any users are assigned this role, and remove the role manually, or contact our Customer Champions if you found more than 50 users assigned to the CONTACT role.

Upgrade Your Enterprise Server From Version 3.3.0.4 To 3.4.1.5

  1. Dump your master server's database from Settings > Server > Action Menu > Dump Database
  2. Download the 3.3.x to 3.4.1.5 upgrade file for your platform: Linux | Mac | Solaris | Windows | MD5 checksums
  3. Apply the upgrade from Settings > Server > Action Menu > Upgrade
  4. Verify the master server's upgrade to 3.4.1.5
  • Sign in to the master server's administration console. Verify that you are able to sign in.
  • Go to Settings > Server and verify that the displayed version number is 3.4.1.5.
  • You are able to view the details of an org, a user, and a device.

If any of the verification steps fail, cease all upgrade activities and contact our Customer Champions.

Multi-server environments: Once your master server has successfully upgraded to 3.4.1.5, repeat the above steps to upgrade your storage servers.

Delete The 3.3.0.4 To 3.4.1.5 Upgrade File

Once the upgrade to 3.4.1.5 is complete and your environment passes all verification steps, delete the 3.3.0.4 to 3.4.1.5 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac: /Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • Windows: C:\Program Files\CrashPlan PROe Server\Upgrade

Upgrade Your Master Server From Version 3.4.1.5 To Version 3.5.1.1

You will not be able to enter annual, device-based product license keys into your master server after upgrading to 3.5.1. Contact Sales with any licensing questions prior to upgrading.
  1. Verify that all purchased annual, device-based product license keys have been applied to your environment.
  2. Dump your server's database from Settings > Server > Action Menu > Dump Database.
  3. Download the upgrade file for your platform.
  4. For multi-server environments with automatic storage server upgrades enabled:
    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:
    • Linux master server:
      /opt/proserver/upgrade OR/home/userName/proserver/server/upgrade
    • Mac master server:
       /Applications/PROServer/Content/Resources/Java/upgrade
    • Windows master server:
      C:\Program Files\CrashPlan\upgrade
  5. Apply the upgrade from Settings > Server > Action Menu > Upgrade.
  6. Clear your browser cache to ensure that the upgraded version of the administration console displays correctly after the upgrade.
 
To verify that the upgrade test was successful, check the following:
  • You are able to sign in to the master server's administration console.
  • 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.
  • (For multi-server environments) Your storage servers are online and connected to the master server.
  • Your CrashPlan app devices are able to re-connect to the master server.
  • You are able to back up and restore files from a CrashPlan app.

Delete The 3.4.1.5 To 3.5.1.1 Upgrade File

Once the upgrade to 3.5.1.1 is complete and your environment passes all verification steps, delete the 3.4.1.5 to 3.5.1.1 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac/Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • WindowsC:\Program Files\CrashPlan PROe Server\Upgrade

Upgrade Your Master Server From Version 3.5.1.1 To Version 3.5.3.2

  1. Dump your master server's database from Settings > Server > Action Menu > Dump Database.
  2. Download the upgrade file(s) for your enterprise server platform(s).
  3. For multi-server environments with automatic storage server upgrades enabled:
    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:
    • Linux master server:
      /opt/proserver/upgrade OR/home/userName/proserver/server/upgrade
    • Mac master server:
      /Applications/PROServer.app/Content/Resources/Java/upgrade
    • Windows master server:
       C:\Program Files\CrashPlan\upgrade
  4. Designate an existing CrashPlan app to upgrade first as a test.
  5. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  6. The enterprise server restarts after successfully upgrading and asks if you want to upgrade all of your CrashPlan app devices now or later. Click No, I'll upgrade later.
  7. Verify the following:
    • You are able to sign in to the master server's administration console.
    • Under Settings > Server, the enterprise server's current version number is 3.5.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 test CrashPlan app is connected to the test master server.
  8. Once you've verified the enterprise server upgrade, initiate the CrashPlan app upgrade for a test device:
    1. Navigate to the test device's Device Details pane.
    2. From the Action Menu, select Upgrade.
    3. Confirm that you are ready to upgrade your test device.
      The upgrade command is sent to the device immediately and the device begins the upgrade process.
  9. Verify the CrashPlan app upgrade:
    • The administration console displays a “success” message in the lower left corner.
    • Launch the CrashPlan app and go to Settings > Account to verify that the version number is 3.5.3.
    • You are able to back up and restore files from the test CrashPlan app.
  10. When you are ready to upgrade the rest of your CrashPlan app devices, enable Auto-upgrade devices to upgrade all of your CrashPlan app devices:
    1. From the administration console, go to Settings > Server.
    2. Enable Auto-upgrade devices.
    3. Confirm that you'd like to upgrade all your CrashPlan app devices now and click OK.

Delete The 3.5.1.1 To 3.5.3.2 Upgrade File

Once the upgrade to 3.5.3.2 is complete and your environment passes all verification steps, delete the 3.5.1.1 to 3.5.3.2 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac: /Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • Windows: C:\Program Files\CrashPlan PROe Server\Upgrade

Upgrade Your Master Server From Version 3.5.3.2 To Version 3.5.4

  1. Dump your master server's database from Settings > Server > Action Menu > Dump Database.
  2. Download the upgrade file(s) for your master server(s).
  3. For multi-server environments with automatic storage server upgrades enabled:
    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:
    • Linux master server:
      /opt/proserver/upgrade OR/home/userName/proserver/server/upgrade
    • Mac master server:
      /Applications/PROServer.app/Content/Resources/Java/upgrade
    • Windows master server:
      C:\Program Files\CrashPlan\upgrade
  4. Apply the master server(s) upgrade from Settings > Server > Action Menu > Upgrade.
    The master server(s) restarts after successfully upgrading.
  5. After the server restart completes, clear your browser's cache and sign in to the administration console.
  6. Verify the following:
    • You are able to sign in to the master server's administration console.
    • Under Settings > Server, the master server(s)'s current version number is 3.5.4.
    • 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 to the master server.
    • You are able to back up and restore files from a CrashPlan app device.

Delete The 3.5.3.2 To 3.5.4 Upgrade File

Once the upgrade to 3.5.4 is complete and your environment passes all verification steps, delete the 3.5.3.2 to 3.5.4 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac: /Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • Windows: C:\Program Files\CrashPlan PROe Server\Upgrade

Upgrade Your Master Server From Version 3.5.4 To Version 3.5.5

  1. Dump your master server's database from Settings > Server > Action Menu > Dump Database.
  2. Download the upgrade file(s) for your enterprise server(s).
  3. For multi-server environments with automatic storage server upgrades enabled:
    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:
    • Linux master server:
       /opt/proserver/upgrade OR/home/userName/proserver/server/upgrade
    • Mac master server:
      /Applications/PROServer.app/Content/Resources/Java/upgrade
    • Windows master server:
      C:\Program Files\CrashPlan\upgrade
  4. Apply the enterprise server(s) upgrade from Settings > Server > Action Menu > Upgrade.
    The enterprise server(s) restarts after successfully upgrading.
  5. After the server restart completes, clear your browser's cache and sign in to the administration console.
  6. Verify the following:
    • You are able to sign in to the master server's administration console.
    • Under Settings > Server, the enterprise server(s)'s current version number is 3.5.5.
    • 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 to the master server.
    • You are able to back up and restore files from a CrashPlan app device.

Delete The 3.5.4 To 3.5.5 Upgrade File

Once the upgrade to 3.5.5 is complete and your environment passes all verification steps, delete the 3.5.4 to 3.5.5 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac: /Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • Windows: C:\Program Files\CrashPlan PROe Server\Upgrade

Upgrade Your Master Server From Version 3.5.5 To Version 3.6.1.5

  1. Dump your master server's database from Settings > Server > Action Menu > Dump Database.
  2. Download the upgrade file(s) for your enterprise server platform(s).
  3. For multi-server environments with automatic {{storagenode4}} upgrades enabled:
  4. 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:
    • Linux master server:
      /opt/proserver/upgrade OR /home/userName/proserver/server/upgrade
    • Mac master server: /Applications/PROServer.app/Content/Resources/Java/upgrade
    • Windows master server:
      C:\Program Files\CrashPlan\upgrade
  5. Apply the enterprise server upgrade from Settings > Server > Action Menu > Upgrade.
  6. Review the End User License Agreement and click I AGREE to proceed with the upgrade.
    The enterprise server restarts after successfully upgrading.
  7. After the server restart completes, clear your browser's cache and sign in to the administration console.
  8. When asked if you would like to upgrade all of your CrashPlan app devices now or later, choose No, I'll upgrade later.
  9. Verify the following:
    • You are able to sign in to the master server's admin administration console.
    • Under Settings > Server, the current version number is 3.6.1.5.
    • 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 to the master server.
    • You are able to back up and restore files from a CrashPlan app device.

Delete The 3.5.5 To 3.6.1.5 Upgrade File

Once the upgrade to 3.6.1.5 is complete and your environment passes all verification steps, delete the 3.5.5 to 3.6.1.5 upgrade file from your servers' file systems to free space in preparation for the next upgrade. Upgrade files are located at:

  • Linux/Solaris (default): /opt/proserver/server/upgrade
  • Mac: /Applications/PROServer.app/Contents/Resources/Java/Upgrade
  • Windows: C:\Program Files\CrashPlan PROe Server\Upgrade

Upgrade Your CrashPlan App Devices

At this stage of the upgrade process, all your enterprise servers are successfully running version 3.6.1.5. CrashPlan app devices are blocked at the firewall and running CrashPlan app version 3.8.2010. In order for your CrashPlan app devices to automatically upgrade, you must:

  1. Change the value of the security provider property on the master server
  2. Update your firewall configuration to allow inbound connections to the master server from the CrashPlan app devices

Edit Security Provider Property

CrashPlan app devices running 3.8.2010 cannot upgrade until a change is made on the master server to the “b42.cpc.securityProvider” property.

Until the b42.cpc.securityProvider property is changed, version 3.8.2010 CrashPlan app devices are unable to connect and all server destinations appear as offline.

Changing the security key from SP to DH allows version 3.8.2010 CrashPlan app devices to connect and upgrade successfully to version 3.4.1. On the master server:

  1. Stop the proserver process:
    • Mac: Open the Terminal and run the following command:
      sudo launchctl unload /Library/LaunchDaemons/com.crashplan.proserver.plist
    • Windows: Use the Windows Services manager to stop the PROServer service
    • Linux: There are two possible commands, depending on your Linux distribution:
      /etc/init.d/proserver stop
      /opt/proserver/bin/proserver stop
    • Solaris:
      /opt/sfw/crashplan/bin/proserver stop
  2. Open the following file in a plain text editor:
    Use Notepad, Notepad++, vim, emacs, nano, pico, TextEdit, etc. to edit the file. Avoid word processors such as Word, Wordpad, Pages or OpenOffice Writer.
    • Mac:
      /Applications/PROServer.app/Contents/Resources/Java/conf/conf_proe.properties
    • Windows:
      C:\Program Files\CrashPlan PROe Server\conf\conf_proe.properties
    • Linux:
      /opt/proserver/server/conf/conf_proe.properties (default install)
    • Solaris:
      /opt/proserver/server/conf/conf_proe.properties (default install)
  3. In the section labeled Misc, find the line beginning with b42.cpc.securityProvider. Change this line:
    b42.cpc.securityProvider = SP

    to this:

    b42.cpc.securityProvider = DH
  4. Save your changes.
  5. Start the proserver process:
    • Mac: Open Terminal and run the following command:
      sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist
    • Windows: Use the Windows Services manager to start the PROServer service
    • Linux: There are two possible commands, depending on your Linux distribution:
      /etc/init.d/proserver start
      /opt/proserver/bin/proserver start
    • Solaris:
      /opt/sfw/crashplan/bin/proserver start
      

Firewall Change: Unblock CrashPlan App Devices

At the beginning of the production upgrade process, CrashPlan app devices were blocked on your firewall from accessing the master server. Now that your servers have successfully upgraded, open the firewall and allow your CrashPlan app devices to upgrade to version 3.6.1.4.

Note: The CrashPlan app upgrade process increases the load on the network and the master server. If you have any concerns on how this temporary increase will affect your environment, please contact our Customer Champions to discuss.

Revert your firewall configuration to the backed up version and restart your firewall.

Examples For iptables Environments

If you use an iptables firewall and you need to disable the firewall temporarily, you can flush ALL the rules using:

sudo iptables -F

OR disable just the new rules you added earlier one at a time. List the firewall INPUT chain in order to remove the correct rule:

iptables -L INPUT 

If rule 1 of the INPUT chain is:

REJECT     tcp  --  anywhere             anywhere             tcp dpt:4282 reject-with icmp-port-unreachable

Then delete rule 1 from the INPUT chain with this command:

iptables -D INPUT 1 

Verify Firewall Rules

Use telnet to verify that the firewall rules have reverted and that CrashPlan app devices and the storage servers are able to connect to the master server. Example command:

telnet mymasterserver.example.com 4282

CrashPlan App Devices Upgrade

Once you've unblocked the firewall, CrashPlan app devices reconnect and automatically upgrade. It may take hours, days, or weeks for all of your environment's CrashPlan app devices to complete the upgrade, depending on a number of factors: the number of devices in your environment, available bandwidth on your network, when the CrashPlan app devices next attempt to connect, or when users next power up their computers.

After The Production Upgrade

When all of the CrashPlan app devices have successfully upgraded from 3.8.2010, switch the b42.cpc.securityProvider property back to the default value 'SP'.

Security Provider
If you do not change the b42.cpc.securityProvider value back to SP, your devices may be unable to connect to your enterprise server.
  1. Stop the proserver process:
    • Mac: Open the Terminal and run the following command:
      sudo launchctl unload /Library/LaunchDaemons/com.crashplan.proserver.plist
    • Windows: Use the Windows Services manager to stop the PROServer service
    • Linux: There are two possible commands, depending on your Linux distribution:
      /etc/init.d/proserver stop
      /opt/proserver/bin/proserver stop
    • Solaris:
      /opt/sfw/crashplan/bin/proserver stop
  2. Open the following file in a plain text editor:
    Use Notepad, Notepad++, vim, emacs, nano, pico, TextEdit, etc. to edit the file. Avoid word processors such as Word, Wordpad, Pages or OpenOffice Writer.
    • Mac: /Applications/PROServer.app/Contents/Resources/Java/conf/conf_proe.properties
    • Windows:
      C:\Program Files\CrashPlan PROe Server\conf\conf_proe.properties
    • Linux: /opt/proserver/server/conf/conf_proe.properties (default install)
    • Solaris: /opt/proserver/server/conf/conf_proe.properties (default install)
  3. In the section labeled Misc, find the line beginning with b42.cpc.securityProvider. Change this line:
    b42.cpc.securityProvider = DH

    to this:

    b42.cpc.securityProvider = SP
  4. Save your changes.
  5. Start the proserver process:
    • Mac: Open the Terminal and run the following command:
      sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist
    • Windows: Use the Windows Services manager to start the PROServer service
    • Linux: There are two possible commands, depending on your Linux distribution:
      /etc/init.d/proserver start
      /opt/proserver/bin/proserver start
    • Solaris:
      /opt/sfw/crashplan/bin/proserver start

 

After the upgrade, user configurations might have old destinations, or an invalid configuration. To repair all client configurations, in the control panel for the master server, double-click the CrashPlan logo to enter the CLI. Enter the command config.fix fix all. This command will take some time to complete.

Important Notes For LDAP Environments

The following section only applies to environments who are authenticating users via CrashPlan PROe's LDAP integration.

Pre-Upgrade

You must turn LDAP syncing off for any orgs that use LDAP for the duration of the upgrade process. Once you have upgraded your enterprise servers to version 3.6.1.5, you may turn LDAP syncing back on, and then proceed to troubleshoot any LDAP issues.

Tip: Before you upgrade your production environment, make a record of existing LDAP settings. You may need to reference them following the upgrade. Contact your network administrator if you have any questions about the settings.

Post-Upgrade

LDAP URL And Search Base

LDAP settings in version 3.6.1.5 are under Settings > Security > LDAP.

If your LDAP URL and search base includes any spaces, you must remove any "%20" escape characters from the search base after upgrading. In version 3.6.1.5, all LDAP searches return an error if there are any "%20" escape characters in the search base.

LDAP Server Setup

Example URL And Search Base (Correct in 3.6.1.5):

ldap://myldapserver.example.com:389/ou=West Coast,dc=example,dc=com
Example URL And Search Base (Incorrect in 3.6.1.5):
ldap://myldapserver.example.com:389/ou=West%20Coast,dc=example,dc=com


If the connection strings work, but no users show up in test search results, you may need to to set the following properties via the administration console CLI, which will cause the LDAP search to behave like 3.8.2010:

prop.set b42.ldap.ignore.partialResultException true save  = Ignore Partial Result Exceptions
prop.set b42.ldap.referral follow save = Follow referrals

Attribute Mappings

CrashPlan PROe version 3.6.1.5 uses Javascript in LDAP configurations, instead of regular expressions as in earlier versions (3.8.2010 and earlier). Example Attribute Mappings from 3.8.2010.2:

LDAP Attribute Mappings Before Conversion

Attribute Mappings Conversion

There is a process during the upgrade from 3.6.1.5 that converts any configured LDAP regular expressions to Javascript. Example Attribute Mappings in 3.6.1.5 after conversion to Javascript:

LDAP Attribute Mappings After Conversion

Once the upgrade completes, verify that the new attribute mapping values are valid for your environment:

  1. On your version 3.6.1.5 master server, go to Settings > Security > LDAP.
  2. Click the LDAP server's name to view settings.
  3. Next to Active script, verify that the Javascript is valid for your environment.
    • The Active script value under 3.6.1.5 combines the values from your 3.8.2010.2 User Status Attribute and User Status Regex configuration and converts them to Javascript.
    • If your environment does not utilize the LDAP Active Status feature under 3.8.2010.2, the upgrade populates the Active script field with the following Javascript:
      function(entry) { return true; }

      In practice, this means that all users found in LDAP are considered active in CrashPlan PROe.

  4. Next to Org name script, verify that the Javascript is valid for your environment.
    • If your environment does not perform org extraction when users register, this field is blank after the upgrade to 3.6.1.5.
    • If your environment used an LDAP attribute to perform org extraction under 3.8.2010.2, the upgrade combines the following fields and converts them to Javascript: Organization Name Attribute, Person Attribute in Group and Org Group Search
    • If your environment applied a Regex to the user's DN to perform org extraction under 3.8.2010.2., the Organization Name Regex is converted to Javascript.

Contact Support

Should you have any questions about the content of this article, or run into any situations that this article does not address, please contact our Customer Champions for further assistance.

If you run into any issues during the upgrade, please include the following information in your support request:

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