—
Name of the device and type to match the model abbreviation used to create the repository
sub-directory structure (for example, 3500, 3700, 4900, 7000).
Procedure
1
Log on to the device account using administrator privileges.
2
From the network device, to create the backup task and specify commands, type:
SWITCH# enable
SWITCH# config t
SWITCH(config)# kron policy-list cfgBackup
SWITCH(config-kron-policy)# cli show startup-config | redirect
tftp://<IP>/<device>/config/<name>_startup_TIMESTAMP.cfg
SWITCH(config-kron-policy)# cli show running-config | redirect
tftp://<IP>/<device>/config/<name>_running_TIMESTAMP.cfg
SWITCH(config-policy)# end
The static placeholder, TIMESTAMP, in the configuration file name is used, because a
variable is not available that inserts the date/time into the file name when the tasks are
executed. It is recommended that a script be deployed that processes the files with the
TIMESTAMP string present and transforms it into the date and time when the file was
created. Otherwise, subsequent executions of the configuration overwrite the prior
versions.
3
From the network device, to schedule the backup task, type:
SWITCH# conf t
SWITCH(config)# kron occurrence Daily0600 at 06:00 recurring
SWITCH(config-kron-occurrence)# policy-list cfgBackup
SWITCH(config-kron-occurrence)# end
SWITCH# conf t
SWITCH(config)# kron occurrence Daily1800 at 18:00 recurring
SWITCH(config-kron-occurrence)# policy-list cfgBackup
SWITCH(config-kron-occurrence)# end
4
To confirm scheduler update, type:
SWITCH# show kron schedule
Kron Occurrence Schedule
Daily0600 inactive, will run again in 0 days 19:08:36 at 6:00 on
Daily1800 inactive, will run again in 0 days 07:08:36 at 18:00 on
Guidelines for backing up system configuration files
|
128
