Skip to main content
Code42 Support

Replacing An Inaccessible Store Point

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

This tutorial explains how to replace a store point that has become inaccessible due to hard drive failure, store point failure, or other causes. As part of this process, Code42 for Enterprise archives from the inaccessible store point must be reassigned to a replacement store point.

To move a store point that is still accessible, see Moving A Store point.

Considerations

Potential data loss
Ensure that the inaccessible store point is not recoverable before proceeding. Reassigning an archive to a new store point starts a new archive. Previously backed up files, version history, and files deleted from the endpoint after being backed up will be lost.

Before you begin

Since data loss could occur, perform all possible troubleshooting measures to recover the inaccessible store point before starting this process. Also, good planning can prevent unexpected hardware and network events and changes that may take a Code42 server or store point offline.

You can contact our Customer Champions if you have questions about recovering your inaccessible store point.

Step 1: Decommission the inaccessible store point

  1. Navigate to Storage > Store points.
  2. Click the inaccessible store point.
    Action menu options for the inaccessible store point
  3. From the action menu, select Pause Activity to prevent the store point from accepting data.
  4. From the action menu, select Reject New Archives to prevent the store point from accepting new archives.
  5. From the action menu, select Disable Balancing.

Step 2: Prepare the replacement store point

  1. Navigate to Storage > Store points.
  2. Click the store point where archives and devices will be reassigned.
  3. From the action menu, select Accept New Archives to configure the store point to accept new archives.
  4. From the action menu, select Enable Balancing.

Step 3: Reassign archives to the replacement store point

  1. Go to Storage > Store points.
  2. Click the value under the Stored column for the inaccessible store point to open its Archives.
    This list contains the stranded archives that are available for reassignment.
    Stranded archives on the inaccessible store point
  3. Select the archives you wish to reassign.
  4. From the action menu, select Reassign Archive.
  5. Type Agree when prompted by the warning message.
    • The message Archive reassignment started briefly appears in the lower left of the administration console.
    • The Code42 server's data balancing engine reassigns the affected archives to any available good store points.
    • The reassignment process may take several minutes.
  6. Once completed, navigate to Storage > Store points to verify that no remaining data is stored on the inaccessible store point.

Step 4: (Optional) remove the inaccessible store point

After you verify that the archives have been moved, and the device GUIDs are reassigned to functional store points, you may remove the inaccessible store point:

  1. Navigate to Storage > Store points.
  2. Click the inaccessible store point.
  3. From the action menu, select Remove.
  4. Select Remove, even if files are still present, then click Remove.
    A message in the lower left of the administration console confirms that the store point was successfully removed.

Step 5: Confirm that devices can back up

To verify that the reassignment process was successful, you may confirm from the CrashPlan app that one of the affected devices is now able to back up. The destination affected by the inaccessible store point should be online (as shown by the green status icon) and the backup process should be underway or complete.Verifying that an affected CrashPlan client is now able to back up