Prestaging the cluster node and solution upgrades

Last Updated : Mar 20, 2026 |
Prolog information
Use this procedure to prestage the cluster node and solution before upgrading them. Prestaging the upgrades does not disrupt service to Cluster Control Manager or cluster nodes.
Typical upgrade operations automatically download artifacts. While convenient, this can create lengthy maintenance windows. Prestaging upgrade artifacts helps minimize the duration of maintenance windows. Prestaging involves manually downloading the upgrade artifact to Cluster Control Manager before the upgrade operation.
Before you begin
Confirm the following are completed:
  • The configuration spreadsheet values are correct and saved to the file.
  • The solution configuration spreadsheet is transferred to Cluster Control Manager.
  1. Log in to Cluster Control Manager with your customer account.
  2. To run the prestage in the background, at the CCM prompt run the screen command.
  3. Run the ccm upgrade spec <solution-spreadsheet> --stage --calculate-size command to determine if Cluster Control Manager and the cluster registry have enough space to host the solution artifacts.
    ADDITIONAL INFORMATION:
  4. Run the ccm upgrade spec <solution-spreadsheet> --stage command to download and stage the flex-vsphere artifact, solution charts, and solution container images.
    ADDITIONAL INFORMATION:
    The staging can take over 50 minutes depending on the size of the solution container images and the number of charts.
  5. At the prompt to accept the terms of the EULA, enter y.
    ADDITIONAL INFORMATION:
    You must accept the EULA for the upgrade to continue.
    The prestaging can take over 50 minutes depending on the size and number of charts.
    CCM upgrade
  6. Run ccm upgrade spec <solution-spreadsheet> --status to verify that the prestaging is complete.
    ADDITIONAL INFORMATION:
    Note:
    When prompted to create a backup after the CCM upgrade, enter N because a backup is created during prestaging.