Backup Config Module - Beta - Final stage

ok thank you for info…

@davidep another test, all ok for me…
i know that now there is fantastic button to download backup config, but what do you think to add in the Backup configuration tab a check button like: copy latest backup config in the same destination folder of backup-data?
so we can have an automatic external backup of data and configuration…
and yes, i know i’m really lazy :slight_smile:

1 Like

I think that already happens when backup-data runs! I expect also the entire history is included in backup-data.

My plans for the future are merge the “Backup (data) and Backup (configuration)” pages together and allow restore of data from the UI, too. But this is another discussion…


yes, is inside the backup, but i think it could be useful to have the backup-config.tar.xz visible directly on the backup folder, as single file. So if i need to restore a ns7 i could
1 install ns7
2 restore config (taken from my folder on nas or webdav)
3 restore full or part of data (the configuration settings was restored in point 2)
i could also simply take the config backup from nas to create a clone of installed ns7

and yes i can also use the download button and store locally the backups :slight_smile:
in any case it will be really useful when creating testing VM, tnx

i like this plan :grin:

It already works like that in the current version! I was talking about it with @giacomo this morning :smile:

If backup-config.tar.xz does not exist in /var/lib/nethserver/backup/ dir, the restore-config command attempts to extract it from the backup-data.

You need to configure the backup-data destination, though…

We could allow this operation from UI: kinda "restore configuration from backup data set"
We could add an action to “post-backup-data” event that copies the configuration backup to the mounted backup device.

Edit: @dz00te, do you think the full history would be useful (/var/lib/nethserver/backup/history/ directory and its contents)? Or the current archive only is enough (/var/lib/nethserver/backup/backup-config.tar.xz file)?


@davidep did you code the netgui upload plugin that you promised me :wink:

I just installed it it looks nice


yes but as i said i’m a litlle bit lazy :grin:

yessss!! great :slight_smile:

for my use case i think the current archive is enough, but honestly i don’t know if there are other scenarios where history might be useful… if someone else is interested, it’s time to talk :slight_smile:

1 Like

I definitely agree! Furthermore, the history/ subdir still can be restored from data-backup by “Restore files” page or restore-file command.



Just reinstalled my scapegoat. Need a foolish tester for this beta module?

1 Like

We always need the most foolish ones! :smiley:

Be kind, put a little more… focus about install. I had to search throught the topic …

yum --enablerepo=nethserver-testing update nethserver-backup-config nethserver-lib

Little feature request: can a description be edited after the end of the backup?
Also: config let choose how many sets you want to retain, but not timing…

What do you think if I split this discussion? So I can move it into the testing category, close the old one and avoid people to read through several posts.

1 Like

I wouldn’t implement a double condition, too complex!

If I set a rule like “clean up configuration backups older than T”, it can conflict with “keep up to N configuration backups”. If N is big enough, it is surely a super-set of T.

Not at the moment, sorry.

The information is stored in a .json file under


I agree with Davide.
Adding a time based removal will not be good.
Let’s say that you set yor removal limit to be 6 months.
What will happen if you do not check the server in 7 ?

I think that number of backups to be saved in history is the best approach.

The one feature that i wanted to add but did not complete it, was to be able to send the backup over email.

That is a nice feature to have in my opinion :blush:

1 Like

Sorry for not using a correct expression.
I was not asking an expire time for the backupset. But a schedule for when the backup is done…

Or that’s not a feature?

For the description issue, maybe a little note into help file could explain this feature

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 :slight_smile:

@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.

What do you think?


Well, it would be a wonderful feature!

Why do you think it is useful? What scenario are you thinking about?

I was thinking about a similar thing, where individual modules can be included/excluded by the restore procedure.

I want to use a config-backup like a “system template” that can be adapted on individual instances…

Exactly! You can use it as a system template.
Also with the posibility to reset unique items maybe…

The second scenario is when you modified yesterday only the DNS and Users settings and do not want to revert also the users but only DNS.

The idea to Remove modules based on restore is great.

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.

1 Like

The backup config module has been released:

@translations_team the following resources need translations: