Offline Upgrade Guidelines
![]() Important |
|
-
Cisco recommends performing online upgrade from HX Connect UI for hitless upgrade experience without any impact operations.
-
Offline upgrade requires the cluster to be shutdown.
-
Offline cluster upgrades require the node(s) to reboot. Applications running on the cluster during an offline upgrade are impacted because they do not have access to the HyperFlex storage during the cluster reboot.
-
Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one at a time.
-
Remote-to-Remote Upgrades in HXDP Release 5.5(2a) or HXDP Release 6.0(x)
-
Protected VMs: Once Site A is upgraded to HXDP Release 5.5(2a) or HXDP Release 6.0(x), there should not be any protected VMs under Other DRO. VMs under the Other DRO category on Site A, are moved to the Standalone tab in Site A.
-
Datastores: Once Site A is upgraded to HXDP Release 5.5(2a) or HXDP Release 6.0(x), there should not be any datastores listed for pairing under Other DRO. Datastores listed for pairing under the Other DRO category on Site A, are relocated to the Native Protection tab. At Site B, this reassignment only occurs during the upgrade process to HXDP Release 5.5(2a) or HXDP Release 6.0(x).
-
-
Offline cluster upgrades with nested vCenter is not supported.

Feedback