Skip to main content
Code42 Support

Cold storage

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)


Cold storage is a temporary storage state for data that is not actively being used by the Code42 environment. These archives have been deactivated but not yet completely deleted.

Proper use and configuration of cold storage can help you manage your Code42 CrashPlan (previously CrashPlan PROe) archives, recover data from deactivated archives, and plan for compliance with policies and regulations that affect your organization.


The terms below are used throughout this article.

cold storage

Temporary holding state for archives after they are deactivated, but before they expire and are permanently deleted. This is analogous to the period when a deleted file remains in the Recycle Bin or the Trash. Users who have backup archives in cold storage consume a user license. Administrators can retrieve archives from cold storage if the archives were backed up to a private cloud or hybrid cloud destination.


Applies to devices, users, and organizations. Deactivation stops backup and causes associated archives to be placed into cold storage and eventually deleted. Licenses are not immediately freed by deactivation.

store point

A storage location within a server that can store archives. The lowest level in the Code42 environment storage hierarchy.

Basics of cold storage

When a user, device, or plan is deactivated, its data is not deleted; it is moved into cold storage.

The Code42 environment does not interact with data that is stored in archives in cold storage. The archives themselves can be moved between store points by the data balancing process, but the Code42 server does not read, write, or modify any data within the archives.

Intended use of cold storage

Cold storage is most often used for these reasons:

  • Preventing Accidental Deletion - The cold storage period gives administrators time to respond in case a user, device, or plan is deactivated accidentally.
  • Providing A Deactivation Grace Period - When a device is deactivated, its archive is placed into cold storage. This makes it easier to adopt this archive from a new device without the risk of data loss.
  • Preserving Data For Legal Holds - Enterprise regulations and policies may require archival data to be maintained for certain periods of time, especially in the event of employee departure.

States of archive storage

Active archive

When a device begins backing up with Code42 CrashPlan, its data is stored in an archive. Archives remain active even if the device is disconnected from the network, powered off, or otherwise separated from the storage device (usually a Code42 server or an external drive).

Archives are considered active until an administrator takes action to deactivate them.

Cold storage retention period

The amount of time archives are kept in cold storage depends on your deployment type:

  • Deployments with an on-premises master server (private cloud, hybrid cloud, and public cloud with keys on premises): 365 days, by default. This setting can be configured in the administration console.
  • Public cloud deployments with hosted keys: 14 days. This setting is only configurable if you disable inheritance in Organization Settings. See the Organizations Reference for more information.

While archives are in cold storage, they are not monitored by the automatic archive maintenance process.

After retention period

When an archive's cold storage retention period is over, it becomes an expired archive.

Effects of cold storage

Archives in cold storage remain on the store point, but they are not affected by most operations of the Code42 environment.

The lists below are not exhaustive to all server operations, but rather examples of the types of operations that do and do not affect archives in cold storage.

Server operations that affect archives in cold storage

  • Data balancing across store points
  • Countdown timer to the end of the cold storage retention period

Server operations that do not affect archives in cold storage

  • archive validation
  • archive healing
  • de-duplication
  • removing files due to updated versioning settings
  • removing files due to updated file exclusion settings

Configure cold storage

Change cold storage duration

You can change the cold storage retention period for your entire Code42 environment or only for specific organizations.

There is no practical upper limit on the duration you can choose for cold storage, but you may find other limitations in your environment, such as available storage space on your store points.

To view or modify cold storage settings at the system-wide level of your Code42 environment:

  1. Sign in to the administration console.
  2. Go to Settings > Organization.
  3. If needed, enter a new value in Move deactivated archives to cold storage for.
  4. Click Save.

To view or modify cold storage settings for a specific organization:

  1. Sign in to the administration console.
  2. Go to Organizations and select an organization.
  3. From the action menu, select Edit.
  4. If needed, enter a new value in Move deactivated archives to cold storage for.
  5. Click Save.

You can review each organization's cold storage retention policy from Settings > Organization.

Disabling inheritance
If inheritance is disabled for an organization, that organization is not affected by changes to its parent organization.

Disable cold storage

You can disable cold storage entirely by changing the cold storage retention period setting to 0 days.

Remove data from cold storage

To remove a backup archive from cold storage before the end of the cold storage retention period, you can purge the archive from cold storage.

Purged archives
Archives purged from cold storage are permanently removed, and associated data is unrecoverable.

For detailed information on removing data from cold storage, see Purge cold storage

Manage space used by cold storage

Archives in cold storage continue to take up storage space on your store point. You have a number of options for dealing with archives if space becomes an issue for your Code42 environment, as described in Managing Space When Disk Runs Low.

Expired archives

Once an archive has been in cold storage for the time of its cold storage retention period, the archive expires. Archive expiration represents a short, additional buffer between recoverable archives and permanent deletion. Expired archives are kept for 20 days (by default), then permanently deleted.

By default, expired archives remain on the store point for 20 days, but this setting can be configured in Settings > Server (private cloud deployments only).

Expired archives are no longer managed by the Code42 environment. This means that an expired archive consumes space on the store point's disk, but this space is not reported by the Code42 server in disk use reports. Also, an expired archive does not consume a license.

After the expired cold storage archives period, archives are deleted (or securely deleted, if that option is enabled). After an archive is deleted, the data is not recoverable.

Archive names after expiration

When a backup archive expires, it is renamed on the store point's file system with the following format:
For example, an archive with the GUID 123456789012345678 would appear on the store point's file system as 123456789012345678.EXPIRED.2013-09-07_020832 after it expired. That archive would not appear at all in the administration console, because expired archives are no longer managed by the Code42 environment.

Reactivate an expired archive

To reactivate a device whose archive has expired, but not yet deleted:

  1. Activate the device.
  2. Change the name of the archive on the file system to its GUID, without the additional text appended when the archive expired.
    See Archive Names After Expiration for details.
  3. Seed the expired archive to your own private cloud.

Simply reactivating a deactivated device does not automatically reassociate an expired archive to the device.

  • Was this article helpful?