Back Up a Configuration
There are a number of reasons for backing up your standalone (local mode) PacketShaper configuration:
- Your configuration may not load properly after upgrading to a new version of PacketShaper software.
- You could upgrade to a new release and then realize that you want to revert to a previous version.
- You might need to exchange your current PacketShaper for a different unit (for example, a newer model) and need to migrate files to the new unit.
- You can preserve the current configuration and use it to configure other units.
- You will be able to recover critical configuration files in the unlikely event of file corruption.
PacketShaper automatically stores your settings in a file named config.ldi. In addition, you can save a configuration on demand, using the config save CLI command. This command creates two files. The .ldi file contains the traffic tree configuration (including all classes, class IDs, partitions, policies, host lists), as well as all sharable configuration settings such as packet shaping, traffic discovery, passwords, SNMP, SNTP, and Syslog. The .cmd file contains the nonshareable settings such as IP address, gateway, date, time, and network interface settings.
You can also capture your traffic configuration and settings in an executable command (.CMD) file, using the setup capture CLI command.
Note that restoring a configuration by running a CMD file takes much longer (possibly hours) than loading a configuration (less than a minute). However, Blue Coat recommends that you create and back up the CMD file as a safeguard in case the config.ldi fails to load.
The setup capture command saves your traffic configuration and settings in an executable CMD file. If you ever need to restore the settings you captured, you can use the run command to re-create the configuration.
To save your settings in a CMD file:
- Decide whether to capture unit-specific details, such as the setup commands for the IP addresses. The complete format stores unit-specific settings; the portable format does not.
Enter one of the following commands:
setup capture portable <filename>
setup capture complete <filename>where <filename> is the name of the CMD file (such as backup.cmd); it is not necessary to type the .CMD file extension.
This ASCII file is saved in the 9.256/cmd folder and should be backed up to a client workstation.
Save the current configuration's sharable settings in an .ldi file and its nonsharable settings in a .cmd file. Shareable settings include the traffic tree configuration (all classes, class IDs, partitions, policies, host lists), as well as all sharable configuration settings such as packet shaping, traffic discovery, passwords, SNMP, SNTP, BCAAA, adaptive response, and Syslog settings. Nonshareable settings include IP address, gateway, date, time, and network interface settings.
A single CLI command creates the .ldi and .cmd file. Enter the following command:
config save <filename>
where <filename> is the name of the configuration file. The .ldi and .cmd extensions are automatically added to the configuration file name.
After creating the configuration backup files, you should copy them to a workstation's hard drive.
To transfer files from the PacketShaper to a workstation hard drive:
- At your workstation's command line (e.g., MS-DOS prompt), create
a folder where the backup files will be stored. Make sure that the
folder name identifies the specific unit so that the .ldi file
stored therein can be used to recover the unit.
- Open the PacketShaper's File Browser.
- Go to the 9.256/ folder and download the .ldi and .cmd text files you created with the config save command.
- Go to the 9.256/CMD folder and download the CMD file you created with the setup capture command.
(Optional) Go to the 9.256/CFG folder and download the conflig.ldi text file. This file can be backed up as an extra precaution, and could be useful when the unit is connected to PolicyCenter.
- Confirm the backup files are stored in the folder you created in step 1.