Skip to main content
Code42 Support

Converting On-Premises Storage To Cloud Storage

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

This tutorial explains how to convert your Code42 environment from using local destinations (store points and Code42 servers in your own on-premises datacenter) to using only cloud destinations from Code42. Doing this allows you to continue to:

  • Maintain the onsite master server
  • Keep the encryption keys on-premises, behind a firewall

Before you begin

You should be familiar with the following terms.

  • Destinations:

    (1) General term applied to locations to which your files are backed up: your server, an external drive, or with online hosted storage.
    (2) Highest level in the Code42 environment storage hierarchy. A named grouping of Code42 servers and store points on a single LAN or at a single data center.

  • Storage server:

    A type of Code42 server. A storage server is used only for storage in multi-server deployments. A storage server cannot function as a failover for an master server. A storage server depends on user authorization provided by the master server.

  • Store point:

    A storage location within a server that can store archives. The lowest level in the Code42 environment storage hierarchy.

Considerations

To plan for removal of store points from a Code42 server, or removal of a destination with attached store points, you must take into account the following.

  • Data loss occurs when store points and destinations are removed. Make sure the end users' computers have fully backed up to the new cloud destination before removing the old store point or destination, and that you are retaining your users' data according your organization's data-retention policy.
  • A store point can be removed only when:
    • All archives on the store point have been deleted and purged.
    • All organizations and users have been disassociated from the store point.
    • All archives in cold storage have been purged manually.
  • A destination can be removed only when:
    • All devices and organizations have stopped backing up data to the destination.
    • The destination is no longer offered for storage.
Follow this tutorial closely
This process has the potential to destroy data. Because of this destructive potential, plan ahead and take care when following this tutorial.

If you have questions about this process, contact our Customer Champions for Code42 for Enterprise support.

Step 1: Add the Code42 cloud as a destination

Add the Code42 cloud as a destination to your Code42 environment. You will need the provider key. Contact your Customer Success Manager (CSM) for enterprise support at csmsupport@code42.com to get the provider key.

Step 2: Confirm devices use the cloud destination

Confirm that your organizations and users use the new cloud destination.

  1. Sign in to your administration console.
  2. Go to Settings > Organization.
  3. Select Destinations and verify that the checkbox next to the cloud destination is enabled.
    Organization destinations
  4. Go to Settings > Device Backup.
  5. Select Backup and in the Destinations section, select the Auto-start checkbox.
    After you select the checkbox, its label changes to Use.
    Device default backup destination
  6. Select push icon to push the change to your devices. You may also lock the setting on this screen.
  7. Click Save.
  8. If you have child organizations that do not inherit settings from their parent organizations, update each organization's destinations individually.
    1. Go to Organizations and click on an organization name.
      The organization details appear.

    2. Click on action menu and choose Edit.

    3. Select Destinations.

    4. Select the cloud destination to offer it to the devices in the child organization.

    5. Click Save.
      organization backup destination

  9. Sign in to a test user's CrashPlan app.
  10. Click Details and confirm the device is backing up to the cloud destination.
    Backup destinations

Step 3: Stop using local store points (optional)

This step is only necessary if you want to stop using any local storage attached to the master server in preparation for permanently removing the local store points.

  1. Go to Storage > Store Points
  2. Select each store point you wish to stop using.
  3. Click the action menu gear menu, and choose Reject New Archives.
  4. If you have another store point in the local destination that you want to migrate the archives to, you can migrate the archives off the store point to be removed.

Step 4: Stop offering the local destination

Stop offering the local destination to make sure all backups are only sent to your cloud storage.

Wait until cloud backups are completed
If you are keeping the backup archives on a local destination until the backups to the new cloud storage are finished, wait to do this step until all backups to the cloud destination have completed.
  1. Go to Settings > Organization > Destinations and deselect the local destination.
    The Remove Destination From Org warning appears.
  2. Type "I AGREE" and click OK.
    remove destination from org
    The archives that were stored in the selected destination are placed into cold storage.
  3. For any child organization that does not inherit settings from its parent organization:
    1. Go to Organizations, and select the organization.
    2. Click the action menu, and choose Edit.
    3. Click Destinations, and deselect the local destination.
    4. Type "I AGREE" and click OK.
      The archives that were stored in the selected destination are placed into cold storage.

Step 5: Purge the archives in cold storage (optional)

This step is optional. You must purge the archives if you wish to remove the store points and/or destinations permanently.

Data retention Policy
You may need to keep the local store points and destination online until your data-retention policy allows you to permanently delete the archives. Those original, local archives contain file versions and deleted files that the new archives in cloud storage do not have.

