As documented in the Backup article, if there are no changes to the config of your device, a new "backup" point is not required. So rather than show you individual backups, Unimus will show you configuration points - ranges of valid configurations on your device to build a configuration timeline of the device. To be able to do this, Unimus needs to be able to figure out if there was a config change on the device. For example, if the configuration of the device contains timestamp (Cisco IOS will show the current timestamp of when "show running-config" was executed), this needs to be ignored so this "change" in the configuration contents doesn't create a new configuration point. Unimus contains many built-in filters for such dynamic data (as mentioned in the Backup article), but you can also create your own custom filters for backup contents.

Filtering order:

• "Deleted data' filters
• Built-in "dynamic content filters"
• "Ignored data" filters

Ignored data filters

During comparison of the new backup to the currently stored backup, Unimus will IGNORE the matched data for the comparison purposes. The data will still be stored as a part of the backup, but if changes in the data happen, those changes iwll be ignored.

Deleted data filters

Before comparison of the new backup to the currently stored backup, Unimus will REMOVE the matched data from the "new" backup. This means that this data will not be stored as a part of the backup at all - as if this data was not received from the device at all.