Skip to main content

This article applies to version 6.

Available in:

StandardPremiumEnterprise
Small Business
Code42 Support

Replace an existing server

This article applies to version 6.

Available in:

StandardPremiumEnterprise
Small Business

Overview

This article describes how to duplicate the authority server's state by dumping and importing its database and copying its store point and archive files when you need to reinstall an authority server or move it to new hardware.

Affects

These instructions describe shutting down and replacing an authority server that uses the default H2 database, typically in order to replace hardware.

Considerations

When you install a new authority server to replace an old one, you must:

  • Install the same version as the old server.
  • Provide the same master license key that was used to install the old server.
  • Run the new server at the same network address as the old one. 
    To use a different address, change the address at the old authority server first. For more information, see Change a Code42 server's network address.
Beware of losing data
Any situation that requires restoring an authority server includes the risk of losing data. Any changes to an authority 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.

Dump, install, duplicate, import

To replace an existing authority server with a new one:

  1. Dump data from the old authority server.
  2. Install the new server.
  3. Duplicate the old store points and device archives for the new server.
  4. Import the database to the new authority server.

Step 1: Dump data from the old authority server

From the old authority server get a list of store points, the version number, and a database dump.

  1. At the old server, sign in to the administration console.
  2. Navigate to Administration > Storage > Store Points.
  3. From the action menu in the upper-left, select Export All.
    You are prompted to save a CSV file that lists the location of your store points.
  4. Navigate to Administration > Settings > Server.
  5. Under General, note the Current server version.
    Only the first three terms are significant. For example, 6.5.0.
  6. From the action menu in the upper-right, select Dump Database.
  7. From the action menu, select Import Database...
    You see a list of dump files identified by timestamps in their filenames. Your dump is complete when you see a file named with the current date and time that ends in .sql.gz.
    • If the file extension ends in .sql, database dumps aren’t completing successfully. Contact our Customer Champions for Code42 for Enterprise support.
    • If you don't see a new dump file, click Cancel, wait 10 seconds, and select Import Database... again.
  8. When the new dump file is present, click Cancel (not Submit).
  9. From a terminal command line, stop the server with this command:
    • Linux: /opt/proserver/bin/proserver stop
    • Windows: net stop CrashPlanPROServer
    Now the old server cannot make changes that the new server won't know about, and the new server can run at the old server's address.

Step 2: Install the new authority server

  1. At the same or new hardware, install an authority server of the same version as the old one.
    Reinstalling at the same system requires first uninstalling the old server.
  2. Copy the most recent database dump from the old server to the same location at the new one.
    The timestamps in the file names indicate which is most recent.
    • Linux: /var/opt/proserver/dumps/proserver-db_<id_year-mo-da_hhmmss>.sql.gz
    • Windows: C:\ProgramData\PROServer\dumps\proserver-db_<id_year-mo-da_hhmmss>.sql.gz
To guard against data loss, every dump has duplicates
Every file 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
  1. Copy the most-recent database encryption key from the old server to the same location at the new one.
    The key is only present if your server uses automatic secure keystore. If the key is not present, skip this step.
    • Linux: /var/opt/proserver/kspDumps/ksp_<id_year-mo-da_hhmmss>
    • Windows: C:\Program Files\CrashPlan PROe Server\data\kspDumps\ksp_<id_year-mo-da_hhmmss>

Step 3: Put store points and backup archives in place

Old store points and backup archives
Before Code42 apps connect to your new authority server, have the old store points and backup archives accessible to the new server. If those archives are not in place, devices will back up to new archives, leading to data loss.  

Depending on your server and storage hardware and the connection between them, you have the following options:

Option 1: Relocate store points and archives to match the old database imported to the new server

  1. Move existing store points to new locations that match the paths recorded in the file you downloaded in Step 1 above: StorePoints_<yearmoda-hhmmss>.csv. See the field, absolutePath.

Archives are large complex files. If you need to copy them, use a robust command-line tool like Windows robocopy or Linux rsync. In a terminal window, issue commands like the following:

robocopy <source> <destination> /COPYALL /PURGE /MIR

sudo rsync -ah --progress --delete --compress-level=0 --inplace <source> <destination>

  1. Verify the store points and archives provide read, write, and execute permissions to the new server. Match the ownership and privileges of the new server's default store point.
  2. Proceed to Step 4 and Step 5.

Option 2: Adjust the server database to look for store points and archives in a different location

Instead of, or in addition to, moving store point and archive files, you can:

  1. Use firewall configuration to isolate the new authority server from your Code42 apps.
  2. Verify the store points and archives provide read, write, and execute permissions to the new server. Match the ownership and privileges of the new server's default store point.
  3. Import the old database to the new server, as in Step 4.
  4. Redefine store points to match the existing locations, as in Step 5.
What is a store point?
A store point is a directory on a file system. A store point holds one or more directories named with an 18-digit number. Those are the archives that hold backed-up data, one archive for each device. The default store point is:
  • Linux: /var/opt/proserver/backupArchives/CrashPlanArchive_Default
  • Windows: C:\ProgramData\PROServer\backupArchives\CrashPlanArchive_Default

Step 4: Import the database

With store points and archives in place and the new authority server isolated from Code42 apps if necessary, duplicate the old authority server's configuration by importing a database dump.

  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 dump you copied from the old server.
  5. Click Submit.
    The Code42 server restarts. 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.

Step 5: Verify or redefine store points

Make sure that the store points defined in your authority server match the store points in your file system, and that your server has access to them.

  1. At the new authority server, sign in to the administration console.
  2. Go to Storage > Store Points.
  3. One at a time, select a store point to review its details.
  4. Confirm that the Path and Directory exist on the file system. If not:
    1. In the upper-left, click action menu > Edit...
    2. Change the Path.
    3. Click Save.

Step 6: Verify Code42 app connections

  1. Reverse any firewall changes that block Code42 apps from connecting to the new authority server.
  2. In the new administration console navigate to Administration > Devices > Active.
    Your endpoint devices should be listed.
  3. Test one or more device archives by restoring a sample of data.