Commvault Error Code 82:156: How to Fix Pending Backup Jobs

Last updated: November 9, 2026. Error meanings checked against Commvault’s own knowledge base and documentation.

Commvault error code 82:156 stops a backup job and leaves it in the Pending state. In most cases the MediaAgent cannot reach its Index Directory (also called the index cache). This guide explains what Commvault error code 82:156 means, how to fix it step by step, and how to deal with the other pending job codes you often see next to it, such as 32:406, 82:158, 19:1131, 19:1132 and 40:110.

How to read a Commvault error code

Commvault writes every error as two numbers split by a colon, like 82:156. The first number is the category (the part of the product that raised the error) and the second number is the exact error inside that category. The same code can have more than one root cause, so always open the job in the Job Controller, read the full Reason for job delay text, and check the logs on the client and the MediaAgent before you change anything.

What Commvault error code 82:156 means

Commvault knowledge base article 54206 describes it as a backup job that goes Pending because the destination hit an error while processing data from the source. The usual reason is that the Index Directory is not accessible. The MediaAgent needs to read and write its index cache for every backup, so if that folder is missing, full, blocked or has the wrong permissions, the job cannot move on.

How to fix Commvault error code 82:156

Find the Index Directory path. In the CommCell Console, open the MediaAgent properties and go to the Catalog tab. Note the Index Directory path.
Check the path exists. Log in to the MediaAgent and open that folder. If the drive letter, mount point or network share is gone, bring it back or move the Index Directory to a working path (Commvault’s “Moving the Index Directory” procedure).
Check free space. A full disk is one of the most common causes. Free up space or move the index cache to a larger volume.
Check permissions. The account that runs the Commvault services needs read and write access to the Index Directory. Fix the folder permissions if they were changed.
Check the path is enabled. If someone disabled the Index Directory path in the Catalog properties, enable it again.
Check security software. Antivirus or ransomware protection can block the index cache. Add the Commvault folders to the exclusion list. Commvault community reports show its own ransomware protection blocked the index cache on some older builds, so keep the MediaAgent on a current maintenance release.
Resume the job. Right-click the job in the Job Controller and choose Resume. Watch the first few minutes to make sure it moves to Running.

Common causes at a glance

Cause	What to check
Index Directory path missing	Drive, mount point or share on the MediaAgent
Disk full	Free space on the index cache volume
Wrong permissions	Read and write access for the Commvault service account
Path disabled	MediaAgent properties, Catalog tab
Blocked by security tools	Antivirus and ransomware protection exclusions
Network problems	Firewall and name resolution between client, MediaAgent and CommServe

Other Commvault pending job error codes

These codes often show up in the same Job Controller view. Each one points to a different fix, so match the exact code first.

Error code 32:406

Another index problem. Commvault lists three causes: the disk that holds the Index Directory is full, the Index Directory path is disabled, or no MediaAgent can access the Index Directory. Use the same checks as 82:156: free space, the Catalog tab, and access from the MediaAgent.

Error code 82:158

The job is pending because of a network connection problem between the client and the MediaAgent. Test the connection both ways, check firewall rules and ports, and make sure both machines can resolve each other’s host names.

Error code 19:1131

The CommServe is waiting for the services on the client to come online. It usually means the CommServe lost network contact with the client services. Check that the Commvault services are running on the client, check the network, and if the link is unstable, Commvault suggests a one-way firewall setup.

Error code 19:1132

Another backup is already running for the same client, agent, instance or subclient. This is usually informational. Let the first job finish, or turn on Queue conflicting jobs so the second job waits instead of failing.

Error code 40:110

Client-side deduplication is on and the client Cache-Database and the Deduplication-Database are out of sync. The job tries again on its own every 20 minutes, or you can resume it by hand.

Error code 19:1308

Register job failure. The job could not be registered with the CommServe. Read the reason text that follows the code, because it names the actual cause.

What about error code 13:85?

Commvault has no public knowledge base article for 13:85, and admins describe it in different ways, usually next to other 13-series data transfer errors such as 13:138. Treat it as a data transfer problem between the client and the MediaAgent: read the full error text, check the network between the two machines, restart the Commvault services if a job is stuck, and open a Commvault support case with the job logs if it keeps coming back.

Where to find the logs

In the Job Controller, right-click the job and choose View Logs to see the entries for that job only.
On Windows, Commvault logs are in the Log Files folder inside the Commvault install directory on each machine.
On the MediaAgent, the index logs show index cache errors. On the client, the backup logs show what the agent saw.
Match the time stamps from the Job Controller to the logs so you read the right lines.

How to stop pending jobs from coming back

Keep the index cache on its own volume with plenty of free space, and set an alert for low disk space.
Do not change permissions on the Commvault folders without testing a backup after.
Keep antivirus and ransomware exclusions for the Commvault install, log and index folders.
Keep the CommServe, MediaAgents and clients on the same supported maintenance release.
Check the Job Controller daily so pending jobs are fixed before the backup window ends.

FAQ

Is Commvault error code 82:156 a data loss problem?

No. The job is paused, not broken. Your earlier backups are safe. Once the Index Directory is reachable again you can resume the job.

Can I move the Index Directory to fix it?

Yes. If the old drive is full or gone, follow Commvault’s “Moving the Index Directory” steps to point the MediaAgent at a new path, then resume the job.

Why does the job stay Pending after I fixed the path?

Pending jobs wait for their next retry. Resume the job by hand, and if it goes back to Pending, read the new reason text. It may now show a different code, such as a network code like 82:158.

For anything not covered here, use the official Commvault documentation or open a case with Commvault support.

Axee Davies

Axee Davies is the founder of AxeeTech, publishing gaming guides, codes, and Windows how-tos since March 2013. A tech enthusiast for 13+ years — starting with smartphones and Android rooting — he now runs a site that puts out a new guide every day for Roblox players, traders, and Windows users. More about AxeeTech

axeetech.com