Skip to main content

This article applies to CrashPlan PROe version 3.

Other available versions:

Version 4icon.qnmark.png

Code42 Support

Replacing A Store Point

This article applies to CrashPlan PROe version 3.

Other available versions:

Version 4icon.qnmark.png

This tutorial explains how to replace a store point on an enterprise server. In most cases, replacing a store point is a simple matter of editing the root path in the store point configuration, then creating the store point directory on the new storage device. This procedure is used primarily to replace a failed storage device, but it can be used even if the original store point is online.

Affected versions

This tutorial applies to CrashPlan PROe master servers and storage servers at version 3.x. The menu paths and screenshots used do not apply to the earlier versions (3.8.2010 and earlier) of CrashPlan PROe.


Replacing a Store point

When replacing a store point, attach the new storage device to the storage server, then create the store point directory. If the mount path is different from the original storage, the store point configuration will need to be edited to match the new path.

  1. Log in to the administration console.
  2. Click Destinations > Store Points.
  3. Click the name of the store point to be replaced to view the store point details screen.
  4. From the Action menu, select Edit.
  5. Enter the Path to the new store point.
    • This directory must exist on the file system, and its permissions must provide the enterprise server read/write access.
  6. Near the bottom of the store point details screen, in the area labeled Store point Info, make note of the directory name.
    • For example: CrashPlanArchive_Default
  7. Create a directory with this name on the new storage device's file system.
    • It may take a few minutes for the enterprise server to recognize the new directory.
  8. Click the action menu to ensure that the store point is Enabled and that Balancing and Accept New Devices are configured appropriately for your Code42 environment.
Once the store point is back online, any previous clients will connect and restart their backups. If you have existing archives for these clients, their existing data can be seeded using the procedure below.

Seeding existing archives

If existing archives are available, either from the original store point or on another enterprise server, then it may be possible to manually seed them to the new storage. Seeding archives can save considerable time and bandwidth because the clients will not need to fully back up again to the new store point.

Replacing an existing Store Point only
Use the steps below only if you are replacing an existing store point. There are additional considerations for seeding archives to new store points.
  1. Copy the original archives to the new storage hardware, but outside of the store point directory.
  2. Stop the CrashPlan service.
  3. Move or delete any newly created archives from the store point folder.
  4. Move the original archives into the store point folder, ensuring correct file system ownership and permissions.
  5. Start the CrashPlan service.

When the clients reconnect to the enterprise server, they will first sync with the newly seeded archives. After this is complete, they will continue their backups from their previous state.