The Cisco configuration archive provides a mechanism to store, organize, and manage an archive of Cisco configuration files
to enhance the configuration rollback capability provided by the
command. Before this feature was introduced, you could save copies of the running configuration using the
destination-url command, storing the replacement file either locally or remotely. However, this method lacked any automated file management.
With the Configuration Replace and Configuration Rollback feature, you can automatically save copies of the running configuration
to the configuration archive. These archived files serve as checkpoint configuration references and can be used by the
configure replace command to revert the configuration to a previous state.
archive config command allows you to save Cisco configurations in the configuration archive using a standard location and filename prefix
that is automatically appended with an incremental version number (and optional time stamp) as each consecutive file is saved.
This functionality provides consistent identification of saved configuration files. You can specify how many versions of the
running configuration are kept in the archive. After the maximum number of files are saved in the archive, the oldest file
is automatically deleted when the next, most recent file is saved. The
show archive command displays information for all configuration files saved in the configuration archive.
The configuration archive, in which the configuration files are stored and available for use with the
configure replace command, can be located on the following file systems depending on your platform:
If your platform has disk0:—disk0:, disk1:, ftp:, pram:, rcp:, slavedisk0:, slavedisk1:, or tftp:
If your platform does not have disk0:—bootflash:, ftp:, harddisk:, http:, pram:, rcp:, tftp:, usb0:, or usb1: