As I mentioned in Hotsync problems with new system, I rebuilt my hotsync target system yesterday. I installed a minimal installation of CentOS 7 to a new SSD, installed all its updates, set up a ZFS mirror on two spinners and mounted it at /var/lib/nethserver, then ran the nethserver-install per the docs. Once that finished, I logged into the server manager and uploaded a saved configuration backup that the previous system had taken earlier in the day, checking the box to download modules. And that’s where the trouble started…
Other than setting the system hostname (maybe–I’d already configured this during the CentOS installation) and time zone, I can’t see that any of the configuration settings from the old installation have carried forward. Specifically:
The IP address wasn’t set; the main interface was left as DHCP
The “organization contacts” weren’t set; they were left at defaults
The UPS support module wasn’t installed, nor were its configuration settings preserved
The trusted networks weren’t saved
None of the hotsync/rsyncd settings were preserved
I’m sure there are other issues; these are just the ones I’ve run across so far. It isn’t looking like restoring the configuration backup did anything useful at all–is this how it’s supposed to behave?
IIRC the cool thing is if you choose to restore the configuration backup during the first setup wizard it will install the previous installed nethserver-modules and configure them as-was.
EDIT: (see below) i’ll gues if you skip this during the first configuration wizard it will configure your system as-was after you manually installed the modules you used to have.
I tested it now and it seems config backup does not work when hotsync is installed.
If you do a config backup on a hotsync system there is no error but no backup. Could it be you restored an old backup (maybe the first automatic one after initial configuration)?
I assume hotsync syncs the master config backup to the slave so it is not allowed to overwrite it. (or it’s a bug?)
AFAIK the config restore process restores the complete configuration in any case (no matter if done in first config wizard or manually afterwards).
It works for @danb35 so maybe my test VM tricks me here, I’ll do some more tests.
I don’t know why you get these errors, on my Nethserver extraction works, maybe you don’t have write permission where you want to extract?
You should find the config database var\lib\nethserver\db\configuration and it should contain the current config values.
I am going to do further tests to find out where the error comes from.
Doesn’t look like it–I don’t get an error, but if I click the blue Create Backup, enter a description (like “test”), and then click the red Create Backup, the screen spins for a moment and then returns to the page–but without any additional entries. If I navigate away from that page and return, again, there are no new entries there.
Now it would be interesting if the backup file contained the correct (actual) config database. I’d like to find out if the error occurs at backup or at restore.
EDIT:
backup-config is disabled when hotsync slave role is enabled:
I assume the config backup of the slave is disabled to not conflict with the sync/promote process.