Management Center Upgrade & Downgrade Paths
Article ID: 169290
Updated On:
Products
Issue/Introduction
Version stepping requirements for upgrading or downgrading Symantec Management Center (MC).
Resolution
An upgrade or downgrade must stay within two minor versions of the current release. Skipping versions is not supported.
Version stepping examples:
To upgrade from 3.0.x to 3.3.x, first install 3.1.x or 3.2.x.
To upgrade from 2.4.x to 3.2.x, first install 3.0.x or 3.1.x.
Downgrades enforce the same two-version limit. A downgrade from MC 3.x to 2.x or 1.x is unsupported.
MC 4.1.1 and MC 4.1.2 only support direct upgrades from 3.3.5.x. Attempting to upgrade directly from any other 3.x version to 4.1.1 or 4.1.2 is not supported.
Execute these steps before applying a new image:
Create & offload a full configuration backup before the upgrade starts, and again after it completes.
Disable failover on both the primary and secondary nodes for active failover pairs.
For any 1.x release, consult the article Upgrading Management Center version 1.x to one of the latest supported versions to reach a supported baseline version.
Note other best practices when doing MC upgrade:
- Create and offload a backup before and after each upgrade.
- For Management Centers with failover setup, disable the failover on both (primary and secondary).
Additional Information
- Downgrading from 4.1.x to 3.3.x or earlier is not supported. The database structure in 4.1.1.1 introduces schema changes that can't reconstruct on older releases.
- To revert a 4.1.x node to 3.3.x, restore the appliance to factory settings & load a 3.3.x configuration backup
Feedback
