Skip to main content

This article applies to Code42 CrashPlan version 5.

Other available versions:

Version 6 | Version 4icon.qnmark.png

Code42 Support

Hybrid cloud setup: add public cloud storage

This article applies to Code42 CrashPlan version 5.

Other available versions:

Version 6 | Version 4icon.qnmark.png

Overview

This tutorial explains how to configure the Code42 public cloud destination in a hybrid deployment and make it an available backup destination for users.

Follow these instructions using the network and provider key information you received from your Professional Services engineer.

Before you begin

  • Your master server must run the current version. Upgrades are available from the upgrades guide.
  • The recommended option is to make your on-premises master server publicly accessible at its primary network address and port. Configure the following network rules:
  • (Optional) You can shield your master server behind a firewall, with inbound access only within the wall, and outbound access only to the Code42 cloud via port 443. (This can delay updates of statistics in the Dashboard and the Reporting web app for up to 24 hours.) 

For a full list of network traffic requirements and recommendations, refer to TCP and UDP ports used by the Code42 platform.

Code42 environment version support
If you are using Code42 cloud's storage, you must continually update your master server's version to match the Code42 cloud. See our Product Lifecycle Policy for details.

Steps

Configure the Code42 public cloud destination

Before your users can back up to the Code42 public cloud, you must first configure the destination on your master server.

  1. Sign in to the administration console on your master server.
  2. Go to Destinations > Add to create a new destination for the Code42 public cloud.
  3. Enter a name for the new destination (e.g., Code42 public cloud).
  4. Check the box next to Provider.
  5. Paste the Provider Key you received from your Professional Services engineer into the Provider Key field.
  6. Click Create to create the destination.

Offer the Code42 public cloud destination

Once the Code42 public cloud destination is configured, you must then make that destination available for backup to your users.

You can choose to offer the Code42 public cloud destination as a system-wide default or only to users within the organizations you choose.

Offer destination as system-wide default:

  1. Sign in to the administration console on your master server.
  2. Go to Settings > Organization.
  3. Click the Destinations tab.
  4. Check the box next to the new Code42 public cloud destination that you configured.

Backup is now available to the new Code42 public cloud destination. All organizations that inherit settings from the system-wide default level are able to back up to the new destination.

Offer destination to specific organizations:

  1. Sign in to the administration console on your master server.
  2. Go to Organizations.
  3. Choose an organization from the Organization List.
  4. From the Action Menu, click Edit.
  5. Click the Destinations tab.
  6. If Inherit destination settings from parent is checked, uncheck the box to view available destinations.
  7. Check the box next to the new Code42 public cloud destination.
  8. Click Save.

The destination you offered is now available for backup from the selected organization's users.

Disabling inheritance
If inheritance is disabled for an organization, that organization is not affected by changes to its parent organization.

Restore from the Code42 public cloud destination

There are several ways to restore files from the Code42 public cloud destination using the administration console, including zip file restores, server file system restores, and device restores. Using a Code42 public cloud to restore files from the administration console follows the same process as a standard Code42 CrashPlan configuration.

Restrictions

  • You must connect to the administration console using HTTPS over TCP port 4285 to restore files from the administration console. If you do not, your web restore may fail. Other methods of restoring, such as restoring files from the CrashPlan app, communicate on a different port. They are not affected by restrictions on port 4285.
  • You cannot use the primary administrator account (the first account created on your master server) to restore from a provider destination. To restore from a provider destination, simply create a new user account with the necessary roles, and use that account to restore files from the administration console.
  • If your master server is not available:
    • CrashPlan app devices that have already connected to the Code42 cloud can continue to back up and restore normally.
    • New CrashPlan app devices cannot connect to the Code42 cloud until the master server is available.