2Management40Step 2:To make the uploaded configuration the current configuration, the following CLI command isused:Device:/> backup ‐restore <filename>Where filename is the name of the file in the backup folder.To list all files in /storage, use the CLI command:Device:/> backup ‐listWhen a restore begins, the selected file is validated before it replaces the currentconfiguration. For the new configuration to become active, the CLI commands activatefollowed by commit are required after the restore is complete.Important: Do not perform a restore operation with live traffic flowing through the securitygateway. Any traffic flows will be disrupted.Reverting a backupAfter performing a restore operation, the SEG retains a copy of the original configuration (thatis to say, the configuration that the restore replaced). This copy can be reactivated at any timewith the CLI command:Device:/> backup ‐revertA revert operation always uses the configuration in effect previous to the last restore if therewas one. If no restore has been performed, a revert operation will have no effect.Restoring the default configurationA special case of backup command usage for configuration restoration is:Device:/> backup ‐resetThis restores the default configuration for the security gateway. The current configuration issaved when this command is used so that the reset can be undone by using the command:Device:/> backup ‐revertRestoring to a dissimilar processorImportant: Restore a backup to the SEG that uses the same interface names as those used onthe original hardware from which the backup was taken. The reason for this is that the backupmay refer to logical interface names that do not exist on the new hardware.On the SEG‐100, there are two processors on each module (DPB1 and DPB2). These areidentical except for the naming of their Ethernet interfaces. If a configuration backup takenfrom the DPB1 processor is then restored to the DPB2 processor, the end result will be asdescribed in the next section.