If you are sure that you want to delete the local store points, follow these steps.

  1. Go to Storage > Store Points and click the number in the Cold column.
    Cold storage
    A list of archives in cold storage appears.
  2. Click the top left checkbox to select all archives in cold storage on this store point.
    Note: You must remove all archives to remove the store point.
  3. From the action menu select Purge Archive.
    The Purge Archives warning appears.
  4. Click OK to immediately delete the cold storage archives.

Step 6: Remove the Store point

  1. Go to Storage > Store Points
  2. Select a store point.
  3. Select the action menu, choose Remove.
    remove store point
  4. In the Remove Storepoint message box, select Remove, even if files are still present, then click Remove.

This removes the local store point and all associated archives, users, and devices. Continue to steps 7 and 8 to remove the local storage server and destination.

Step 7: Remove Storage server (optional)

This is an optional step that only applies to certain Code42 environments:

  • A storage server was providing non-cloud storage.
  • You want to stop using that storage server after the move to cloud storage.

You need to remove any storage servers that are contained in a destination you want to remove. Alternatively, you can move the storage server to a different destination.

To permanently remove the storage server (after completing steps 3-6 above for the storage server):

  1. Go to Storage > Servers.
  2. Select a server.
  3. Click the action menu, and choose Remove.
    The Successfully removed storage server message appears.

Remove storage server

Step 8: Remove the destination

After moving to cloud storage, you may remove destinations that are no longer needed. You must first move any attached storage servers to another destination, or remove the storage server. However, you may not remove the default destination for the master server.

For example, a destination that contained a storage server that was on your LAN may no longer be needed after the move to the cloud. In that case, repeat steps 3-7 above for each local storage server that is no longer needed after the move to cloud storage.

  1. Go to Storage > Destinations.
  2. Select the local destination.
  3. Click the action menu, and choose Remove.
    The warning message appears: Removing this destination will no longer allow users to back up to this destination.
  4. Click OK.
    This message appears: Successfully removed destination.

Troubleshooting: Unable to remove destination

Failed to remove destination

If you are unable to remove a destination, you may receive the following warning message in the lower-left corner of the administration console: Failed to remove destination

This warning is usually caused by trying to remove the destination while organizations are still offering it. Deactivated organizations that still offer the destination can prevent destination removal. Confirm that none of your deactivated organizations are offering the destination.

  1. Go to Organizations.
  2. Click the action menu, and choose Show Deactivated.
  3. Follow Step 4 above for each deactivated organization that is visible on the Organization Overview page.

If the steps above are unable to solve the issue, or you have a prohibitively large number of organizations, you may want to search the logs for organizations that are still offering the destination.

Search the main application log (com_backup42_app.log.0) for the associated organizations using the following steps:

  1. Go to Settings > Logs.
  2. From the Logs dropdown menu, choose "com_backup42_app.log.0"
  3. Search for the expression "CommandException: Unable to delete destination"
    unable to remove destination
  4. You should find a text similar to this entry in the log search results:
[12.06.13 23:06:31.794 INFO   jetty-web-5834    com.code42.core.ws.lib.RESTResource  ] Unexpected exception: DELETE /console/api/Destination/4, SYSTEM com.code42.core.CommandException: Unable to delete destination; orgs still assigned: , [OrgDestination [orgDestinationId=7, orgId=3, destinationId=4, autoStart=false, name=null, creationDate=Fri Dec 06 15:12:51 CST 2013, modificationDate=Fri Dec 06 15:12:51 CST 2013]]
  1. You may need to scroll to the right to record all of the organization IDs (orgId) that are identified. These organization IDs identify the organizations that are still offering the destination, and therefore preventing you from removing the destination.
  2. In the Logs dropdown menu, select "history.log.0"
  3. Search for the following expression for each organization ID you identified: "modified org: <orgId>", where <orgId> is replaced with the actual organization ID you recorded:
    administration console cli
    In the screenshot above, a deactivated organization named "Deactivated Org" was still offering the destination. Once you have identified the organizations that are still offering the destination, stop offering the destination as described in Step 4.

Client configuration

Occasionally, a client configuration prevents the removal of a destination. To fix this problem:

  1. Sign into the administration console.
  2. Open the CLI by double-clicking the Code42 for Enterprise icon in the upper left.
  3. Execute the following command in the CLI: config.fix fix all
    The CLI responds with "SUBMITTED"
  4. Wait a few minutes for the command to execute.
  5. Attempt to remove the destination again.