configuration backup local disable

Usage Scenario

To automatically back up the current running configurations to the local storage after the device configurations are modified, run the undo configuration backup local disable command to enable automatic backup of the current running configurations. This function helps check historical records of configuration changes and facilitate fault location.

Precautions

• When the device is enabled to back up the current running configurations, the current running configurations are backed up 2 hours after the device configurations are modified. If saving or automatic saving operation is performed, conflicts may occur. The configuration backup will be triggered every 30 minutes until the backup succeeds.
• If the CPU usage exceeds 60% during the configuration backup, the configuration backup will be triggered every 30 minutes until the backup succeeds.
• Delivering a configuration command fails during the configuration backup.
• If the current configurations are consistent with the configurations saved last time, the device does not repeatedly back up the current configurations to the local storage.

Rules for backup file management:

• The local storage path is $_backup/running_config/.
• The format of the backup file name is yyyymmddhhmmss.sysname.zip, where yyyymmdd indicates the year, month, and day, hhmmss indicates the hour, minute, and second, and sysname indicates the host name of the device.
• Backup files are aged based on the aging rules each time when the number of backup files exceeds 30, when the total space used by backup files exceeds 10 MB, or when the remaining storage space is less than 30 MB.
• The backup file aging stops when the number of backup files is 5 or less.

Rules for backup file aging:

• A number and an aging priority are specified for a backup file based on the file generation time.
  

  File number: The latest file generated is numbered 1, the file generated before the latest file is numbered 2, and so on. A larger number indicates an earlier generation time.

  File aging priority: The file with a smaller file number has a higher priority. Files with a lower priority are aged first. Note that files with priority 0 are not aged. If a file has multiple priorities, refer to the highest priority.

  • Priority 0: files numbered from 1 to 5
  • Priority 1: files numbered from 6 to 10
  • Priority 2: the last generated files on each day in the past week
  • Priority 3: the last generated files in each month in the past 5 months
  • Priority 4: other backup files
• Note for backup file aging:
  • The backup files are aged in time sequence based on the priority. A backup file generated earlier is aged first.