Category:Cisco Systems -> Routing and Switching
Hostname in Path
R1(config)#archive
R1(config-archive)#path tftp://172.16.1.10/R1
R1(config-archive)#exit
Hostname Variable in Path
R1(config)#archive
R1(config-archive)#path tftp://192.168.2.2/$h
R1(config-archive)#exit
R1#archive config
!!
R1#show archive
The next archive file will be named
tftp://172.16.1.10/R1-2
Archive # Name
0
1 tftp://172.16.1.10/R1-1 <- Most Recent
2 tftp://172.16.1.10/-2
3 tftp://172.16.1.10/-3
4
5
6
7
8
9
10
11
12
13
14
Time Variable in Path
We could also configure a time variable in the naming convention of the archive configuration. This is to have the date in the name of the file in the TFTP backup folder.
R1(config)#archive
R1(config-archive)#path tftp://172.16.1.10/$h-$t
R1(config-archive)#exit
Archive Write-Memory Option
R1(config)#archive
R1(config-archive)#write-memory
R1(config-archive)#exit
If we execute the “write memory” or “copy running-config startup-config” commands we can see that the configuration is automatically stored in the TFTP folder.
Archive Time-Period Option
R1(config)#archive
R1(config-archive)#time-period 10080
R1(config-archive)#exit
The next backup will be performed in one week exactly (time in minutes),
KRON
R1(config)#kron policy-list CONFIGURATION_BACKUP
R1(config-kron-policy)#cli write memory
R1(config)#kron occurrence Backup BACKUP_OCCURRENCE at 9:00 25 recurring
R1(config-kron-occurrence)#policy-list CONFIGURATION_BACKUP
Now the router will execute the configuration backup every 25th at 9:00 AM.
By privilege15NOTE
We could also use EEM in order to automate this process.
