Skip to main content

This article applies to version 6.

Other available versions:

Version 5icon.qnmark.png

Available in:

StandardPremiumEnterprise
Small Business
Code42 Support

Preserve deactivated archives

This article applies to version 6.

Other available versions:

Version 5icon.qnmark.png

Available in:

StandardPremiumEnterprise
Small Business

Overview

When an administrator deactivates Code42 app users, the Code42 platform retains their archives until the administrator purges them or until they expire from cold storage. In either case the archives are permanently lost. To preserve archives, copy archive files before purging or expiration. This article explains how to find, copy, and preserve backup archives from deactivated users.

Considerations

Archives outside the Code42 platform are not supported
Archives outside of the Code42 environment do not undergo maintenance, and therefore there is no guarantee that the integrity of the data is retained. No alerts are generated about problems with these archives (for example, corruption or data loss), and the point at which you would encounter issues is at the time of archive recovery.

Therefore, Code42 does not support archives that exist outside of the Code42 environment. The following steps are provided as a convenience and do not constitute an agreement for support. Undertake these steps at your own risk.

Copy archives from cold storage to local storage

The backup archives of deactivated users go into cold storage for a given retention period. Unless an administrator purges the archives from cold storage, the archives then become expired.

Before archives are purged or expire, an administrator can copy them to a location outside the Code42 platform to preserve them. Compliance policies may require preserving archives in this way.

Code42 does not back up copies of archives
The Code42 app does not back up copies of Code42 archives. The administrator is responsible for maintaining archives copied out of Code42 cold storage.

For details on how archives consume subscriptions, see Cold storage subscription usage.

Step 1: Identify the archives to preserve

A deactivated user has one or more devices, and each device has a separate backup archive. To find the archives, generate a report:

  1. Sign in to the administration console.
  2. Select Administration > Users.
  3. (Version 6.5 and later) Select Deactivated.
    (Version 6.0.x) From the action menu, select Show Deactivated.
    The display now shows only deactivated users.
  4. Click the Device Report icon device report icon.
    A new browser window opens.
  5. From the menu Device Status, select Deactivated.
  6. Click Run Report.
    The report now includes only deactivated archives.
  7. Click the action menu, and select these fields:
    • Archive GUID
    • Cold Storage
    • Destination Name
    • Device Name
    • Server Name
    • Username
  8. Click OK.
  9. Record the data for those users and devices whose archives you want to preserve.
    For large numbers of users, click Export All As CSV, then use a spreadsheet tool.

Step 2: Locate the store points for those archives

To learn where archives are stored, first understand the Code42 storage hierarchy:

  • Users send backup data to one or more destinations.
    • Each destination has one or more storage servers.
      • Each storage server has one or more store points. A store point is a file path on the server's host machine.
        • An archive is a directory on a store point. Its name is one of the Archive GUIDs you retrieved in Step 1 above.

To locate the store points you want to copy archives from:

  1. Sign in to the administration console.
  2. Select Storage > Destinations.
  3. Click the expander icons to navigate through each of the destinations and servers named in the data you retrieved in Step 1.
  4. Click on each store point name.
    The store point details display.
  5. For each store point, record the Path and Directory name.

Store point information

Step 3: Locate and copy archive directories

Copy your archives to a new location to preserve them. The Code42 app is not able to back up the copies.

  1. Open the terminal or Finder on the storage server's host system.
  2. Navigate to the /path/directory pairs you recorded in Step 2.
  3. Look for directories that match the archive GUIDs you recorded in Step 1.

For archives in cold storage, paths are in the form:

/<storePointPath>/<storePointDirectory>/<ArchiveGUID>

For expired archives, paths are in the form:

/<storePointPath>/<storePointDirectory>/<ArchiveGUID>.EXPIRED.<timestamp>
  1. Copy those directories and everything in them to a new location.
    Store point files can be large. For copying them, we recommend a tool like rsync or robocopy.

Restore deactivated archives

Use a seeding directory to restore the deactivated archives.

Restore considerations

  • Although seeding to restore deactivated archives is an unsupported process, this article provides information that some administrators may find useful.
    Nonstandard process
    The information presented here describes a configuration that some users have successfully implemented, but that are outside the scope of normal support. Our Customer Champions cannot assist you with tasks outside normal support, so you assume all risk of unintended behavior.

    However, you might find additional support from other users in our forums: Code42 for Enterprise use the Code42 customer community and CrashPlan for Small Business use the support forum. Code42 for Enterprise customers, you can also contact your Customer Success Manager (CSM) at csmsupport@code42.com to engage the Code42 Professional Services team.
  • This process fails if the following has occurred while the archive is stored outside of the Code42 system:
    • The authority server or storage server has been upgraded.
    • The device to which the archive belongs has been reactivated and given a new archive.

Before you begin 

Before seeding deactivated archives, you must ensure the following to prevent data loss:

  1. Update your version retention to ensure that none of the following values are set to Never:
    • Last week
    • Last 90 days
    • Last year
    • Previous years
  2. Reactivate the target device and ensure that the destination on which you'll be performing the seeding process is offered to the user. If you seed to a location for which the device is not authorized for backup, the process fails.

Steps

  1. Copy the archives into the CrashPlanArchive_REVIVE directory on your server:
    • Linux: /var/opt/proserver/backupArchives/CrashPlanArchive_REVIVE
    • Windows: C:\ProgramData\PROServer\backupArchives\CrashPlanArchive_REVIVE
    Copy the archive
    Do not move the archive to the seed directory. Use a copy to prevent data loss in the event that something goes wrong. 
  1. Wait for the Code42 server to process the seeded archives.
    It may take up to 10 minutes for the Code42 server to begin moving the archives from the seeding directory to the main archive storage directory.
  2. Reattach the deactivated archive to the target device.
    Seeding to an existing active device
    If you seed an archive to an existing active device, its current archive is overwritten.