Skip to main content
Code42 Support

Code42 Server Command Line Tools

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

All Code42 server installations contain a collection of command line tools and utilities that can perform various administrative tasks. This reference guide details the tools and utilities available to you.

Location

These tools are contained in the bin directory of your Code42 server installation:

  • Linux: /opt/proserver/bin
    Applies to Code42 servers installed as root on Ubuntu
  • Windows: C:\Program Files\CrashPlan PROe Server\bin

You must run all scripts from the bin directory as the user that owns the Code42 server process. On Windows, this means running the scripts from a command prompt with administrator permissions.

Reset admin credentials

Use the reset_admin_credentials tool to reset the username and password for the local administrator account to their default values:

  • Username: admin
  • Password: admin
Change default credentials
After resetting the local administrator account's credentials, we strongly recommend you change the password for security reasons.

Usage

  • You must run the reset_admin_credentials tool as the user that owns the Code42 server process.
  • For security reasons, the reset_admin_credentials tool requires a single parameter containing the first four or more characters of the master license key used during the initial installation of your Code42 server. If your master license key has changed, you must use the original master license key to reset credentials.

Linux

  1. On your Code42 server's file system, open a command-line interface, such as Terminal.
  2. Navigate to the bin directory.
  3. Run the reset_admin_credentials tool with administrative credentials and the first four (or more) characters of your master license key:
    sudo ./reset_admin_credentials.sh <MLKcharacters>

Windows

  1. On your Code42 server's file system, open a command-line interface, such as PowerShell, with administrative privileges.
  2. Navigate to the bin directory.
  3. Run the reset_admin_credentials tool with the first four (or more) characters of your master license key:
    reset_admin_credentials.bat <MLKcharacters>

Example

Input on Linux

sudo ./reset_admin_credentials.sh InGI

Output

user:bin user$ sudo ./reset_admin_credentials.sh InGI
Password:
Shutting down PROe Server...
CrashPlanPROServer unloaded cleanly.
Resetting admin credentials

Attempting to load config from /Applications/PROServer.app/Contents/Resources/Java//conf/conf_proe.groovy, /Applications/PROServer.app/Contents/Resources/Java//conf/conf_proe.mac.groovy, /Applications/PROServer.app/Contents/Resources/Java//conf/conf_proe.properties
  config loaded
[06.26.12 11:00:22.418 INFO    main                 root                                    ] logPath: /Library/Logs/PROServer
Configuring environment ...
  registering an appropriate driver
  retrieving connection specifications
  JDBC URL: jdbc:h2:/Library/Application Support/CrashPlan/PROServer//db/proserver;IFEXISTS=TRUE;DEFAULT_LOCK_TIMEOUT=30000;WRITE_DELAY=0;ACCESS_MODE_DATA=rwd;DB_CLOSE_ON_EXIT=FALSE
  retrieving connection credentials
  opening a connection
Examining master license key fragment ...
  key fragment validated
Resetting administrator credentials ...
  attempting update
  proper update detected, committing changes.
Reset completed normally
Starting PROe Server...
  71166 ??         0:16.09 /usr/bin/java -Dapp=CrashPlanPROServer -Dprogram.name=CPServer -Xss128k -XX:PermSize=256m -Xms256m -Xmx1024m -XX:+UseAdaptiveGCBoundary -XX:+DisableExplicitGC -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Ddrools.compiler=JANINO -Dfile.encoding=UTF-8 -server -classpath lib/com.backup42.app.jar com.code42.core.impl.Core -prop conf/conf_proe.properties -config conf/conf_proe.groovy -config conf/conf_proe.mac.groovy

Restore database

The restore_database tool rebuilds a Code42 server's database based on a database dump file and, optionally, a supplementary recovery log. The tool is designed to assist with recovery following system or hardware failure or for moving a Code42 server installation from one machine to another.

Usage

Using restore_database is a complex operation. For detailed usage instructions, see Recovering Your Code42 server To A Previous State.