Specifications

clear boot backup-configuration
Chapter 20
File Management Commands
579
The maximum supported file size is 32 MB. If the file size of the tarball is too
large, delete unnecessary files (such as unneeded copies of system image files)
and try again, or use the critical option instead of the all option.
Neither option archives image files or any other files listed in the Boot section of
dir command output. The all option archives image files only if they are present
in the user files area.
Archive files created by the all option are larger than files created by the critical
option. The file size depends on the files in the user area, and the file can be quite
large if the user area contains image files.
The backup command places the boot configuration file into the archive. (The
boot configuration file is the Configured boot configuration in the show boot
command’s output.) If the running configuration contains changes that have not
been saved, these changes are not in the boot configuration file and are not
archived. To make sure the archive contains the configuration that is currently
running on the UNIVERGE WL Controller, use the save config command to save
the running configuration to the boot configuration file, before using the backup
command.
Examples
The following command creates an archive of the system-critical files
and copies the archive directly to a TFTP server. The filename in this example
includes a TFTP server IP address, so the archive is not stored locally on the
UNIVERGE WL Controller.
PROMPT# backup system tftp:/10.10.20.9/sysa_bak critical
success: sent 13082 bytes in 0.052 seconds [ 251576 bytes/sec]
success: received 13082 bytes in 0.227 seconds [ 57629 bytes/sec]
success: backup complete.
See Also
l dir on page 584
l restore on page 592
clear boot backup-configuration
Clears the filename specified as the backup configuration file. In the event that
UNIVERGE WL Control System cannot read the configuration file at boot time, a
backup configuration file is not used.