The system is restored in two phases: configuration first, then data. Right after configuration restore, the system is ready to be used if the proper packages are installed. When the machine is functional, a full data restore can be performed while the machine is already in production. You can install additional packages before or after the restore. For example, if the mail-server is installed, the system can send and receive mails.
Other restored configurations:
- Users and groups
- SSL certificates
Do not restore a configuration backup from an old minor version into a newer version. The backup should come from a NethServer having the same operating system version of the new installation, i.e., avoid restoring a configuration backup from a 7.4.1708 installation on a new 7.6.1810 system, as it may lead to unexpected results.
New Server Manager¶
Please, follow below steps:
Install the new machine (refer to installation section), access the new Server Manager and make sure the machine is able to access the internet and resolve public names correctly
If the machine has a Community subscription entitlement, please follow Subscription, otherwise you can skip this step
Install all the available core updates from the Software updates
Access the Backup page and click on the Restore button under the Configuration Backup section, then upload the configuration backup or download it directly from an HTTP/S URL.
For NethServer Enterprise, all cloud backups will be automatically downloaded and ready to be restored directly from the From backup field.
Map network interface names from the backup to the running system.
Click the Restore to start the restore process.
If you’re connected to a network interface that will change the IP address during the restore, you will be disconnected from the Server Manager and you will need to login again using the new IP address.
Verify the system is functional and then access the Backup page. To restore all files, click on Restore button under the Data Backup section, select the name of the backup and click the Restore button.
Please bear in mind that the restore process can last from minutes to hours depending on the storage backend speed.
Old Server Manager¶
Please, follow below steps:
Ensure that NethServer is able to access the internet and resolve public names correctly
Install all the available core updates in the Software Center
Restore the configuration backup using the Backup (configuration) panel
If a warning message requires it, reconfigure the network roles assignment. See Restore network roles below.
Verify the system is functional
Restore data backup executing on the console
restore-data -b <name>
nameis the name of the data backup you want to restore from.
Please note that the disaster recovery should be always performed from a local media (eg. NFS or USB) to speed up the process.
The root/admin password is not restored.
Restore network roles¶
If a role configuration points to a missing network interface, the Dashboard, Backup (configuration) > Restore and Network pages pop up a warning. This happens for instance in the following cases:
- configuration backup has been restored on a new hardware
- one or more network cards have been substituted
- system disks are moved to a new machine
The warning message points to a page that lists the network cards present in the system, highlighting those not having an assigned role. Such cards have a drop down menu where to select a role available for restoring.
For instance, if a card with the orange role has been replaced, the
drop down menu will list an element
orange, near the new
The same applies if the old card was a component of a logical interface, such as a bridge or bond.
By picking an element from the drop down menu, the old role is transferred to the new physical interface.
Click the Submit button to apply the changes.
Choose carefully the new interfaces assignment: doing a mistake here could lead to a system isolated from the network!
If the missing role is
green an automatic procedure attempts to fix
the configuration at boot-time, to ensure a minimal network
connectivity and login again on the Server Manager.