System information

How Configuration Changes Are Handled
60 AlterPath OnBoard Administrator’s Guide
How Configuration Changes Are Handled
The OnBoard handles changes to configuration files and backups of
configuration file changes differently from other Cyclades AlterPath
products. The following bulleted items give an overview of how the
OnBoard handles configuration changes:
• When an OnBoard administrator performs configuration tasks, changes
are stored in RAM memory until the administrator takes a specific action
to save the changes in configuration files.
• Unless changes are saved in configuration files, they do not persist after a
reboot.
• The OnBoard administrator can back up changed configuration files at
any time.
• Like other AlterPath products, the OnBoard maintains a backed up copy
of the factory-default configuration files.
• The OnBoard administrator can restore the factory default configuration
files or restore any backed-up copies of the configuration files.
• The current state of the configuration files is maintained after a software
upgrade. (This allows you to upgrade software on the OnBoard without
losing all user and device configurations.) After a software upgrade, the
administrator can optionally do the following:
• Return from the current state to the last backed-up copy of the
configuration files.
• Return to the factory default configuration files.
• When an OnBoard administrator adds a new application, script, or
configuration file to the system, the root user needs to add the pathname
to the file to the list of files to be backed up and restored.