Hello Commvault Community,
I have a strange case where a connection loss occurred in the environment during an AG SQL backup, the Commvault system resumed the backup job for another attempt, but didn’t reset the Size of Application counter from the first attempt, which increased this parameter by x1.5 times, causing the Front-end license to be exceeded.
To clarify the situation, AG SQL in the case of Full Backup actually has 6.9 TB Size of Application - that's 22 databases. For example, a correctly performed backup tonight (from 21.01 to 22.01) for JobID [...]140, correctly recognized 6.9 TB Size of Application.
Last night (from 20.01 to 21.01) Full Backup was also performed and the network connection was interrupted (this isn’t the most important thing at the moment), then Commvault independently resumed the backup job in the second attempt, which ended correctly, but unfortunately the Size of Application from the first interrupted attempt was added to the second one, which was completed correctly.
This caused the AG SQL Full Backup job to indicate 11.1 TB instead of 6.9 TB according to the Size of Application parameter. Example of JobID [...]449:
This is important because in this environment where this happened there was a small of Front-end licenses, which is why the available licenses were exceeded and the data protection tasks stopped working.
I would like to know if this is the correct behavior of the system, that it counts all attempts made within the same task, or maybe it should ignore the Size of Application parameter from the failed attempt in the event of an unsuccessful attempt.
Thanks in advance!
Kind Regards,
Kamil
