Identify and Retry Failed Backups using Ola's Solution

I ran into a situation where a database backup would fail due to a network error - specifically "Operating system error 59(An unexpected network error occurred.)" This post pertains to those using the Ola Hallengren backup solution, but the concept and/or approach could likely be applied to other backup solutions as well.

When the solution iterates through the databases to be backed up, it may succeed on all but one or two but the job as a whole would report a failure. In this scenario, you wouldn't want to re-run the entire job or configure the job step to use the Retry attempt/Retry Interval options, as that would result in all databases getting backed up again. That would consume unnecessary resources. The ideal solution would identify only those database backups that failed and retry those. With Ola's solution, we can identify and retry failed backups by querying the CommandLog table and running a subsequent backup script - click on the article to get the script!