Skip to main content

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, no.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

HOME
GETTING STARTED
RELEASE NOTES
FAQS
SYSTEM STATUS
Code42 Support

Upgrade to the Code42 Cloud

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, no.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

Overview

Upgrading from an on-premises authority server to the Code42 cloud requires moving your database. This article describes how the Code42 Professional Services team migrates your database from your authority server to the Code42 cloud.

Upgrading to the Code42 cloud allows you to take advantage of our latest features to protect data from insider threat.

For more information about upgrading to the Code42 cloud, see our Authority Upgrade Toolkit.

Considerations

  • A Professional Services team member guides you through the upgrade process. Contact your Customer Success Manager (CSM) to learn more.
  • Your Professional Services contact runs the Migration Assistant tool on the server where your Code42 authority server is installed.
  • This process does not migrate on-premises backup data. It only migrates archives stored in the cloud.

Functionality not available during migration

  • You cannot add new users via Code42 console or Code42 app.
  • New SSO users cannot log in for the first time.
  • Web and push restores cannot happen via the Code42 console.
  • Users currently on archive key password security cannot change their passwords.
  • You cannot change the security level of users.

Note: Backup and restore using the Code42 app is still functional during the migration.

Before you upgrade

A Code42 Professional Services team member works with you to get a migration code and help validate your database. This validation step ensures the database is ready to be moved to the Code42 cloud.

Before upgrading to the cloud, you must do the following: 

  • Upgrade to the latest version
    The authority server is upgraded to 8.2.5 with the latest Code42 app version.
  • Open network ports
    • Open ports 443 and 4287 for access to the Code42 cloud.
    • Port 443 is used for the migration. Code42 can turn off access to this port when the migration is complete.
  • Change usernames to emails
  • Change custom roles to standard
    The Code42 cloud does not support custom roles. Re-assign standard roles to users.
  • Assign Customer Cloud Admin role
    Assign the the Customer Cloud Admin role to the individual administering the cloud deployment.
  • Discontinue on-premises backup
    On-premises destinations are not supported. On-premises backups stop after the authority migration. Web restores via zip file are still available. 
  • Select identity management methodology
    Your identity management methods may need to change in a cloud deployment model. 
  • Assess API usage
    API scripts or integration (outside of Splunk) will break during the migration. 

Run the Migration Assistant

Your Professional Services contact does the following after validating that your Code42 environment meets the requirements for starting the upgrade process.

  1. Logs in to the host server where your authority server is installed. 
  2. Stops your authority server
  3. Downloads the Migration Assistant to the server: 
    1. Linux: Unpacks the TGZ file. 
    2. Windows: Double-clicks the ZIP file.
  4. Opens Terminal (Linux) or Command Prompt (Windows).
  5. Navigates to the MigrationAssistant-x.x.x folder.
  6. Runs the Migration Assistant script as an administrator:
    1. Linux:
      sudo./bin/C42MigrationAssistant --migrate-now <migration code>
    2. Windows:
      .\bin\C42MigrationAssistant.bat --migrate-now <migration code>
  7. The migration is successful when the Professional Services contact receives the following message: 

    {
    "success" : true

      "errorDescriptions" : { },

      "errors" : { },

      "warningDescriptions" : { },

      "warnings" : { }
    }

Verify your new Code42 console

When the migration is finished, sign in to the Code42 console to verify that everything is working as expected. 

  1. Sign in to the Code42 console in the Code42 cloud as a user with the Customer Cloud Admin role.
  2. Verify your Code42 environment is configured correctly:
  3. Start your old on-premises authority server using the CLI command. Your Code42 Professional Services contact helps you update this old Code42 console to redirect Code42 apps to your new cloud Code42 console.

Next steps

Troubleshoot migration errors

Below are tips that the Professional Services team uses to troubleshoot common errors when migrating authority servers to the Code42 cloud.

Illegal value

"ILLEGAL_VALUE": 
    ["t_user[119]: Field username value user.lastname@example.com: Value already exists in another tenant", 

This means that the identified user already exists in the Code42 cloud. The Professional Services team updates the user's email or deactivates the old user account to complete migration. 

Tenant not found

"TENANT_NOT_FOUND" : "The tenant could not be identified in the target cloud."

This means that the migration code is incorrect. The Professional Services team verifies and enters the correct migration code. 

  • Was this article helpful?