Commvault Certified Professional key terms

The central management server of a CommCell. It stores the configuration database, schedules jobs, coordinates clients and MediaAgents, and provides the console and API endpoints administrators use to control data protection operations.

The complete logical deployment consisting of one CommServe, its clients, MediaAgents, and storage. It is the top-level administrative and security boundary within which policies and permissions are applied.

The CommServe database holding all CommCell configuration and job metadata, such as clients, subclients, policies, schedules, and job history. Backing it up regularly is essential for disaster recovery.

A software component that moves data between clients and storage media. It writes to and reads from disk libraries, tape libraries, and cloud storage, and performs deduplication and encryption work during data movement.

A computer or application instance protected by the CommCell, running Commvault software agents or accessed through an agentless method. Clients are grouped into subclients that define what data is protected.

The intelligent data agent installed on a client that reads and prepares data for backup and restores it on request. Different iDAs exist for file systems, databases, applications, and virtual platforms.

A logical container inside a client that defines the specific content to protect, such as file paths, database instances, or volumes, along with its own schedule, retention, and storage policy associations.

A collection of clients managed together so that policies, schedules, and operations can be applied to many machines at once. Useful for consistent configuration across large environments.

A logical container that binds data to one or more storage copies and defines retention, deduplication, and data-flow rules. Subclients write to a storage policy rather than directly to a library.

A physical destination within a storage policy, pointing to a library and MediaAgent. Multiple copies provide redundancy, and one copy is designated primary for backups while others receive auxiliary copies.

A configured storage target such as a disk library, tape library, or cloud library that MediaAgents use to read and write backup data. Libraries define mount paths, credentials, and media characteristics.

A file system location on a disk or cloud library where a MediaAgent writes backup data. Multiple mount paths spread load and allow capacity to grow without reconfiguring the library.

Rules that determine how long backed-up data is kept before it becomes eligible for pruning. Retention can be set by cycles, days, or extended rules, and influences auxiliary copy and deduplication cleanup.

A job that copies backed-up data from one storage copy to another, typically from a primary copy to a secondary or offsite copy. It can run on demand or on a schedule and supports selective copy.

An auxiliary copy option that copies only specified jobs or time ranges rather than all eligible data. It is useful for moving particular backups to offsite or long-term storage without duplicating everything.

The deduplication database that stores signatures and references for blocks already written to a deduplicated storage policy. It enables MediaAgents to identify and avoid writing duplicate blocks.

A technique that stores a block of data only once and references it for subsequent backups containing identical content. It reduces storage consumption and can be done at the client or MediaAgent side.

Deduplication performed by dividing data into blocks, hashing each block, and storing only blocks whose signatures are not already present in the deduplication database. It is the common mode for disk storage policies.

A streaming or sequential deduplication database used with certain deduplication configurations, particularly for IntelliSnap or streaming workloads, to track signatures in an append-friendly structure rather than a random-access database.

Commvault's snapshot management framework that coordinates hardware or software snapshots and can create backup copies from them. It reduces backup windows and application impact by leveraging array or hypervisor snapshots.

A point-in-time image of a volume, file system, or virtual machine created by storage, hypervisor, or application mechanisms. Commvault can index snapshots and use them as sources for backups or restores.

A reusable definition of when jobs run, including frequency, time windows, and recurrence rules. It is attached to subclients or other objects so many workloads share consistent timing.

A unit of work executed by the CommCell, such as a backup, restore, auxiliary copy, or report. Jobs have phases, statuses, and logs that administrators use to track progress and diagnose failures.

The CommServe service that queues, schedules, and dispatches jobs to clients and MediaAgents, enforcing priorities and resource limits. It is the first place to look when jobs remain pending.

The route data takes from a client through one or more MediaAgents to storage. Data path configuration controls load balancing, failover, and which MediaAgents handle a subclient's backups.

The process of cataloging file or object metadata during backup so items can be searched and restored by name or path without browsing full directory trees. It supports granular search and restore operations.

The console workflow for navigating backed-up content by client, subclient, and time range, then selecting items to recover. Restores can target original locations or alternate destinations with options.

The assignment of roles and permissions to users and user groups, determining which CommCell objects they can view or modify. It is often scoped by client, client group, or storage policy.

A named set of permissions granted to users or groups, such as operator, backup administrator, or restore-only. Roles simplify administration by bundling capabilities that can be assigned consistently.

A collection of CommCell users managed together for permission assignment and notification. Grouping users reduces administrative effort and supports consistent access control across teams.

Protection of backup data and credentials using algorithms and keys configured in the CommCell. It can apply in transit, at rest, or both, and key management must be planned for recovery.

The handling of encryption keys used to protect backup data, including where keys are stored and how they are recovered. Losing keys can make backups unrecoverable, so escrow and documentation matter.

A backup of the CommServe configuration database and related components that allows rebuilding the CommCell after server loss. It should be scheduled frequently and stored off the CommServe host.

The process of removing data whose retention has expired from storage and the deduplication database, freeing capacity. Pruning jobs run in the background and depend on retention and copy rules.

An automated sequence of tasks triggered by events or schedules, used to orchestrate operations such as provisioning, validation, or notification. Workflows can call scripts and interact with external systems.

The HTTP-based interface for managing the CommCell programmatically, including authentication, job control, and reporting. It underpins custom integrations, automation scripts, and third-party tooling.

The use of schedules, workflows, scripts, and APIs to perform repetitive data protection tasks without manual intervention, improving consistency and reducing operator error across large environments.

The generation of dashboards and reports on job outcomes, storage consumption, SLA compliance, and client health. Reports support auditing and capacity planning and can be scheduled or exported.

Ongoing observation of CommCell health through alerts, job status, event logs, and dashboards. Effective monitoring catches failed jobs, capacity issues, and service problems before they affect recovery objectives.