commvault.com commvault.com
Question

Error Code: [13:138]

  • 15 September 2023
  • 2 replies
  • 315 views
A
Rank
Badge

Estou tendo problema no Commvault para realizar o backup Auxiliary Copy sempre apresenta esse erro abaixo alguem ja teve esse problema e sabe como posso resover? 

I'm having problems with Commvault when performing the backup. Auxiliary Copy always shows this error below. Has anyone had this problem and knows how I can solve it?

 

Error Code: [13:138]
Description: Error occurred while processing chunk [1111336] in media [V_504103], at the time of error in library [Pool_Disk_VMs_Definitivo] and mount path [[xxx_bkp01] C:\Commvault_Pool_Disk_VMs_Definitivo], for storage policy [Policy_Pool_Disk_VMs_Definitivo] copy [Copia-Fita-Definitiva-Manual] MediaAgent [xxx_bkp01]: Backup Job [603097]. Encountered an I/O error while performing the operation.

2 replies

dude
Rank
Badge +15

Hello @Ayres 

Have you tried the KB provided by Commvault around this error code?

https://kb.commvault.com/article/54451

Symptoms

Error Code: [13:138] Description: Error occurred while processing chunk [] in media [], at the time of error in library [] and mount path [[] /], for storage policy [] copy [Primary] MediaAgent []: Backup job []. In-use chunkId requested by data verification job.

Causes

This error message may be generated if data chunks are in use when the deduplication data verification job runs. The data verification job completes with an error and the data chunks are skipped.

Resolution

The in-use data chunks that are skipped during a data verification job are automatically picked up during the consecutive data verification job.

CMR 280202 has been implemented (FR25+) to mark the jobs completed successful (instead of Completed with errors) when verification skips in-use data chunks.

N
Rank
Badge

Hello @Ayres , For the error you have shared it suggest we are getting either of the below problems:

» Chunk cannot be read ,as it can in use by other CV operations

» Storage holding the chunks\volumes are not in healthy state.

» AV or third party intruding within those storage due to CV process cannot lock to read it

» We have communication issue between source and destination MA

 

Going forward would suggest to ran full ddb verf , in-order to validate the consistency of the backed data within storage and if you see failure in that then would recommend to open a support case for team to review. 

 

Reply


Terms & ConditionsCookie settings