Commvault Certified Professional study plan

Diagram the CommCell hierarchy from CommServe through MediaAgents, clients, and client groups, labeling the role of each component and the traffic each one carries.

Explain how the CommServe database, Job Manager, and Event Manager coordinate a running job, and identify which component owns each piece of job state.

List the default TCP ports used by CommServe, MediaAgent, and client communication, and state which three you would verify first when a client cannot register.

Walk through installing or reviewing a CommServe and MediaAgent pair in a lab, then record the configuration choices that affect scalability (index cache location, deduplication database placement, network topology).

Build a storage policy with a primary copy on disk and a secondary copy to a second library, then explain how the copy precedence rules decide which copy answers a restore.

Configure source-side and MediaAgent-side deduplication in the lab and compare the resulting signature and block behavior, including where the deduplication database lives and why its disk latency matters.

Trace the lifecycle of an auxiliary copy job from schedule trigger through job completion, and describe what happens to the source copy's aging rules afterward.

Tune retention and aging rules on a test policy and predict, before running, which jobs will be prunable and which will be blocked by dependent copies.

Configure a file system subclient with filters, a schedule, and a retention override, then verify the resulting job actually honored each setting in the job details.

Compare full, incremental, differential, and synthetic full backup strategies for a database agent, and state the recovery time and recovery point implications of each.

Set up an application-aware backup (SQL or Exchange style agent) including log handling and truncation, and describe what breaks if log backups stop running.

Perform a targeted restore of a single file and a single database to an alternate location, documenting the exact restore options you selected and why.

Explain how the virtualization layer discovers hypervisor hosts, what a VM group or subclient represents, and how changed block tracking drives incremental VM backups.

Configure an agentless VM backup in the lab and identify the transport modes available, plus the conditions that force a fallback to a slower mode.

Describe application-consistent VM backups versus crash-consistent ones, and state which guest quiescing mechanism you would enable for a database VM.

Outline how cloud workload protection differs from on-premises VM protection in terms of credentials, network paths, and restore targets.

Map the role-based access model from users and user groups through security associations to CommCell objects, and build a least-privilege role that can restore but not delete.

Configure multi-factor or token-based authentication for an administrative account and verify that a weaker login path is actually refused.

Enable audit trails and compliance-oriented retention (legal hold or locked retention) on a test subclient, then confirm the hold prevents deletion.

Call the REST API to list clients and trigger a backup job from a script, and explain how the authentication token is obtained and refreshed.

Read the Job Manager and job history views to classify a failed job as client-side, network-side, or media-side using only the error codes and phase timings.

Locate and interpret the logs for CommServe, MediaAgent, and client, and state which log you open first for a given symptom such as a timeout versus an authentication failure.

Build a report or dashboard from the built-in reporting tools that shows failed jobs and unprotected clients for the last seven days.

Diagnose one deliberately broken lab scenario (for example, a stopped MediaAgent service) and write the evidence chain from symptom to root cause.

Plan an upgrade sequence for CommServe, MediaAgent, and clients, stating the required order and where compatibility gaps would appear.

Describe how to export and protect the CommServe database and configuration, and explain why that backup is the true disaster recovery anchor.

Draft a disaster recovery runbook for losing the CommServe host, covering restore of the database, re-registration of MediaAgents, and validation of job resumption.

Identify the maintenance tasks that keep a CommCell healthy (database space checks, index cache cleanup, library audits) and schedule them.

Re-derive the highest-weight domain facts from memory: architecture roles, storage policy copy rules, and restore options, without opening notes.

Take a timed practice set weighted to the domain percentages and log every miss by domain so weak areas are explicit.

Re-teach your two weakest domains in writing, at the level of detail a colleague could follow without asking questions.

Review every lab deliverable from weeks one through seven and close the gaps you left marked as unfinished.