@wblinger sorry, I wasn’t clear before: to put again in production you now have to launch
hotsync-slave is executed every hour, it’s useful to give it by hand only in testing environment. It take the list of NethServer packages installed on master and install (or update) them without launching configuration scripts.
@Sebastian maybe hotsync-cockpit is in backup package list:
tar -xf /var/lib/nethserver/backup/backup-config.tar.xz -C / var/lib/nethserver/backup/package-list
nethserver-hotsync-update exent is executed automatically after package installation/update. Every nethserver package launch signal-event $NAME-update
You can use slave as new master (I’m not sure if I got the question)
signal-event nethserver-hotsync-restoreinstead of restoring config