The configuration backup runs every day within cron.daily, that means a random time betwen 3 AM and 22PM.
However, if backup-data is enabled, the configuration backup runs just before the backup-data runs. In other words it obeys the backup-data scheduled time.
This is just an implementation detail, please do not consider it a feature at all
@davidep I think that a really good feature will be the ability to export / restore selective config sections.
For example restore section from backup only for DHCP and networks and firewall.
Something like select a backup to be restored and have two options: Restore -all or Restore - specific.
And when you select Restore - specific you are presented with a list with checkboxes for each section.
The current backup implementation is designed for disaster recovery scenario. We can push it beyond this, like we’ve done for ns6 upgrade but it’s a risk and it’s very complex.
Modules selection is a possible enhancement, because we have the underlying data required for an implementation.
However resetting unique items, such as selectively restore/merge some parts is much more difficult. We need to merge different versions of the configuration database. Designing an UI for this task is even more difficult IMO.