Skip to main content
Code42 Support

Decommissioning A 3.8.2010.x Environment

Applies to:
  • CrashPlan PROe
This tutorial explains how to retire and archive a CrashPlan environment running version 3.8.2010.x in preparation for starting over with the current version of CrashPlan PROe.  Archiving the legacy system allows for backup continuity and provides access to historic versions of files, should the need ever arise to restore files from the legacy backups. This process also facilitates retention and adherence to compliance requirements while user devices/endpoints start over with the 3.x/4.x CrashPlan environment for backups.

Before you begin

  • Please make sure you completely understand the concepts and processes involved in this article before beginning.
  • The storage required for the archives should be calculated and arranged before the process begins.

Considerations

  • This process only applies to 3.8.2010.x environments.
  • End user devices will be unable to access 3.8.2010.x archives through the CrashPlan app after the transition, meaning users will need to start their back ups over from scratch.
  • Unnecessary alerts and reports could be sent to users and administrators from the 3.8.2010.x PROe server when it is turned on for file restore sessions, unless proper precautions are taken (as outlined in the steps below).

Option 1: Completely new hardware for new Enterprise Server

Before you begin

This option assumes that your new CrashPlan environment will be running on completely new hardware, thus allowing you to preserve the 3.8.2010.x installation on the original hardware, including the original storage hardware.

Steps

  1. Verify the version of CrashPlan running on the PROe server by navigating to Home.
    Only follow the steps in this article if your current version is 3.8.2010 or 3.8.2010.2.
  2. Download and safeguard installation files for the server and client for future use.
    • 3.8.2010.2 and 3.8.2010 installers are available for download.
    • Download these files and keep them in a safe location.
  3. Ensure the primary and secondary IP addresses are different from the IP addresses in the new 3.x/4.x CrashPlan environment. You may edit the network settings at Settings > Edit Server Settings.
  4. From Settings > Edit Server Settings, set Retain backup archives for to 9999 days, and Maintain archives every to 999 days. This will prevent the server from removing archives for deactivated computers or running maintenance on archives automatically when it is turned back on.
  5. To prevent emailed alerts from being sent to users if the server is powered on by accident or to restore files, go to Settings > Alerts and turn off alerts to org managers and parent org managers. You may also want to delete or change emails in the Server Alert Email Addresses field.
  6. Take the PROe server offline.
  7. Completely uninstall the CrashPlan app from all endpoints. Make sure to delete the .identity file.

Option 2: Re-using server hardware

Before you begin

This option is the preferred option, and also allows you to reuse the hardware for the new CrashPlan environment.

Steps

  1. Verify the version of CrashPlan running on the PROe server by navigating to Home.
  2. Download and safeguard installation files for the server and client for future use.
    • 3.8.2010.2 and 3.8.2010 installers are available for download.
    • Download these files and keep them in a safe location! You will need to use them to reinstall the legacy PROe server software in order to restore any items from these archives in the future.
  3. To avoid potential IP conflicts during future reinstallation/recovery efforts, ensure that the primary and secondary IP addresses are different from the IP addresses in the new 3.x/4.x CrashPlan environment. You may edit the network settings at Settings > Edit Server Settings.
  4. From Settings > Edit Server Settings, set Retain backup archives for to 9999 days, and Maintain archives every to 999 days. This will prevent the server from removing archives for deactivated computers or running maintenance on archives automatically when it is turned back on.
  5. To prevent emailed alerts from being sent to users if the server is powered on by accident or to restore files, go to Settings > Alerts and turn off alerts to org managers and parent org managers. You may also want to delete or change emails in the Server Alert Email Addresses field.
  6. Perform a manual database dump at this time from Settings > Dump Database > Export the database to disk immediately.
  7. Copy the entire database dumps folder to a holding location, after verifying that the dump files are valid:
    1. Make sure that the filenames end with the file extensions .sql.gz
    2. Verify that the filesizes are non-zero
    3. Verify that the latest dump occurred within the past 24 hours
  8. Copy the desired archives to the holding location(s).
    • The easiest method is to simply save the entire volume label directory, containing all the archives for the mount point, to the holding location.
    • An example absolute path to the volume label directory: /Volumes/USB1/backups/CrashPlanPROArchive_m424765x001
  9. Take the PROe server offline.
  10. Completely uninstall the CrashPlan client from all endpoints. Make sure to delete the .identity file.
  11. You may now reuse the server hardware, or decommission the hardware for recycling or reuse, since the database dumps and archives necessary to rebuild a working server are safely stored on the holding location(s).

