When real-time change detection is enabled and a change is made have it backup both the running and startup configurations at the same time. Otherwise now the backups you have are out of sync.
Had this in one of your competitors products.
I'm not sure if this is worth it. If the person who is making the changes doesn't write off the config, they will be out of sync anyways.
Once a week, I get a report that compares the running to the startup config and any that don't match, get listed in the report. Basically means that those configs weren't written off.
What might be useful here is if the RCD set some kind of flag indicating that the configurations were 'dirty'
This could then drive a periodic backup job that backups up such configurations (in our environment with junipers we have two commits per change since we use the automatic roll-back functionality as a safety measure for someone accidentally cutting themselves off from a router/switch)
The same flag could be set if a backup fails for some reason, so a catch-up job could re-run failed backups.
We do the same thing. Once a week a report is generated to confirm both are the same.
