Move a store point
Who is this article for?
Incydr, no.
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
This article applies to on-premises authority servers.
Overview
This tutorial explains how to move 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.
You can move a store point to a location in the same storage server or a different storage server in the same destination, but you cannot move the store point to a different destination.
To move archives to a different store point, see Migrate archives between store points. If your store point is inaccessible, see Replace 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:
- If necessary, add new storage to the storage server:
- Attach a new storage device to the storage server.
- Create a file system on the storage device.
- Mount the file system.
- Create a directory for the store point.
- This directory corresponds to the store point Path in the Code42 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.
- 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:
- Sign in to the Code42 console.
- Navigate to Storage > Store Points.
- Select the store point.
- From the action menu, select Pause Activity.
- From the action menu, select Reject New Archives.
- From the action menu, select Disable Balancing.
- 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
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
- In the Code42 console, navigate to Storage > Store Points.
- Select the store point.
- From the action menu, select Edit.
- Enter the new Path to the store point.
- Click Save.
It may take a few minutes for the Code42 server to recognize the new directory. - From the action menu, select Resume Activity.
- From the action menu, select Accept New Archives.
- 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.