Planned Activity Precheck Review Case for vSphere vSAN
search cancel

Planned Activity Precheck Review Case for vSphere vSAN

book

Article ID: 386336

calendar_today

Updated On:

Products

VMware vSAN VMware vSAN 6.x VMware vSAN 7.x VMware vSAN 8.x

Issue/Introduction

Note: The Planned Activity Precheck Review outlined in this KB is available only to Advanced Support customers with a Support Account Manager (SAM) and/or Dedicated/Designated Support Engineer (DTSE/DSE). 

The Planned Activity Precheck Review is provided on a best effort basis and is intended to assist with identified issues and precheck failures. While Broadcom Support strives to highlight potential risks, this review is not exhaustive and may not identify all issues or environment-specific considerations. It is not a commitment to participate during the planned activity nor is it a certification or validation of a runbook. The customer remains responsible for validating their activity plan and ensuring their environment if fully prepared for the change. 

Prerequisites before opening a Planned Activity Precheck Review for vSAN:

  • Cases must be opened at least 10 business days in advance of the upgrade window.
  • Cases should be opened as Low-P4.
  • Have a development environment upgraded before production to test that any customization still functions as expected on the latest version.
  • Upgrade pre-checks must be run in advance and report any issues that cannot be resolved.
  • Collect the vSphere vSAN log bundle and upload to the new case.
  • Read the target version Release Notes and be aware of Known Issues.
  • Reference the Interop Matrix to confirm the target vSphere vSAN version is compatible with other integrations in the environment and plan to upgrade those if necessary. Also confirm the vSphere ESXi upgrade path is supported.
  • If this is a VCF environment, open a Planned Activity Precheck Review Case with VCF Support.
  • Validate there are good backups.
  • Walk through Verify the health of vSAN.
  • Be familiar with VMware vSAN Upgrade Best Practices

VMware by Broadcom Support will: 

  • Ensure precheck issues are resolved.
  • Validate the target version and advise if a newer one is available.
  • Review provided logs for known issues that may impact the upgrade.
  • If a Planned Activity Precheck Review case is not raised with sufficient notice of 10 days, it may not be possible to offer log review and precheck resolution within the planned timeframe. 
  • Once the review is complete, the Planned Activity Precheck Review case will be closed.
    • Two days prior to the upgrade, either you or your SAM/DTSE/DSE will open a maintenance case. This case will track the upgrade and can be uplifted to a Critical - P1 in the event of a production down outage during the upgrade. 
    • The next available support engineer will engage with you. Broadcom will not be able to provide dedicated support to be on standby during the activity. 

Please complete the following template when opening the Case: 

  • Upgrade Date & Time:
  • vSphere vSAN from version:
  • vSphere vSAN to version:
  • Server Make & Model
  • Number of HBAs
  • Make & Model of HBAs
  • Firmware of HBA
  • Current Driver version of HBA
  • Drive Make and Model
  • Drive firmware
  • Current remaining space utilization percentage?
  • Please copy and paste any triggered alarms/alerts in vSAN Health Check
  • Current On-Disk format version?
  • Features enabled?
    • Deduplication
    • Compression
    • Encryption
    • Stretch Cluster
    • vSAN File Services
  • Storage Architecture being used?
    • OSA - Original Storage Architecture
    • ESA - Express Storage Architecture
    • Both
  • Upgrade Prechecks Passed?:  
  • 2 or more upgrade paths required?
  • Please comment on any other environmental changes expected (provide runbook)

Upgrade Recommendations:

  • It is recommended to retain locally the vSphere vSAN logs collected when opening the Planned Activity Precheck Review Case until the upgrade has completed successfully.
  • Prepare a contingency plan to allow the upgrade maintenance window to be extended should a failure occur.
  • Schedule a maintenance window for the entire upgrade so that VMs can be powered off to make backups.  Make sure there are good backups just prior to the upgrade.  A good backup is one that restores have been tested and everything boots as expected.  Powered off snapshots can provide a quick rollback point and are also required before starting the upgrade.
  • Have full cold backups of the nodes in case a roll back is necessary if the upgrade is unable to be completed before the maintenance window.
  • If 2 or more upgrade should be performed in line, take the latest snapshots after last upgrade completed.
  • If an upgrade failure occurs, please request an uplift in case severity.

Environment

  • VMware vSAN 8.x
  • VMware vSAN 9.x

Resolution

Open a Low - P4, Planned Activity Precheck Review case via Broadcom Support portal. 

The purpose of a Planned Activity Precheck Review case is to prepare in advance for the vSAN upgrade.

If an issue is experienced during upgrade that causes a production down outage, Advanced Support customers should uplift the severity of the case to a Critical - P1.

This is not an exhaustive health check of the environment. If this is required, engage VMware by Broadcom Professional Services.

Additional Information

For further Planned Activity Precheck Review guidance, please see the Planned Activity Precheck Review - Broadcom Advanced Support KB which details the process and includes all VCF specific products this is offered for. 

Powered by Wolken Software