Take snapshots before and after updates. Use the Bulk Action tool in the web interface to snapshot your VMs prior to beginning any update.
Refresh the web interface after updates complete. The web interface services, as well as many other management services, restart when an update is applied. Make sure your browser is displaying the correct information with a hard page refresh.
Update target clusters before primary clusters when using remote connections and/or replication. It may be a required action to update to the latest SC//HyperCore software version when troubleshooting issues with Scale Computing Support.
Software updates cannot be rolled back. After updating to a new SC//HyperCore software version, either through an in-place update or a full software update, you will be unable to revert to the previous SC//HyperCore version.
Check the Ansible Collection for SC//HyperCore compatibility information at Ansible Galaxy for the latest tested component and SC//HyperCore versions.
Software update timing
No-hassle, non-disruptive software updates that require node reboots take time — about 30 minutes per node for each update is typical. Updating from older versions may take slightly longer, so plan accordingly. The web interface will be unavailable for the duration of the update, but remote access to VMs will continue to function normally.