Skip to main content

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Cloud.

Code42 Support

Archive keystore reference

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Cloud.

Overview

External keystores mean that in the Code42 cloud you can store copies of users' encryption keys separately from the backup data and from other customers. In the administration console, the Archive Keystore view allows you to identify, monitor, configure, and move your keystore.

For details about managing archive keystores, see Manage your archive keystore.

Archive keystore

To access the Archive Keystore view, you need the Customer Cloud Admin role.

  1. Sign in to the administration console.
  2. Select Administration > Settings > Keystore.

Archive keystore

Item   Description
a Action menu

Commands available in the Archive Keystore view:

  • Edit Keystore: Provide a new URL and certificate file for a private keystore. (Self-administered only.)
  • Migrate Keystore: Move keys from one storage location to another.
  • View Keystore History: See a log of all keystore configuration and migration activity. (Disabled until the first history record exists.)
b Administrator
  • Code42: The keystore is owned and operated by Code42.
  • Self-Administered: A private keystore owned and operated by the customer.
c Type
  • Vault: A server and storage service separate from the Code42 cloud.
    For details, see Configure a Vault server to hold your Code42 archive keystore.
  • Legacy: For existing customers before version 6.0, copies of keys reside in the server database (at least until the customer moves them to a Vault keystore).
d URL
(Self-administered only.)
The address, including port number, of a self-administered keystore.
e Connection Status

The state of Code42-keystore communications at the time this view opened.

 

Online: The Code42 cloud and keystore are communicating.

 

Offline since date, time (cause):

  • Host unavailable: The keystore does not respond to Code42 cloud requests.
    Possible error messages:
    • Bad HTTP response failure
    • Certificate verification error while connecting to your Vault URL
    • DNS resolution failure
    • Request failure
    • Unknown failure
    • Unsupported or unrecognized SSL message
    • Web certificate expired
    • Web certificate not yet valid
  • Unable to authenticate: The Vault is not allowing the administrator to access the data.

    Possible error messages: 

    • Authentication certificate expired
    • Authentication certificate not yet valid
  • No request: The server failed to test the connection.
  • Unknown: A migration has just completed. There is no data to inform a status report.

The timestamps present your local time in a 12-hour clock.

f Connection Reliability A summary of the data reported in the time line below.
g Time line Keystore online Keystore offline Keystore failed

The Code42 cloud tests its connection to your keystore every minute.

The time line reports the result of the last hour's tests:

Keystore online Keystore is online
Keystore offline Keystore is offline
Keystore failed Unknown (the Code42 cloud has no data to report)

The timestamps report your local time in a 24-hour clock.

Edit keystore

Edit the configuration of a private keystore by selecting the action menu > Edit Keystore. (Self-administered keystores only.)

keystore edit view

Item   Description
a URL The address of a private Vault keystore.
b Upload PFX or P12 file

Click to provide the security certificate for the Vault.

The file must be a PFX or PKCS12 certificate. The file name extension need not be .pfx or .p12.

c PFX or P12 file password The password for the certificate, if it is configured to use one.

Migrate keystore

Move a keystore from one location to another by selecting the action menu > Migrate keystore.

keystore migrate view

Item   Description
a Type
  • Code42 Vault: Move copies of keys to the keystore service owned and managed by Code42.
  • Self-Administered Vault: Move copies of keys to a keystore service owned and managed by the customer.
b URL The address of a self-administered keystore.
c Upload PFX or P12 file

Click to provide the security certificate for the Vault.

The file must be a PFX or PKCS12 certificate. The file name extension need not be .pfx or .p12.

d PFX or P12 file password The password for the certificate, if it is configured to use one.
e Who should be notified when this migration is complete? The email address to receive notice from the Code42 cloud when migration starts, and when it either fails or succeeds.

Keystore history

View the record of all your keystore configuration and migration activity by selecting the action menu > View keystore history. (Self-administered keystores only.)

keystore history view

Item   Description
a

Date & Time

When an event took place, in your local time.
b User

The administrator who initiated the event.

  • system: the Code42 cloud.
c Action Type
  • Migration: A process of moving copies of keys from one location to another.
  • Configuration: A process of changing a keystore's URL and security certificate.
d Action Details Detailed description of the event.

External resources

  • Was this article helpful?