R3204P16-HP Load Balancing Module System Management Command Reference-6PW101

102
By default, the path and filename prefix for saving configuration files are not configured, and the system
does not save the configuration file periodically.
Before the running configuration is saved either manually or automatically, the file path and filename
prefix must be configured.
If the undo archive configuration location command is executed, the running configuration cannot be
saved manually or automatically. The configuration done by executing the archive configuration interval
and archive configuration max commands will restore to the default, and clear the saved configuration
files.
Examples
# Configure the path and the filename prefix for saving configuration files as cfa0:/archive/ and
my_archive respectively.
<Sysname> mkdir archive
.
%Created dir cfa0:/archive.
<Sysname> system-view
[Sysname] archive configuration location cfa0:/archive filename-prefix my_archive
archive configuration max
Syntax
archive configuration max file-number
undo archive configuration max
View
System view
Default level
3: Manage level
Parameters
file-number: The maximum number of configuration files that can be saved, which ranges from 1 to 10.
The value of the file-number argument is determined by the memory space. You are recommended to set
a comparatively small value for this argument if the available memory space is small.
Description
Use the archive configuration max command to set the maximum number of configuration files that can
be saved.
Use the undo archive configuration max command to restore the default.
By default, a maximum of 5 configuration files can be saved.
Because excessive configuration files occupy large memory space, you can use this command to control
the number of the files. After the maximum number of configuration files is saved, the system deletes the
oldest files when the next file is saved (either automatically or manually). When you change the
maximum number of configuration files that can be saved, the exceeded files are not deleted. If the
number of the existing configuration files is larger than or equal to the newly configured upper limit, the
system deletes the oldest n files when the next file is saved, where n = the current number - the newly
configured number + 1, for example: if the number of configuration files that have been saved is 7, and
the newly configured upper limit is 4, when there is a new configuration file to be saved, the system
deletes 4 oldest files, where 4 = 7-4+1.