Migrating and restoring settings to new system.
When a new appliance or hardware is required, migrating settings from an existing installation is the easiest way of getting the new hardware configured as a replacement.
A full archive from the original Smoothwall system containing all system settings can be used to restore almost all settings from the original system to the new one. It is recommended to update the original and the new system to the latest update levels before creating and restoring the system settings archive.
Backup archives are defined and created in System - Maintenance - Archives
TIP: Schedule a reboot in 5 mins time right before you perform the restore of settings. This can be done in the System - maintenance - reboot menu. Then restore settings on the new system and let it reboot on it's own.
NOTE: Restoring ethernet settings could previously cause issues due to MAC address matching. This is no longer an issue after Leeds-40. Ethernet settings can be restore to a new system and will be implemented in the correct order. NIC1 to NIC 1 and so on.
Different number of network cards, remapping interfaces
It may be needed to remap some interfaces if the new system has a different number of network cards. In those cases, disable the existing interface and configure the new one with the same IP and settings. Then make sure all references in the Network - Configuration and Network - Firewall menus to the old interface are changed to use the new interface. Once done, delete the old interface. If you get an error deleting the old interface IP, it means there is still a direct reference to that interface in the config. Check all menu items in networking again, DNS and Link Load Balancing sections are often overlooked.
Use available network card for access during migration
If there is an available network card, configure that for admin access on an unrelated subnet before migrating settings from the original system.
That access can be used once the settings have been restored to the new system, to allow for admin access to the system, without connecting any of the other interfaces to the network. This will keep the new system isolated while settings can be checked to see if everything has been transferred correctly.
After a migration, before a reboot, the admin UI may not start initially on the new system. SSH access on port 222 will be available - which brings us to this note:
NOTE: The root user password is not restored - this will have to be reset manually. Login to the console as root using 'smoothwall' as password and change the root password using the 'setup' program or the 'passwd' command.
Use the console access as root top reboot the new system (use the 'reboot' command) if you have note scheduled a reboot earlier.
Swapping out the systems
When settings have been confirmed, power off the new system and unplug the original one. Plug in the new system and power it on - let it bring up all the services while it is connected to the network. Once up, connect to the admin UI and check settings and test network connectivity.
NOTE: The admin UI is the last service that starts up. The interface and the SSH service is brought up fairly early so check those to see if the