Skip to main content
Question

Troubleshooting Data verification errors

  • February 27, 2025
  • 3 replies
  • 22 views

Forum|alt.badge.img+1

We have over 100 systems in our CommCell computer group and most of the systems are backing up just fine. We have two schedules, a monthly full on the first Friday of each month and weekly incremental jobs. However, on one large file server, the incremental backups are routinely being converted to fulls. I see these messages in the job history: Backup job has been converted to a full backup because Data
   Verification detected errors

The full backups are causing quite a load on the file server. Looking at the job history, about ½ of the jobs are being converted from INCR to FULLs. How do I track down what is causing the verification errors so that it doesn’t have to convert incremental to fulls?

 

Thanks,

Q

3 replies

dude
Byte
Forum|alt.badge.img+15
  • Byte
  • 330 replies
  • February 27, 2025

Do you see any errors while the INC job is running? Are all these systems running on the same media agents? Did you narrow down the jobs converting to full to a specific media agent or storage pool?

There is a lot of information missing here, but I would start by looking at the event logs on the job that converts to full.


Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Vaulter
  • 1301 replies
  • February 28, 2025

This is not good. Its an automatic protection when data verification fails - either at the job level or the incremental DDB verification. DDB verification can mark blocks on disk as bad, a full backup ensures that a new baseline set of data is created, otherwise all your backups might be unrecoverable forever if the synthetic full is referencing missing or damaged blocks.

Check out the admin job history and look for any verification jobs. There should be events on the job with more details. There is also job based verification - add or look for the verification status column in the backup history

If you can’t find the source of the issue, please open a support case - as dude said, there are many variables and likely will require some analysis in the logs.


Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • April 14, 2025

Thanks both for replying. The system that was having issues was having some drive issues on the OS drive which we just replaced last week. The first FULL after the drive replacement and OS upgrade completed w/o errors. However, we’re still having the INCR to FULL conversions due to data verification errors. I’m a sys admin for this system and we use CV for the backups but I didn’t set up the back up policies/schedules. I’m a bit of a newbie with Commvault.  I don’t have full admin access to CommCell, for example, for this client, I see no “admin job history”.

Where do I find the media agents for my backup policy?

Do I need to add a data verification job to the schedule? I don’t currently see one.

Would adding a synthetic full to the schedule help with this issue?

Looking through the /var/log/commvault/Log_Files on the client, I do see some messages about the job failing, but no details of why the job failed. How do I find more details of the job?

 

Thanks in advance!

Q


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings