SOHO NOTES DATABASE FILE ARCHIVE
There are currently 2 archive configurations saved. Note that configuration archival is performed separately from start-up configuration synchronization write or copy run start is still needed to save the running configuration to the default start-up configuration.Īfter archiving the configuration again, we see that there are now two copies in the archive: Now, to illustrate the benefits of configuration archiving, we'll configure interface FastEthernet1, which currently has no configuration, to support a routed link:ĭemarc(config-if)# ip address 192.0.2.1 255.255.255.0 The next archive file will be named flash:/archive/-1ġ28237568 bytes total (104632320 bytes free) There are currently 1 archive configurations saved. Looking at the archive again, we see the first configuration slot has been filled: Let's begin by archiving the router's current configuration with the archive config command:
The next archive file will be named flash:/archive/-0Īs you can see, the archive is currently empty. There are currently no configuration saved. The maximum archive configurations allowed is 14. We can view the current archive with the show archive command: Here we'll increase the default number of configurations stored to 14, since we have plenty of space on the filesystem, and enable weekly automatic archivals (seven days are equal to 10080 minutes).ĭemarc(config-archive)# time-period 10080 Here, we can also optionally set the maximum number of configurations to store at any time (the default is 10, maximum is 14), and/or enable automatic archiving with the time-period command. End with CNTL/Z.ĭemarc(config-archive)# path flash:/archive/
In the following example, we've created a directory appropriately named archive on the Flash filesystem.ġ -rw- 23587052 17:16:58 -05:00 .binġ28237568 bytes total (104640512 bytes free)Įnter configuration commands, one per line. To enable this feature, we enter archive configuration and specify a path where archived configurations are to be stored.
SOHO NOTES DATABASE FILE MANUAL
In such situations, where only one or few devices are present, it may not be justifiable or practical to run an on-site server dedicated for configuration backups.Ĭisco IOS includes a configuration archive feature which allows for the creation of both manual and automated configuration snapshots, stored locally on the router's own filesystem.
However, this approach is often poorly suited for the small office/home office (SOHO) and similar small-scale environments. Such a scheme is typically accomplished via automated FTP or SCP transfers to a centralized database, often integrated with a network management system like CiscoWorks. These backups can be used in an emergency to restore a device's configuration which was inadvertently altered or erased. In large enterprise and service provider environments, it is considered best practice to routinely back-up and archive the configurations of all network devices.
0 kommentar(er)
