Skip to main content
Code42 Support

Set up a multi-server test environment

Applies to:
  • CrashPlan PROe

Overview

This tutorial explains how to to set up a multi-server test Code42 environment that simulates your production Code42 environment. You can use the test environment to perform upgrade and feature testing without impacting your production environment.

If you have a single-server production Code42 environment, see Setting Up A Single-Server Test Environment.

Definitions

Code42 environment

Term encompassing all components of a Code42 for Enterprise environment, with one authority authority server. Components may include: Code42 servers, administration console, organizations, users, devices. Example usage: Go to Settings > Security > LDAP to enable LDAP integration for your Code42 environment.

host server
A physical or virtual server that hosts a Code42 server.
production Code42 environment
The Code42 environment that supports the day-to-day operations of your business.
test Code42 environment
A Code42 environment that is dedicated to testing and separated from your production Code42 environment.

Considerations

Your test Code42 environment should contain one master server and at least one storage server. You do not need to set up a test storage server for each storage server in your production Code42 environment.

Before you begin

  • Make sure your test Code42 environment is completely separated from your production Code42 environment to avoid unintended interaction during testing.
  • Allocate two physical servers or virtual machines to host the test master server and test storage server.
  • Allocate a separate computer or virtual machine to run the test CrashPlan app and SharePlan app.

Step 1: Gather information from your production Code42 Environment

Perform these steps for your master server and one of your storage servers:

  1. Sign in to your production Code42 server's administration console.
  2. Navigate to Settings > Server.
  3. Record the following information:
    • Current server version
    • Primary network address
    • Secondary network address
  4. From the action menu, select Dump Database.
    The database dump is written to the host server's file system. The location varies by operating system:
    • Linux: /var/opt/proserver/dumps
      Applies to Code42 servers installed as root on Ubuntu
    • Windows: C:\ProgramData\PROServer\dumps
    • OS X: /Library/Application Support/CrashPlan/PROServer/dumps
  5. Copy the database dump to your test server.
  6. If you have enabled automatic secure keystore, copy the password file to your test server.
    The password file is written to the host server's file system. The location varies by operating system:
    • Linux: /var/opt/proserver/ksp
      Applies to Code42 servers installed as root on Ubuntu
    • Windows: C:\Program Files\CrashPlan PROe Server\data\ksp
    • OS X: /Library/Application Support/CrashPlan/PROServer/ksp

Step 2: Set up the test Enterprise Servers

Perform these steps for both test host servers:

  1. Disconnect your host server from your production network.
    This prevents your test enterprise server from interacting with devices or sending alert emails to users or administrators.
  2. Assign an IP address to the host server.
    If possible, use an IP address that matches your production enterprise server to simplify the configuration process.
  3. Make sure that the host names for both host servers resolve to the correct IP addresses by taking one of these actions:
    • If your test environment has a dedicated DNS server, configure DNS records for both servers.
    • Edit the hosts file on the server to add entries for both servers.
      For example:
      192.0.2.101    master-server.example.com
      192.0.2.102    storage-server.example.com
      
  4. On the host server, install the enterprise server version that matches your production Code42 environment.

Step 3: Import the database dumps

Import the database dumps from your production Code42 environment:

  1. On the test master server, import the database dump from your production master server.
  2. On the test storage server, import the database dump from your production storage server.

There are two ways to import the database dump:

  • Use the restore_database script to import a database dump. You must use the command line to access the restore_database script, but you do not need your master license key.
  • Use the administration console to import a database dump. You must have your master license key to access the administration console for the first time.

Importing with the restore_database script

  1. Open a command line interface with administrative privileges on your new server:
    • Linux: Terminal or equivalent for your distribution
    • Windows: Command or PowerShell
    • OS X: Terminal
  2. Navigate to the directory for the Code42 server command line tools:
    • Linux: /opt/proserver/bin
      Applies to Code42 servers installed as root on Ubuntu
    • Windows: C:\Program Files\CrashPlan PROe Server\bin
    • OS X: /Applications/PROServer.app/Contents/Resources/Java/bin/
  3. Run the restore_database command on the location of the database dump you want to import. For example, on Linux:
    sudo ./restore_database.sh /var/opt/proserver/dumps/proserver-db_1332824401321_2012-06-26_121011.sql.gz

For more information, refer to the Command Line Tools reference.

Import database dump using the Administration console

  1. Sign in to the administration console.
  2. Go to Settings > Server > action menu > Import Database
  3. Import the database from desired location. Database dumps are ordered by date.
  4. Click Submit. Two notifications appear:
    1. "Database import submitted. Server will shut down."
    2. "Server connection has been lost."
  5. The server imports the selected database.
  6. Select Reconnect to reload the administration console sign-in page.
  7. Sign in to the administration console to verify your changes.

Step 4: Verify Enterprise Server communication

Verify that the test enterprise servers are able to communicate with each other.

  1. Sign in to the master server's administration console.
  2. Navigate to Destinations > Servers.
  3. Click the name of the test storage server.
  4. Find the online indicator located at the top left of the server details.
    A solid circle indicates that the storage server is online.
    Server status indicator

Step 5: Configure Store Points

The store points from your production Code42 environment will not function on your test enterprise servers if the corresponding directories do not exist on the file system. To make your test enterprise servers function correctly, disable existing store points and create a new store point for testing. We recommend creating a store point on the test storage server to simulate your production Code42 environment.

  1. Sign in to your test authority server's administration console.
  2. Navigate to Destinations > Store Points.
  3. Configure each existing store point to reject new archives:
    1. Click the name of the store point.
    2. From the action menu, select Reject New Archives.
  4. Create a new store point for testing.
    1. Navigate to Destinations > Servers.
    2. Click the name of the test Code42 server.
    3. From the action menu, select Add Store Point.
    4. Configure store point settings:
      • Name: Enter a descriptive name.
      • Path: Enter the path to a directory that currently exists on the file system.
        The host Code42 server must have permission to write to this directory.
      • Note: (Optional) Enter descriptive notes.
    5. Click Create.

Step 6: Set up test CrashPlan devices

  1. Download the Code42 app from the test authority server's administration console.
    • If the Welcome to Code42 message appears when you sign in, click CrashPlan to download the apps.
    • If the message does not appear, navigate to Devices, then click Add a new device to download the apps.
  2. Install the Code42 app on a test device.
    Customized installers should not be used for upgrade testing.
  3. Register the Code42 app under a new user account.
    If your Code42 environment uses LDAP or SSO to authenticate users, register the user in an organization that uses local authentication.
  4. Use the Code42 app to back up a small amount of data to the test Code42 server.