A few of my 800+ network nodes don't always have a successful NCM backup; I've come to recognize which ones they are, and new ones reported to have failures stand out in my memory. I investigate them, back them up manually, look for causes or explanations of why they didn't backup.
But my memory won't always be what it is today. Maybe it isn't what it was yesterday!
I'd like to see an entry in the daily NCM Backup Failure e-mail that includes the date of the last successful backup for any node that failed the most recent job. This should give me more information to investigate nodes that have not been backed up in a long time. Maybe the node was unmanaged and removed. Maybe its ssh certificate needs updating. But my team may not investigate this on a timely basis because they they "It didn't successfully backup last night, but it probably did the night before, and probably will tonight." This kind of thinking can lead to nodes that haven't been backed up in years.
I envision this right inline with the failure notice. Even better, it should not only include the date and time of the last successful backup, but also calculate the days since the last backup and display them in the same e-mail.
I already have two Backup Status reports (running-config and startup-config) in NCM, which can be edited and scheduled . . .
But why generate more reports & e-mail when the needed info could be included in the backup failure e-mail?
Make it so?
