This package is not supported in NethServer Enterprise
HotSync should be considered a beta release. Please test it on your environment before using in production.
For a correct restore, it’s suggested to configure HotSync on two identical servers or two servers with same network cards number, name and position. If the master and slave servers differ, the restore procedure may behave unexpectedly (see Troubleshooting).
If you have configured slave host before release 2.2.0, update to a newer one on master and slave with yum update -y nethserver-hotsync –enablerepo=nethforge or from Software Center. After that, on slave host, launch signal-event nethserver-hotsync-save or do it from Cockpit HotSync interface by pressing Save button.
HotSync aims to reduce downtime in case of failure, syncing your NethServer with another one, that will be manually activated in case of master server failure.
Normally, when a hardware damage occurs, the time needed to restore service is:
fix/buy another server: from 4h to 2 days
install OS: 30 minutes
restore backup: from 10 minutes to 8 hours
In summary, users are able to start working again with data from the night before failure after a few hours/days. Using HotSync, time 1 and 3 are 0, 2 is 5 minutes (time to activate spare server). Users are able to start working again in few minutes, using data from a few minutes before the crash.
By default all data included in backup are synchronized every 15 minutes. MariaDB databases are synchronized too, unless databases synchronization isn’t disabled. Applications that use PostgreSQL are synchronized (Mattermost, Webtop5) unless databases synchronization isn’t disabled.
MASTER is the production system SLAVE is the spare server
SLAVE is switched on, with an IP address different than MASTER
Every 15 minutes, MASTER makes a backup on SLAVE
If an error occurs, an email is sent to root (admin if mail server is installed)
SLAVE check updates and makes some system operations every 60 minutes
Install nethserver-hotsync on both MASTER and SLAVE from Software Center or execute from command line:
yum install -y nethserver-hotsync --enablerepo=nethforge
You can configure HotSync from Cockpit interface: access it from Master and Slave, select role and fill required fields with password and IP.
<PASSWORD> must be the same on master and slave.
You can also configure HotSync from command line using these commands:
[root@master]# config setprop rsyncd password <PASSWORD> [root@master]# config setprop hotsync role master [root@master]# config setprop hotsync SlaveHost <SLAVE_IP> [root@master]# signal-event nethserver-hotsync-save
[root@slave]# config setprop rsyncd password <PASSWORD> [root@slave]# config setprop hotsync role slave [root@slave]# config setprop hotsync MasterHost <MASTER_IP> [root@slave]# signal-event nethserver-hotsync-save
If mysql or postgresql are installed, they will be synchronized by default. You can disable databases sync from Master Cockpit interface or from command line on master machine with this command:
[root@master]# config setprop hotsync databases disabled [root@master]# signal-event nethserver-hotsync-save
If you are using HotSync to restore FreePBX leave databases enabled, otherwise FreePBX database will not be restored properly.
HotSync is enabled by default. To disable it uncheck the checkbox into HotSync Cockpit GUI or use this command:
[root@slave]# config setprop hotsync status disabled [root@slave]# signal-event nethserver-hotsync-save
and to re-enable it re-check the checkbox on interface or use CLI:
[root@slave]# config setprop hotsync status enabled [root@slave]# signal-event nethserver-hotsync-save
After HotSync is configured, it’s a good practice to launch
hotsync command on master host. After master has properly syncronized, access the slave and execute
You can force these commands also from Cockpit GUI and check
/var/log/messages logs. As best practice, the first syncrhonization should be done via command line to better check if everything is properly configured.
After HotSync is configured and
hotsync command executed properly, note that
hotsync-slave command must be executed at least one time before proceed with
hotsync-promote. You can launch it manually or wait 60 minutes for automatic execution.
Restore: put SLAVE in production¶
The following procedure puts the SLAVE in production when the master has crashed.
Switch off MASTER.
If the SLAVE machine must run as network gateway, connect it to the router/modem with a network cable.
On SLAVE, if you are connected through an SSH console, launch the
screencommand, to make your session survive to network outages:
As best practice, execute following procedure using a local console and not via SSH connection.
on SLAVE launch the following command, and read carefully its output
If no Internet connection is detected (e.g. you are restoring a firewall on a machine that was passing through crashed master for Internet connection), the scripts will purpose you some options
1. Restore master network configuration (IMPORTANT: use this option only if two servers are identical - NIC number, names and positions must be identical) 2. Fix network configuration from Cockpit GUI (when restoring on different hardware) 3. Continue without internet: assign correct roles before proceed with this option. Some events could fails (not recommended)
else restore will start automatically. If you are restore on different hardware you could encounter DC errors.
When restoring on identical hardware choose option 1 and network configuration will be overwritten, else choose option 2. It’s not recommended to start the promote procedure without Internet access. When restoring on a different hardware and you’ve choosed option 2, you can encounter DC errors. Please see Troubleshooting.
If necessary go to Server Manager or Cockpit GUI, in page
Networkand reassign roles to network interfaces as master one. Remember also to recreate bridge if you have configured DC. In case of DC errors consult troubleshooting section before proceed with network restore.
After everything has been restored, launch the command
[root@slave]# /sbin/e-smith/signal-event post-restore-data
Update the system to the latest packages version
[root@slave]# yum clean all && yum -y update
If an USB backup is configured on MASTER, connect the backup HD to SLAVE
After restore on different hardware DC is not working¶
Console could report some errors like these
[ERROR] /usr/libexec/nethserver/sambads: failed to add service primaries to system keytab Action: /etc/e-smith/events/nethserver-mail-server-update/S50nethserver-sssd-initkeytabs FAILED
To solve this, restore network configuration as master (including bridges) and then launch
/sbin/e-smith/signal-event nethserver-dc-save /sbin/e-smith/signal-event nethserver-sssd-save
After restore permissions on ibays are not correct¶
Restore permissions from Cockpit GUI, under File Server, open shared folder menu and click on
After network restore server is unreachable¶
If you cannot reach server after a network reconfiguration, check configuration and, if it’s correct, try launching this commands
/sbin/e-smith/signal-event interface-update /sbin/e-smith/signal-event nethserver-firewall-base-update
If you cannot reach the server yet, use
Suggested check after restore¶
When all issues have been solved, please make that: - configuration is restored properly - all enabled services are working - applications interfaces (e.g. freepbx, webtop) are working - file server is working and users can log into shared folders - email server is working and users can send and receive emails - asterisk is working and users can make calls
Finally, reboot the system and check all services are working after boot.
All nethserver packages are supported. Here is a list of major NethServer packages:
nethserver-freepbx > 14.0.3
nethserver-webtop5 (z-push state is not synchronized)
Packages nethserver-ntopng and nethserver-evebox are reinstalled without migrating history.
To avoid errors on the slave host, do not make any changes to the modules from the Cockpit GUI except the HotSync module.