The FW provides real-time configuration saving functions for you to save the configurations of the FW.
You can save configuration files on demand or set the system to save configuration files at regular intervals. This prevents data loss if the FW restarts without warning or when it is powered off.
Run one of the following steps to save configuration files.
By default, only the system administrator has the configuration saving permission.
For a non-system administrator to save configuration, the system administrator must run the non-system-admin save enable command to grant the configuration saving permission to the non-system administrator.
When the automatic saving function is enabled and the LPU is not correctly installed, corresponding configurations may be lost.
Access the system view.
system-view
Set an interval at which the configuration file is saved.
set save-configuration [ interval interval | cpu-limit cpu-usage |delay delay-interval ] *
If you do not run the set save-configuration command, the system does not automatically save configurations.
If you run the set save-configuration command without specifying interval, the system automatically saves configurations at an interval of 30 minutes.
When you configure the automatic saving function, to prevent that function from affecting system performance, you can set the upper limit of the CPU usage for the system during automatic saving. When automatic saving is triggered by the expiry of the timer, the CPU usage is checked. If the CPU usage is higher than the set upper limit, automatic saving will be canceled.
After you specify delay delay-interval, if the configuration is changed, the device automatically saves the configuration after the specified delay.
After you configure the configurations to be automatically saved, the system automatically saves the changed configurations to the configuration file for the next startup. Then, the configuration files change according to the saved configurations.
Before you configure the configurations to be automatically saved on the server, you must run the set save-configuration backup-to-server server server-ip [ vpn-instance vpn-instance-name ] transport-type { ftp | sftp } user user-name password password [ path folder ] or set save-configuration backup-to-server server server-ip [ vpn-instance vpn-instance-name ] transport-type tftp [ path folder ] command to configure the server, including the IP address, username, password of the server, destination path, and mode of transporting the configuration file to the server.
save [ all ] [ vsys vsys-name ] [ configuration-file ]
The extension of the configuration file must be .cfg or .zip. The system startup configuration file must be saved in the root directory of a storage device. The file name is case-insensitive, special characters (~/|\*:'"?) and spaces not supported. The value is a string of 5 to 48 characters, including a path. If no path is specified, the configuration file is saved in the default path.
You can modify the current configuration through the CLI. To set the current configuration as the initial configuration the next time the FW starts, you can use the save command to save it in the storage media.
You can use the save all command to save all the current configurations, including the configurations of the boards that have not been inserted, to the next startup configuration file.
When you save the configuration file for the first time, if you do not specify the optional parameter configuration-file, the FW asks you whether you want to save the file as "vrpcfg.zip". "vrpcfg.zip" is the default configuration file which initially contains no configuration.