Skip to main content
Code42 Support

Moving A Store Point

Available in:

  • CrashPlan PRO
    • Standard
    • Premium
    • Enterprise
Applies to:

Overview

This tutorial explains how to move the data of an online store point to a new location on the Code42 server's file system. You may need to move a store point if:

  • The drive or volume that hosts the store point is running out of space, and you are not using data balancing.
  • The drive or volume that hosts the store point is showing signs of imminent failure.

This process moves store point data within the Code42 server; it does not move the store point to a different Code42 server. To move archives to a different Code42 server, see Migrating Archives Between Store points.

If your store point is inaccessible, see Replacing An Inaccessible Store point.

Considerations

  • Archives on the store point are not accessible while it is being moved.
  • The storage server must have read/write access to the volume or directory that contains the store point data.

Before you begin

Review the existing storage hierarchy of your Code42 environment.

Step 1: Prepare the new storage location

Set up storage on the Code42 server to host the store point data:

  1. If necessary, add new storage to the storage server:
    1. Attach a new storage device to the storage server.
    2. Create a file system on the storage device.
    3. Mount the file system.
  2. Create a directory for the store point.
    • This directory corresponds to the store point Path in the administration console.
    • You do not need to create a directory if you want the store point data to reside at the root of the drive or volume.
  3. Verify that the new storage location has enough space to hold the store point data.

Step 2: Prepare the Store point

Deactivate the store point so that you can copy the data:

  1. Sign in to the administration console.
  2. Navigate to Storage > Store Points.
  3. Select the store point.
  4. From the action menu, select Pause Activity.
  5. From the action menu, select Reject New Archives.
  6. From the action menu, select Disable Balancing.
  7. In the area labeled Store point Info, make note of the Path.

Step 3: Move the Store point data

Copy the directories located in the store point's path to the new path. For example:

  • CrashPlanArchive_m74758225239x002
  • CrashPlanArchive_SEED
  • CrashPlanArchive_REVIVE
Use command-line tool to copy data
We recommend using a command-line tool like rsync (Linux) or robocopy (Windows) to copy data. These tools are designed to handle large transfers without failing.

Recommended rsync options

If your Code42 server runs Linux, run the following command to move the store point data:

rsync -ah --progress --compress-level=0 --inplace <source> <destination>
  • Replace <source> with the existing store point path.
    Do not include a trailing slash in the path.
  • Replace <destination> with the new store point path.

Recommended Robocopy options

If your Code42 server runs Windows, run the following command to move the store point data:

robocopy <source> <destination> /COPYALL /PURGE /MIR
  • Replace <source> with the existing store point path.
  • Replace <destination> with the new store point path.

Step 4: Configure the Store point to use the new storage location

  1. In the administration console, navigate to Storage > Store points.
  2. Select the store point.
  3. From the action menu, select Edit.
  4. Enter the new Path to the store point.
  5. Click Save.
    It may take a few minutes for the Code42 server to recognize the new directory.
  6. From the action menu, select Resume Activity.
  7. From the action menu, select Accept New Archives.
  8. From the action menu, select Enable Balancing.

Once the store point is back online, any previous devices will connect and resume backing up and syncing.

  • Was this article helpful?