Skip to main content
Code42 Support

Recover your Code42 server to a previous state

Available in:

StandardPremiumEnterprise
Small Business
Applies to:

Overview

In its standard installation, a Code42 authority server uses an internal H2 database to hold its environment, configuration, and user data—everything except the backed up data from users' devices. The Code42 server backs up that database daily by dumping it to files on the server hardware. This article describes how to import a database dump and restore a damaged server to a previous state.

Affects

These instructions describe restoring an authority server that uses the default H2 database.

Considerations

Beware of losing data
Any situation that requires restoring a Code42 server includes the risk of losing data. Any changes to a Code42 server after the final database dump will be lost.

For example, users created between dumping a database and importing it will no longer exist after the import. Their devices do not back up and their archives are not maintained.

If you have questions or encounter errors, contact our Customer Champions for Code42 for Enterprise support.

Import a database dump

To import a database dump, give the import command from the administration console. If the console is not accessible, use the command-line script.

From the administration console
  1. Sign in to the administration console.
  2. Navigate to Administration > Settings > Server.
  3. From the action menu in the upper-right, select Import Database...
  4. Select the database you want to import from the chronological list of database dumps.
  5. Click Submit.
    The Code42 server restarts to import the selected database dump. This process can take several minutes.
  6. Sign in to the administration console to verify your environment.
    For example, check that Administration > Users > Active lists your users.
From the command line
  1. Open a Windows or Linux command terminal with administrative privileges.
  2. Run the authority server's restore_database script.
    The command ends with the full path and name of the dump file.
    • Linux:
      sudo /opt/proserver/bin/restore_database.sh /var/opt/proserver/dumps/proserver-db_<id_yyyy-mm-dd_hhmmss>.sql.gz
      
    • Windows:
      C:\Program Files\CrashPlan PROe Server\bin\restore_database C:\ProgramData\PROServer\dumps\proserver-db_<id_yyyy-mm-dd_hhmmss>.sql.gz
      
  3. Sign in to the administration console to verify your changes.
    For example, check that Administration > Users > Active lists your users.
To guard against data loss, every dump has duplicates
Every database dump in the dumps directory has a duplicate in every store point directory. See, for example, the default store point:
  • Linux: /var/opt/proserver/backupArchives/CrashPlanArchive_Default/dbDumps
  • Windows: C:\ProgramData\PROServer\backupArchives\CrashPlanArchive_Default\dbDumps