Blue Coat Systems SGOS 4.x ユーザーズマニュアル
Chapter 2: Upgrade Behavior, General
9
Redoing an Upgrade from SGOS 3.2.4
When the initial SGOS 4.x upgrade occurs, any compatible configurations are converted. This only
happens the first time you upgrade; if you later downgrade to a pre-SGOS 4.x version by selecting an
earlier image on your system, make configuration changes, and re-install SGOS 4.x, the new SGOS
3.2.4 changes are not propagated to SGOS 4.x.
happens the first time you upgrade; if you later downgrade to a pre-SGOS 4.x version by selecting an
earlier image on your system, make configuration changes, and re-install SGOS 4.x, the new SGOS
3.2.4 changes are not propagated to SGOS 4.x.
To force the new system's configuration to be regenerated after changes are made to the older system's
configuration, you will need to force the upgrade conversion to occur again. Use the
configuration, you will need to force the upgrade conversion to occur again. Use the
restore-sgos3-config
command, which converts the current SGOS 3.x configuration to the SGOS
4.x configuration.
Note:
Previous force commands,
restore-sgos2-config
and
restore-cacheos4-config,
are not
available in SGOS 4.x; they can only be run from earlier versions.
The
restore-sgos3-config
command first checks if there are saved SGOS 3.2.4 settings on the
ProxySG. If not, the CLI command warns the administrator and exits.
If saved SGOS 3 settings exist, the
restore-sgos3-config
command warns the administrator that all
the current SGOS 4.x settings will be lost and that a restart will be initiated, waiting for positive
confirmation before clearing all the current SGOS 4.x settings, and then initiating a restart. The restart
(similar to a
confirmation before clearing all the current SGOS 4.x settings, and then initiating a restart. The restart
(similar to a
restart regular
) triggers the upgrade process, which copies over the SGOS 3 settings
and transforms them to the SGOS 4.x settings.
Redoing an Upgrade from SGOS 2.x or CacheOS 4.x
To downgrade to capture changes to the older version’s configuration, you must first launch the SGOS
3.x image, then select the SGOS 2.x or CacheOS 4.x version to launch. After you make the desired
changes, you must follow the upgrade path back to SGOS 3.2.4, using the
3.x image, then select the SGOS 2.x or CacheOS 4.x version to launch. After you make the desired
changes, you must follow the upgrade path back to SGOS 3.2.4, using the
restore-sgos2-config
or
restore-cacheos4-config
commands. (See Table 2.1 on page 7 for information on upgrade paths.)
The
restore-sgos2-config or restore-cacheos4-config
command first checks if there are saved
SGOS 2.x or CacheOS 4.x settings on the ProxySG. If not, the CLI command warns the administrator
and exits.
and exits.
Important:
Check for deprecation warnings after upgrading to 3.2.4 and before proceeding to SGOS
4.x.
4.x.
If saved settings exist, the command warns the administrator that all the current next version settings
will be lost and that a restart will be initiated, waiting for positive confirmation before clearing all the
current next version settings, and then initiates a restart. The restart (similar to a
will be lost and that a restart will be initiated, waiting for positive confirmation before clearing all the
current next version settings, and then initiates a restart. The restart (similar to a
restart regular
)
triggers the upgrade process, which copies over the settings and transform them to the next version
settings.
settings.