Enabling automatic configuration archiving, Manually archiving running configuration, Rolling back configuration – H3C Technologies H3C S12500 Series Switches User Manual
Page 114
102
Enabling automatic configuration archiving
To avoid decreasing system performance, follow these guidelines when you configure automatic
configuration archiving:
•
If the switch configuration does not change frequently, manually save the running configuration
manually as needed.
•
If a low-speed storage medium (such as a flash memory) is used, archive the running configuration
manually, or configure automatic archiving with an interval longer than 1440 minutes (24 hours).
•
If a high-speed storage medium (such as a CF card) is used and the configuration of the switch
changes frequently, set a shorter saving interval.
Make sure you have set an archive path and file name prefix before performing this task.
To enable automatic configuration archiving:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable automatic
configuration archiving, and
set the archiving interval.
archive configuration interval
minutes
By default, this function is
disabled.
To view configuration archive
names and their archiving time,
use the display archive
configuration command.
Manually archiving running configuration
To save system resources, disable automatic configuration archiving and manually archive configuration
if the configuration will not be changed very often. You can also manually archive configuration before
performing complicated configuration tasks so you can use the archive for configuration recovery after
the configuration attempt fails.
Make sure you have set an archive path and file name prefix before performing this task.
Perform the following task in user view:
Task Command
Manually archive the running configuration.
archive configuration
Rolling back configuration
To ensure a successful rollback, follow these guidelines:
•
Do not remove or install a card while the system is executing the configuration replace file
command.
•
Make sure the replacement configuration file is created by using the configuration archive function
or the save command on the current device.
•
If the configuration file is not created on the current device, make sure the configuration file content
format is fully compatible with the current device.