Offline Upgrade Guidelines
![]() Restriction |
Offline Upgrade to HyperFlex Release 6.0(1a) is not supported. To upgrade to HXDP 6.0(1a) use the upgrade process found in Cisco HXDP Upgrade using HX Installer. |
![]() 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 6.0(1a)
-
Protected VMs: Once Site A is upgraded to HXDP Release 6.0(1a), 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 6.0(1a), 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 Standalone tab. At Site B, this reassignment only occurs during the upgrade process to HXDP Releae 6.0(1a).
-
-
Unmapping DRO datastore pairs simultaneously with any other Native datastore mapping or unmapping actions is not supported after upgrading the Site A and Site B clusters to HXDP Release 6.0(1a). Thus, unmapping of DRO datastores must be carried out individually.
-
Offline cluster upgrades with nested vCenter is not supported.