Advanced Boot and Backup Configuration Information > How Configuration Files Changes Are Managed

How Configuration Files Changes Are Managed
Changes to configuration files can be made without backing up the configuration files by performing the actions shown in the following table.
Changes made to the configuration files persist after a reboot. If you upgrade software, any changes to configuration files are brought forward after the upgrade. (This allows you to upgrade software on the OnSite without losing all your user configurations.)
Changes to configuration files can be both made and backed up in different environments on the OnSite by performing the actions shown in the following table.
Enter the saveconf command
Enter the CLI config savetoflash command
Saving a backup copy of the configuration files allows an administrator to restore the backed up configuration files even after a reboot or after a software upgrade to overwrite all changes made to the configuration files since the last save.
The system software updates the affected configuration files and creates a compressed copy of the configuration files in /mnt/hda3/backup/configuration_files.gz on the resident flash memory. If a compressed configuration file already exists in the backup directory, it is overwritten. The file and the backup directory are shown in the following screen example.
[[root@ONS /]# ls /mnt/hda3/backup
 
 
Backed-up changes to configuration files can be restored by performing the actions shown in the following table.
Enter the restoreconf command
Enter the CLI config restorefromflash command

Advanced Boot and Backup Configuration Information > How Configuration Files Changes Are Managed