The Custom Strike Count report lists all clients and subclients that have at least one strike in your CommCell environment. The most recent failed or killed backup job on each client, subclient, or VM counts as a strike. This report can help you to identify the clients and subclients that consistently fail backups.
For full backups, only a successful full backup job resets the strike count to zero. However, for incremental and differential backups, a successful full, incremental, or differential backup job resets the strike count to zero. If a subclient has both full and incremental strikes, the highest number of strikes is displayed so that each subclient, client, and VM is counted only once in the Summary table. Synthetic Full backup jobs are not included in the strike count.
For some databases, backup jobs that are Completed with Errors count as strikes. For file systems, backup jobs that are Completed with Warnings and backup jobs that are Completed with Errors do not count as strikes.
Note: The Custom Strike Count report is not applicable for the laptop clients, DB command line clients, and system-initiated backup jobs, such as DDB backups.