Who is this article for?
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
Backing up large amounts of data over the Internet or other bandwidth-constrained networks can saturate your connection or negatively impact other network activity. To avoid this, seed your archives to the file system on a enterprise server in your Code42 environment.
Seeding is used to quickly start a backup on a remote destination by transporting an existing archive via a portable hard drive or local network. Subsequent backups, which perform de-duplication and send only changed data, are much faster.
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 enterprise server or an external hard drive attached to the device. The second destination is usually a remote enterprise 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 enterprise server periodically checks each store point for archives in these seeding directories. When the enterprise 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.
Locating the seeding directories
The seeding directories are located inside the path of each store point. To locate the seeding directories on any store point:
- Sign in to your Code42 console.
- Navigate to Destinations > Store points.
- Select the store point.
- Note the directory listed as the Path:
Default Store point locations
- Linux: /var/opt/proserver/backupArchives
Applies to enterprise servers installed as root on Ubuntu
- Windows: C:\ProgramData\PROServer\backupArchives
- OS X: /Library/Application Support/CrashPlan/PROServer/backupArchives
- You can only seed archives if your Code42 environment uses the private cloud architecture. If your Code42 environment uses managed appliances, contact PRO Services to seed archives.
- Seeding is intended for a device's initial backup only. The seeding process completely overwrites any data previously backed up for each device used in the seeding process.
- 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
- Seeding and reviving (using the CrashPlanArchive_REVIVE directory) is available only in version 4.2 and later of the Code42 platform.
- 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.
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
- Sign in to the Code42 console on the enterprise server that you want to seed to.
- Specify an email address to receive notifications of seeding success or failure:
- Double-click the logo in the upper-left corner of the Code42 console to open the Code42 console CLI.
- Set the
c42.seed.emailproperty by issuing the following command:
prop.set c42.seed.email firstname.lastname@example.org save
Step 2: Copy the seed archives
- 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, a enterprise server, or another CrashPlan device.
- (Optional) At the remote destination, create a staging directory for seeding to avoid any accidental operation on the active archive.
- Prepare a staging directory on the same volume as the seeding directories.
- Copy the seed archives from the local destination to the staging directory.
- Move the seed archives into one of the two seeding directories below:
- Wait for the enterprise server to process the seeded archives.
It may take up to 10 minutes for the enterprise 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 Code42 console to view the seeded devices, confirming that the seed process is complete.