Web Manager Introduction > Common Features of Administrative User’s Windows > Trying, Saving, and Restoring Configuration Changes

Trying, Saving, and Restoring Configuration Changes
The various options for trying, saving, and restoring configuration changes are summarized in the following table. Trying, saving, and restoring can be done in the OSD and on the Linux command line. The “Action” column shows the Web Manager actions.
Enter information in any of the screens and click the OK or Done button
The “unsaved changes button” appears and a red graphical LED blinks. Changes are held in memory and not saved.
 
Updates (saves the changes in) the appropriate configuration files. Changes are preserved if you log in and log out again and even if you restart the system. The changes are not backed up unless “apply changes” is clicked. You can restore the backed-up configuration files by clicking “cancel changes.”
Cancel changes
Click the “cancel changes” button
Restores the configuration files using the backup file that was created the last time changes were applied.
If “try changes” has not been previously clicked, updates the appropriate configuration files. The first time changes are “applied,” creates a compressed copy of the configuration files in a backup directory. Subsequently overwrites the backed-up copy of the configuration files.
See How Configuration Files Changes Are Managed for details about how to save, apply, and back up changes in the OSD and on the command line.

Web Manager Introduction > Common Features of Administrative User’s Windows > Trying, Saving, and Restoring Configuration Changes