File recovery

Before you begin

Steps

The steps to take for restoring files will depend on whether you preserved the original installation on the original hardware (option 1), or you reused the server hardware (option 2).

Option 1: Old server is available

  1. Power on your 3.8.2010.x PROe server
  2. Restore desired files using one of two methods:
    • Web restore
      • Web restore is not recommended for large restores, and must be limited to less than the web restore limits set under Settings > General (default is 250 MB)
    • Client restore
      • Install the 3.8.2010 CrashPlan app on the device with the desired restore point (this could be the PROe server itself, or another device). Note: You can not install the 3.8.2010 CrashPlan app on a device if it is already running a more current version of CrashPlan.
      • Sign into the CrashPlan app as the desired user. If necessary, reset the user password from the console. You will also need to enter the hostname or IP address of the 3.8.2010.x master server. You can find the IP address or hostname of the master server by signing in to the admin console and going to Home.
      • Restore

Option 2: Server must be reinstalled using db dump and archives

  1. Install the required server version (3.8.2010 or 3.8.2010.2) on the target server hardware or VM, using the install files you downloaded previously. The files are also available for download:
  2. Import the database dump that was stored in the holding location:
    • Navigate to Settings > Import Database
    • Browse to the database dump file and click Save.
  3. Verify that the IP address and hostname of the master server are set to values that will not interfere with your currently running CrashPlan enterprise server(s).
  4. Connect the storage device holding the archives to the master server, and then add the mount point from Settings > Add Storage. More details on adding local storage are available on our legacy support site.
  5. Restore desired files using one of two methods:
    1. Web restore
      • Web restore is not recommended for large restores, and must be limited to less than the web restore limits set under Settings > General (default is 250 MB)
    2. Client restore
      • Install the 3.8.2010 CrashPlan app on the device with the desired restore point (this could be the PROe server itself, or another device). Note: You can not install the 3.8.2010 CrashPlan app on a device if it is already running a more current version of CrashPlan.
      • Sign into the CrashPlan app as the desired user. If necessary, reset the user password from the console. You will also need to enter the hostname or IP address of the 3.8.2010.x master server. You can find the IP address or hostname of the master server by signing in to the admin console and going to Home.
      • Restore

Locally connected archive restore option

It is possible to connect the storage device containing the archived files to be restored directly to the client device, but this option still requires that the master server be installed (or reinstalled) and available to the client. This method of restoring files may be faster, as the files to be restored do not need to traverse the network.

Considerations

This option is a form of seeding, and requires you to understand the seeding process as it works in version 3.8.2010.x.

Steps

  1. If necessary, follow steps 1 and 2 from Option 2 (install server software and import the archived database).
  2. In the CrashPlan app, go to Backup, then click the pause icon at the far right of the backup progress bar (only necessary if backup has started to the newly restored or preexisting server).
  3. From Settings > Backup > Inbound backup from other computers, set Maintain archives every to 999 days. This will prevent the client from automatically running maintenance on archives when they are attached for restore.
  4. After connecting the storage device holding the target archive to the destination device, go to Destinations > Folders, and click Select to navigate to the device and GUID folder containing the target archive.
  5. Select the GUID folder, then click OK. The Attach Backup dialog will appear, with detailed information on the location, owner, device name, device GUID, size, and last backup date of the archive. If the information looks appropriate, click OK. You should see the following message:
    • Archive successfully added!
  6. Click OK.
  7. Perform a standard restore from the CrashPlan app, by going to Restore.
Deleting the archive
Removing the local backup destination or deleting the folder containing the archive from Destinations > Folders will permanently delete the folder containing the archive.
  • Was this article helpful?