Is there a way to either report on or configure alerts for CBT failures? Right now, the only way we can catch them is by seeing that the job is running longer than expected. Running 11.36
Solved
Alerts for failed changed block tracking
+3Best answer by Kirk Brown
I wasn’t able to get this info easily from Commvault, but found that the error was being sent to Splunk/syslog. I was able to create a report there. This query gets me a list of VMs that generated this error over the given time period.
index=[ours] sourcetype=[ours] "{91:461}"
| eval Timestamp=strftime(_time, "%Y-%m-%d %H:%M:%S")
| eval Computer=replace(Computer,"[{}]","")
| rex field=Description "Changed block tracking verification failed for disk \[(?<VMDK>[\w\.\-\[\]\/ ]+)\] on virtual machine \[(?<VM>[\w\.]+)\]; performing a full backup of the disk."
| table Timestamp,Computer,Jobid,Description,VMDK,VM
| sort -Timestamp
| stats count by VM
+3- Vaulter
- 16 replies
Hi
To monitor or configure alerts for Changed Block Tracking (CBT) failures in Commvault version 11.36, you can utilize the logging and reporting features available in Commvault. Here are the steps you can follow:
1. Check the vsbkp.log File: Regularly review the vsbkp.log file for entries that indicate CBT issues, such as using CRC for backups, which can be a sign of CBT failure. The log file is typically located at C:\Program Files\CommVault\Simpana\Log Files.
2. Configure Job Summary Reports: Set up Job Summary reports to monitor backup jobs. You can configure these reports to include details about backup jobs, which can help identify jobs that are taking longer due to CBT issues. To generate a Job Summary report:
- Navigate to the Reports section in the CommCell Console.
- Select 'Job Summary'.
- Configure the report to group by Client and include Virtual Server Agent jobs.
3. Monitor Alerts: While specific alerts for CBT failures are not directly mentioned in the documentation, you can configure alerts based on job duration or failure criteria that might indirectly indicate CBT issues. Use the Monitoring and Alerting setup in the Command Center to configure these alerts.
For detailed steps on monitoring and configuring alerts, you can refer to the following documentation links:
VMW0067: Change tracking for Virtual Machine has reported an error (VMware)
Regards,
Dheeraj Shetty
+3Unfortunately, considering we have around 40 media agents backing up over 15,000 VMs every day, these very manual steps are not feasible for us to complete each day. That is why I was hoping for a report or alert we could configure specifically for this information. Perhaps it is time for me to submit another CMR. LOL
+3- Vaulter
- 16 replies
Hi
I understand that you have more than 15,000 VMs being backed up regularly.
Could you consider using the Token Criteria Selection in the Alert to create a rule for the Error Code? This way, you'll be notified whenever a VM backup fails due to a CBT error with that specific Error Code."
Regards,
Dheeraj
+3I have configured this and will see if this gives us what we need. Thank you!
Alert Information
| Alert Category | : | Job Management |
| Alert Type | : | Data Protection |
| Alert Criteria | : | Job Failed, Job Skipped, Job Succeeded, No Data Protection, Job Succeeded with Errors, Job Started, Job Committed |
Alert Configuration
| Notification Types | : | |
| Reporting Criteria | : | Immediate Notification |
| User and User Groups(To) | : | [hidden] |
| Sender Name: | : | Commvault |
| Sender Address: | : | [hidden] |
| Agent Type Filter | : | All Agents |
Token rules
Err code Equals 19:857
Security
| User Groups - Role | : | master - Alert Owner |
+3- Vaulter
- 16 replies
+3I don't know if I configured the alert incorrectly or it just doesn't work. However, I have not received any alerts based on this despite seeing quite a few instances of CBT failures. I am still working to find a good way to be notified of these or to report on these so that they can be addressed in a timely manner.
+3I wasn’t able to get this info easily from Commvault, but found that the error was being sent to Splunk/syslog. I was able to create a report there. This query gets me a list of VMs that generated this error over the given time period.
index=[ours] sourcetype=[ours] "{91:461}"
| eval Timestamp=strftime(_time, "%Y-%m-%d %H:%M:%S")
| eval Computer=replace(Computer,"[{}]","")
| rex field=Description "Changed block tracking verification failed for disk \[(?<VMDK>[\w\.\-\[\]\/ ]+)\] on virtual machine \[(?<VM>[\w\.]+)\]; performing a full backup of the disk."
| table Timestamp,Computer,Jobid,Description,VMDK,VM
| sort -Timestamp
| stats count by VM
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.