Who is this article for?
CrashPlan for Small Business, yes.
Code42 for Enterprise, yes.
Link: Product plans and features.
List of administrator-related terms and definitions.
Password you supplied when you registered your user account.
The web-based application that manages the Code42 environment. The administration console is part of every Code42 installation.
See replace device.
An archive contains backed-up data for a single device. Each archive is securely encrypted using an archive encryption key.
Archive key password
The password supplied when you enable the archive key password option for your archive’s encryption. If you enable this option, you must supply the archive key password to restore your files. See also account password and secured key.
A task that checks the health of each active archive on a regular schedule. Archive maintenance removes excess file versions, deleted files, and files no longer selected for backup. It also identifies and corrects corrupted data.
Administrators can start the archive maintenance manually from the administration console. Users can start the archive maintenance in the Code42 app with the Run Maintenance button.
The process of identifying and verifying users in a system. Methods for authentication include:
- Local Code42 directory
- Single sign-on (SSO)
- Multi-factor authentication (MFA)
Allows access to Code42. When enabled, users sign in using the authentication provider instead of Code42. Examples of authentication providers include Okta, Google SSO, Ping, Azure AD, OneLogin, and Microsoft AD FS.
- The files that you saved to another location, so you can restore them in case of loss. Also known as “backup archive.”
- The operation in which files are sent and stored in the Code42 cloud or a local destination, as in, “Your backup is in progress.”
The setting for how often the Code42 app backs up files or file revisions.
A group of files backed up to a specific location or with specific settings.
Devices, users, and organizations can be blocked. This is non-destructive, and no data is lost. Blocked devices continue to back up, but blocked users cannot sign in or restore files on any of their devices. Blocked organizations prevent all of that organization’s users from signing in or restoring files. A blocked user continues to use a subscription.
Links that appear at the top of a web page to show you where you are in the website and help with website navigation.
Code42 app for Splunk
Code42 uses Splunk (software for searching, analyzing, and visualizing large amounts of machine-generated data) to provide visual reports about Code42 data and usage. The Code42 app for Splunk is an add-on to Splunk that connects a customer's Code42 data to their Splunk environment.
- A Code42 environment with no on-premises authority server or storage server. This is Code42’s SaaS solution; all administrative functions and storage are managed by the Code42 cloud.
- An optional storage destination for Code42 environments that have an on-premises authority server.
A broad term for all parts of a Code42 for Enterprise installation, which might include the administration console, organizations, users, and devices.
The services that power the Code42 environment including storage, transport, directory, identity, policy, and search.
The engine that runs backup operations in the background on a device running the Code42 app.
Temporary holding state for archives after they are deactivated but before they expire and are permanently deleted. This is similar to a file in your computer’s Recycle Bin or Trash. A user who has an archive in cold storage still consumes a user subscription. Administrators can retrieve archives from cold storage throughout the cold storage retention period.
The final step of archive maintenance. Compaction reclaims disk space by removing the following from the backup archive: old file versions and old deleted files (according to user or administrator settings), and files no longer selected for backup.
Reduces the size of files so they take less space and less time to send. The Code42 app compresses files before sending them for backup, which increases the overall backup speed. This compression is lossless. The Code42 app does not compress certain types of files, such as files ending in .zip.
See Code42 service.
An encryption key that is user-created (using the Passphrase or Generate options) and is used instead of the encryption key generated by the Code42 app. The custom key option greatly increases user responsibility because there is no way to recover a backup if the custom key is lost or forgotten, and our Customer Champions have no way to help recover a custom key.
Main page of the administration console with stats and graphs across all organizations.
Process in which duplicate files (and parts of files) are identified and backed up only once. Data de-duplication runs on each source device.
Stop a backup and move the archive into cold storage (for eventual deletion). Subscriptions are not immediately freed by deactivation. Devices, users, and organizations can be deactivated. Deactivated users cannot sign in and cannot be added to a legal hold.
Cause the Code42 app on a device to sign out. This is non-destructive and no files are deleted. The user of the device will be able to sign in again. A deauthorized device continues to use a subscription. Only devices can be deauthorized; users and organizations cannot.
Location where your files are backed up. For example: an external drive or Code42 cloud storage.
The process of getting files from a backup destination. Downloading allows you to get backed-up files from any device, any time.
New features and functionality are considered early access (EA) when they are released to all Code42 cloud environments, but still may undergo minor refinements and improvements before general availability.
Some features and functionality apply only to specific product plans, so you may not see an EA feature if it is not included in your product plan.
Encode files so no unauthorized persons can read them.
A string that a cryptographic algorithm uses to encrypt files.
A Code42 security feature that uses the Code42 app to capture file activity on user devices in real time, helping administrators identify the following types of potential data leaks or security problems:
- Removable media
- File sharing on cloud services
- File uploads and downloads in web browsers and other applications
An encryption level upgraded from the standard security option. Code42 has two enhanced security options: archive key password and custom key. Also called upgraded security.
A device's public IP address.
A service outside of Code42 that stores encryption keys for customers. By default, the Code42 cloud uses a Vault server owned and managed by Code42. Code42 cloud customers can also use their own Vault server.
Data about a file. For example, file size, file type, date created, date last modified, etc.
New features and functionality are considered generally available (GA) when they are released to all Code42 cloud environments and there are no known refinements or improvements immediately necessary. However, even after GA, Code42 may continue to evolve and improve functionality in future releases.
Some features and functionality apply only to specific product plans, so you may not see a GA feature if it is not included in your product plan.
- Globally Unique IDentifier. A number generated and assigned to each device, plan, and server in the Code42 environment. Used by Code42 for Enterprise to associate each device with its backup archive.
- A Code42 app command-line interface command to view and manipulate the GUID value for the current device.
An IT administrative area or market that deals with users in a IT system and gives them access to the right resources within the system.
Identity provider (IdP)
A general term to refer to a system that contains user identities. Identity provider can refer to a system performing authentication, provisioning, or both. Examples of identity providers include Okta, Google SSO, Ping, Azure AD, and OneLogin.
The process of saving only the parts of files that changed since the last backup.
The very first backup performed on a specific source device. The initial backup of files takes significantly longer than later, incremental backups.
The process when selected files on a user’s device are preserved, for example if a lawsuit is anticipated. Code42 provides a central, well-organized archive for the discovery of electronically stored information (ESI) on laptops and desktops in the event of litigation. The Code42 Legal Hold application enables legal teams to create and manage their organizations’ legal holds.
Limited early access
New features and functionality are considered limited early access (LEA) when they are released only to specific Code42 customer environments, typically as a result of direct communication with your Customer Success Manager (CSM) or other Code42 personnel. Limited early access features and functionality may still require refinements and improvements before early access or general availability.
A type of backup destination that is attached directly to the same device. For example, a folder in the file system or an external drive.
A user that is managed within Code42. This means the user's credentials are stored in the Code42 database, rather than using a third-party authentication method like single sign-on. Additionally, the local user's authorization is managed within the administration console, not through a third-party authorization method like LDAP.
A type of backup in which files are transmitted over the Internet or WAN. In the Code42 app, all Code42 cloud destinations are considered online destinations.
The hierarchical level in the Code42 environment for users and their devices. Each user can belong to only one organization. You can define many settings at the organization level; different organizations can have different settings. An organization can contain child organizations, and an organization can exist without containing any users.
See Code42 cloud.
Automates user management. Applications like Code42 sync with a provisioning provider and then create, update, or remove users based on the provisioning provider's user profile. Examples of provisioning providers include Okta, Ping, and Azure AD.
See Code42 cloud.
The process of backing up files immediately after the files were created or changed. This protects you from loss that might occur if backups are scheduled only at specific times.
A 16-character string that activates your subscription. The registration key is required to purchase user subscriptions or support plans.
The process of a new device taking the place of a device that has been lost, stolen, sold, reformatted, etc. The replace device process is optional when Code42 for Enterprise detects a new device on an existing account. The replace device process transfers the backup archive, backup file selection, and backup settings to the new device. It also deactivates the other device so it can longer back up.
Reporting web app
The online tool that administrators can use to search, filter, and export usage statistics about their Code42 environment.
An open standard protocol for automating user management.
An archive encryption key that is protected with an account password (default security) or an archive key password (enhanced security).
Single sign-on (SSO)
SSO is one type of authentication method. It allows a user to use the same credentials to sign in to multiple applications.
See Code42 cloud.
A process where the source device and the storage destination compare what files the source has sent vs. what files are actually stored on the destination.
An attribute that defines functions and features of the Code42 environment. System properties are usually enabled, disabled, or configured from the administration console command-line interface.
A single account in your Code42 environment. A user account has a single set of sign-in credentials (username and password) and a single encryption key for all backups. A user always belongs to one (and only one) organization.
Setting to specify how many versions of a file to keep over time. Removing older and less relevant versions can reduce the size of your backup archive. The default setting keeps more of your recent versions and fewer of your older ones.
The ability to restore files from the administration console and download files from a web browser. Web restore is a secondary method of restoring files.
Windows user profile backup
This feature uses Microsoft's User State Migration Tool (USMT) to create a backup of user profile settings. Administrators can download the user profile to a new device as part of the replace device process.