Skip to main content

This article applies to Code42 CrashPlan version 5.

Other available versions:

Version 6 | Version 4icon.qnmark.png

Code42 Support

Seed archives to your private cloud

This article applies to Code42 CrashPlan version 5.

Other available versions:

Version 6 | Version 4icon.qnmark.png


Backing up devices to a remote storage destination for the first time can require excessive amounts of network bandwidth. To increase efficiency, you can create the initial backups at a local destination, then transfer (or "seed") the archives to the remote location on a portable drive. Endpoint devices then connect to the remote destination and resume backing up, but consume significantly less bandwidth because they are only transporting changes, not entire files.

You can also use seeding to transfer archives from one store point to another if, for example, a storage server fails and you must move archives to a new store point.


  • You can only seed archives if your Code42 environment uses the private cloud architecture. If your Code42 environment uses managed appliances, contact Professional Services to seed archives.
  • Seeding is intended primarily for a device's initial backup. The seeding process completely overwrites any data previously backed up for each device used in the seeding process.
  • You can seed archives between any store point in your Code42 environment, regardless of the storage server or destination. Cross-destination seeding requires that you first offer the target destination to the organization in which the user resides.
  • When copying backup archives, always verify the copy operation using checksums or another verification method.
  • Only users with the admin.system.command permission are allowed to configure the seeding settings described in this article. The following default user roles contain this permission:
    • Server Administrator
  • When seeding and reviving an archive, the archive's organization and user must be active (not deactivated). If the organization and user for that archive are deactivated, the seed and revive process fails.

How seeding works

Seeding uses an existing archive from one destination to back up to a second destination. The first destination is usually a local destination, such as a local Code42 server or an external hard drive attached to the device. The second destination is usually a remote Code42 server.

Store point seeding directories

Administrators place an archive in one of two seeding directories that reside on each store point inside the store point's path. Both directories process active archives in the same way, but they process deactivated archives differently:

  • CrashPlanArchive_REVIVE reactivates deactivated archives.
  • CrashPlanArchive_SEED does not reactivate deactivated archives.

The Code42 server periodically checks each store point for archives in these seeding directories. When the Code42 server finds archives in the seeding directories, it:

  • Moves the archives to the main archive storage directory on the store point. Archives are moved, not copied.
  • Performs archive maintenance on the archives.
  • Reactivates any deactivated archives in the CrashPlanArchive_REVIVE directory.

Locate the seeding directories

The seeding directories are located inside the path of each store point. To locate the seeding directories on any store point:

  1. Sign in to your administration console.
  2. Navigate to Destinations > Store Points.
  3. Select the store point.
  4. Note the directory listed as the Path:Store point path

Default store point locations

  • Linux: /var/opt/proserver/backupArchives
    Applies to Code42 servers installed as root on Ubuntu
  • Windows: C:\ProgramData\PROServer\backupArchives
  • OS X: /Library/Application Support/CrashPlan/PROServer/backupArchives

Before you begin

Before you begin the seeding process, verify that:

  • The seeding destination has enough space for all the seeded backup archives
  • The seeding destination is offered to the devices you are seeding


Step 1: Prepare seeding notifications

  1. Sign in to the administration console on the Code42 server that you want to seed to.
  2. Specify an email address to receive notifications of seeding success or failure:
    1. Double-click the logo in the upper-left corner of the administration console to open the administration console CLI.
    2. Set the property by issuing the following command:
      prop.set save

      Setting system property for

Step 2: Copy the seed archives

  1. Create the seed archives by backing up the devices to a local destination.
    The local destination is any destination whose file system you can access, such as an external hard drive, another device, or a Code42 server.
  2. (Optional) At the remote destination, create a staging directory for seeding to avoid any accidental operation on the active archive. Prepare the staging directory on the same volume as the seeding directories.
  3. Stop backups on the local destination.
  1. Copy the seed archives from the local destination to the staging directory on the remote destination.
    Copying data
    We recommend using a command line tool like rsync (OS X, Linux) or robocopy (Windows) to copy data. These tools are designed to handle large transfers without failing.
    Alternatively, you can copy the seed archive to a removable drive, then ship that drive to the remote destination.
  2. Start backups on the local destination.
  1. Move the seed archives into one of the two seeding directories below:
    • CrashPlanArchive_REVIVE
    • CrashPlanArchive_SEED
  2. 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.

Step 3: Confirm seeding success

Navigate to Devices in the administration console to view the seeded devices, confirming that the seed process is complete.