Kerio Tech Firewall6 User Manual
Page 373
25.1 Configuration Backup and Transfer
373
star
The star directory includes a complete database for statistics of the WinRoute web inter-
face.
Handling configuration files
We recommend that WinRoute Firewall Engine be stopped prior to any manipulation with
the configuration files (backups, recoveries, etc.)! Information contained within these files is
loaded and saved only upon starting or stopping the MailServer. All changes to the configura-
tion performed while the Engine is running are only stored in memory. All modifications done
during Engine performance will be overwritten by the configuration in the system memory
when the Engine is stopped.
Configuration backup recovery
Configuration can be backed-up by copying all the previously described configuration and/or
status files.
To recover configuration through backed-up data (typically this need may arise when WinRoute
is installed to a new workstation or when the operating system is being reinstalled), follow
these steps:
1.
Perform WinRoute installation on a required machine (refer to chapter
).
2.
Stop WinRoute Firewall Engine.
3.
Into the WinRoute directory
(the typical path is C:\Program Files\Kerio\WinRoute Firewall)
copy files host.cfg, logs.cfg, UserDB.cfg and winroute.cfg from the back-up
4.
Copy license and SSL certificate subdirectories (license, sslcert and dbSSL).
5.
Copy all files and directories with status information (files Cache.CFS, dnscache.cfg,
leases.cfg
, ofclient.cfg, stats.cfg, vpnclient.cfg and directories logs and star).
6.
Run WinRoute Firewall Engine.
At this stage, WinRoute detects the required configuration file. Within this process, un-
known network interfaces (ones which are not defined in the winroute.cfg configuration
file) will be detected in the system. Each network interface includes a unique (randomly
generated) identifier in the operating system. It is almost not possible that two identifiers
were identical.
To avoid setting up new interfaces and changing traffic rules, you can assign new identi-
fiers to original interfaces in the winroute.cfg configuration file.
7.
Stop WinRoute Firewall Engine.