Skip to main content

This article applies to CrashPlan PROe version 4.

Code42 Support

Reactivated device unable to restore or resume backup

This article applies to CrashPlan PROe version 4.


This article describes a fix for a known issue that may prevent a previously deactivated CrashPlan device from being able to resume backups or restore from provider storage destinations.


Code42 environments that meet both of these criteria:

  • Have an on-premises master server running version 4.x of the Code42 platform
  • Use a provider storage destination, such as the Code42 cloud
Resolved in 4.3.0
This issue is resolved in version 4.3.0 of the Code42 platform. If possible, we recommend upgrading to version 4.3.0 or later.


This issue occurs under the following circumstances:

  1. A CrashPlan device is deactivated.
  2. The device is reactivated.
  3. The user signs in to the device and clicks Start Backup for a backup on a provider destination (for example, the Code42 cloud).
  4. The destination server appears offline or displays the message, "Destination unavailable – the backup location is not accessible."

This results in the user being unable to resume backing up or to restore previously backed up files.

Recommended solution

Before allowing the user to sign in to the device again, follow these steps to reattach the backup archive to the device:

  1. Sign in to the administration console.
  2. (Optional) If the user associated with the device is also deactivated, activate the user.
  3. Activate the device associated with the backup archive.
  4. Reattach the backup archive:
    1. Select Devices
    2. Locate and select the user's device.
    3. From the action menu, select Edit.
    4. Select Backup (or Backup Sets, if configured).
    5. From Destinations, select the destination(s) holding the device's backup archive.
    6. Click Save.

If the user already signed in to the device and is unable to back up or restore:

  1. Deactivate the device and reactivate it again.
  2. Follow the steps above to reattach the archive.
  3. Ask the user to sign in to the device again.