Before you update

Follow these steps before you update SC//HyperCore, so the update goes smoothly and you can recover if something goes wrong.

Product: SC//HyperCore

Software updates can’t be rolled back. After you update to a new SC//HyperCore version, through an in-place update or a full software update, you can’t revert to the previous version.

Plan for the update

Updates that require node reboots take time. About 30 minutes per node is typical, and updating from an older version can take longer. The web interface is unavailable during the update, but remote access to your VMs continues to work.

Steps

  1. Check the update path. Confirm the supported path from your current version in Update paths. Check its update barriers too: some releases must be installed before you can update further.
  2. Check your hardware. Make sure your nodes aren’t excluded from the release. See Compatibility and end of life.
  3. Take snapshots. Use the Bulk Action tool in the web interface to snapshot your VMs before you begin.
  4. Update target clusters first. If you use remote connections or replication, update target clusters before primary clusters.
  5. Check integrations. If you use the Ansible Collection for SC//HyperCore, check its documentation on Ansible Galaxy for the latest tested component and SC//HyperCore versions.
  6. Run the update.
  7. Refresh the web interface. Management services restart during an update. When it completes, do a hard refresh in your browser so it shows current information.
  8. Take snapshots again after the update completes.

Scale Computing Support may ask you to update to the latest SC//HyperCore version when troubleshooting an issue.