NCM Backup Verification

Question

Does NCM do any sort of hash or other check to validate / verify backups taken from nodes?

My understanding is that NCM dumps the config and captures it, watching for a # to indicate the dump has finished.  I know you change the symbol it listens for in case # appears in the actual config:

NCM Hash symbol in config - SolarWinds Worldwide, LLC. Help and Support

What other checks does NCM make (if any)?  I was wondering if there's a situation where a backup is corrupt but "completes" so a failure isn't logged in the Transfer Status section.

Is this behaviour any different for devices which might present a binary file from the CLI eg CheckPoint?

Thanks!

jpetkevich · Accepted Answer

For binary configs we verify that the file exists in the appropriate folder and are unable to do any further validation.

For text files we also verify that they meet the minimum config line limits set within NCM.