Skip to main content
Code42 Support

Converting Your Code42 Environment From Local to Exclusively Cloud Destination

Applies to:
  • CrashPlan PROe
This tutorial explains how to convert your Code42 environment from using exclusively local destinations (i.e., destinations using enterprise servers and store points in your own datacenter) to exclusively using cloud destinations provided by Code42 or a third party.

Before You Begin

You should be familiar with the following terms:

  1. 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 enterprise servers and store points on a single LAN or at a single data center.

  2. Storage server:

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

  3. Store point:

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

Considerations

There are many reasons you may want to remove store points and destinations from an enterprise server. This tutorial shows you how to replace your Code42 environment's onsite storage with cloud storage, while continuing to use your onsite master server for authentication.

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

  • Data loss will occur when store points and destinations are removed. You should ensure that source devices have fully backed up to the new cloud destination before removing the 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
  • 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
  • Archives in cold storage must be purged manually or you must wait until the cold storage retention period has expired.
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, please contact our Customer Champion team.

Step 1: Adding The Cloud Destination

Add a cloud provider destination to your Code42 environment. You will need the "provider key" supplied by your cloud storage provider for this step. Contact the provider to get the provider key.

Step 2: Confirming Devices Are Using The Cloud Destination

Confirm that your organizations and users are using the new cloud destination:

  1. Sign in to your administration console.
  2. In Settings > Organization > Destinations, verify that the checkbox next to the cloud destination is selected.Confirm cloud destination being offered by default org
  3. In Settings > Device > Backup, verify that the new cloud destination is in use. If not, click the Use checkbox, then push the change to your devices. You may also lock the setting on this screen.Confirm device default settings offer cloud destination
  4. Since not all of your organizations may be configured to inherit the default organization and device settings, go to each individual organization's details screen, then choose action menu > Edit > Destinations. If the child organization does not inherit the settings from its parent organization, click the checkbox for the cloud destination in order to offer it to to the devices within the child organization.

    Disabling Inheritance
    If inheritance is disabled for an organization, that organization is not affected by changes to its parent organization.
    Verify that orgs offer the cloud destination

  5. Open the CrashPlan app for a test user or real user
  6. Go to Backup and confirm that the cloud destination is available and is being utilized.
    Verify that CrashPlan app is using the cloud

Step 3: Stop Using Local Store Points (Optional)

This step is only necessary if you want to stop using any "non-cloud" storage attached to the master server in preparation for permanently removing the local store points (the store points not offered by the cloud storage provider).

  1. Reject new devices on the local store point:
    • From Destinations > Store Points > Store Point Details > action menu, choose Reject New Devices.
  2. Disable inbound backup on the local store point:
    • From Destinations > Store Points > Store Point Details > action menu, choose Disable Inbound Backup.
  3. If you have another store point in the local destination to which you would like to migrate the archives, you can easily migrate the archives off the store point to be removed.

Step 4: Stop Offering The Local Destination

Stop offering the local destination to ensure that all backups are stored on your cloud storage.

Cold Storage
If you plan to keep archives in cold storage on a local destination until backups to the new cloud storage have completed, this step should be delayed until the backups to the cloud destination have completed.
  1. From Settings > Organization > Destinations, deselect the local destination. A dialog box will warn you of the data loss associated with deselecting a destination. Type "I AGREE" in the text box, and click OK.Unoffer a destination dialog box warning
  2. For each organization that does not inherit settings from the parent organization, do the following:
    • From Organizations > Organization Details > action menu > Edit > Destinations, deselect the local destination. A dialog box will warn you of the data loss associated with deselecting a destination. Type "I AGREE" in the text box, and click OK.Stop offering destination to orgs

The archives that were stored in the selected destination will be 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 destination permanently. However:

  • You may wish to keep the local store points until you have confirmed that your users and their devices have completely backed up to the new cloud destination
  • You may need to keep the local store points and destination online until your organization's data retention policy allows you to permanently delete the original local archives. The original, local archives contain file versions and deleted files that new archives in cloud storage will not be able to restore

If you are sure that you want to delete the local store points and/or destination, follow these steps:

  1. From Destinations > Store Points (the Store Points Overview screen) , click on the value in the Cold Storage column (labeled "Cold"), in the row representing the store point you wish to empty.Finding archives in cold storage to purge
  2. Click the top left checkbox to select all archives in cold storage on this store point:
    Select Cold Storage
  3. From the action menu, select Purge Archive.Purge cold storage
  4. Click OK in the dialog box that warns you about data loss:Archive purge warning
  5. The archives will be immediately purged:Successful purge of archives

Step 6: Remove The Store Point

  1. From Destinations > Store Points > Store Point Details > action menu, choose "Remove"Remove storepoint
  2. In the Remove Storepoint dialog box, click the checkbox labeled "Remove, even if files are still present," then click Remove.Remove storepoint warning dialog

At this point, you have removed the local store point and all associated archives, users, and devices. You are not able to remove or delete the default local destination on a master server. However, you have already stopped offering the local destination to all of your organizations, so it will not be visible to any users or devices.

 

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 wish to cease using that storage server after the move to cloud-based storage.

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

To permanently remove the storage server (after applying steps 3-6 above to the storage server):

  1. Go to Destinations > Servers > Server Details > action menu, and choose Remove:Remove storage node
    • You will see a message in the lower left of the administration console verifying that the server was removed:Successful removal of storage node

Step 8: Remove The Destination

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

Storage Servers
Remember that you administer storage servers from 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 will no longer be needed after the move to cloud-based storage. Then, on the master server, to remove the newly redundant destination:

  1. From Destinations > Destination Details > action menu, choose Remove:Removing a destination
  2. You will receive the warning message, "Removing this destination will no longer allow users to backup to this destination." Click OK.
  3. If the removal of the destination succeeds, you will see a message in the lower left of the administration console verifying that the destination was removed:Successful removal of destination

Advanced Topics

Unable To Remove A Destination, Possible Cause 1

If you are unable to remove a destination, you may receive the following warning message in the lower-left of the administration console: "Failed to remove destination"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. From Organizations > action menu, choose Show Deactivated, then 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 > Server > System Logs > View
  2. From the Logs dropdown menu, choose "com_backup42_app.log.0"
  3. Search for the expression "CommandException: Unable to delete destination"Search logs for CommandException
  4. You should find a text similar to this entry in the log search results:
    1. [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]]
  5. Scroll to the right if necessary, in order 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.
  6. In the Logs dropdown menu, select "history.log.0"
  7. 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:Search logs for Org ID
  8. In the example from 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, you can then stop offering the destination as described in Step 4, substep 2.

Unable To Remove A Destination, Possible Cause 2

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

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