Infrastructure Updates

It's possible that your Commerce VMSS configuration doesn't utilize all available resources. To mitigate that, SAP constantly rightsizes Commerce infrastructure to reduce the number of performance-related incidents and optimize infrastructure and resource allocation between the existing virtual machines. After the optimization, the virtual machines in the Kubernetes cluster can properly manage the existing pods.

The process of rightsizing your database happens only when the intended result:

• Meets your performance requirements.
• Meets the service level agreements between you and SAP.
• Minimizes the cost when other prerequisites are met.

The rightsizing process may cause several seconds of service interruption. SAP will contact you to plan the maintenance window so that you know when to avoid scheduling deployments and long-running database operations.

Database rightsizing minimizes infrastructure costs without affecting database performance.

Upgrading the image takes approximately 30-40 minutes long. To account for possible delays, a 4-hour-long maintenance period is allocated to each affected environment. The upgrade has the following impact:

• Non-production environments:

  • The affected environment is locked. It prevents all operations on it, including new deployments.

  • SAP Commerce Cloud applications are offline, including the APIs, the storefront, and Backoffice.

• Production environments:

  • The affected environment is locked.

  • SAP Commerce Cloud experience disruption or degradation.

• Data Hub (high-availability component unavailable)
• Platform - API
• Platform - background processing
• Dynatrace (delayed response time)

• JavaScript apps (delayed response time)
• Performance testing (possible loss of performance data)
• Platform - ACC storefront (delayed response time)
• Platform - Backoffice (Logged-in users are logged out. Unsaved changes are lost.)
• Search - Solr (possible Solr failure)

Upgrading the AKS image ensures that all SAP Commerce Cloud clusters running on Kubernetes use the latest features and security updates.

Upgrading the cluster is a zero-downtime operation, but it causes service disruption approximately 10-20 minutes long for development and staging environments and 15-45 minutes long for production environments. This locks the affected environment, which prevents operations, including new deployments.

• Data Hub (High-availability component unavailable)
• Cronjob service (High-availability component unavailable)
• Dynatrace (Possible loss of cluster monitoring data)

• Platform - ACC storefront (Delayed response time)
• Platform - Backoffice (Logged-in users are logged out. Unsaved changes are lost.)

Upgrading the Kubernetes cluster version ensures that all SAP Commerce Cloud clusters running on Kubernetes use the latest features and security updates.

You use VPN or VPN and NAT in your Commerce subscription.

In the Cloud Portal, you have the option to run a self-service upgrade before the deadline. After the deadline, SAP runs the upgrade mechanism during a previously announced maintenance window. The upgrade will take about 30 minutes of VPN/NAT downtime during which all your VPN and NAT connections are dropped.

Loss of connection to the external network:

• Data Hub
• Platform - ACC Storefront, Backoffice, API, background processing, update

Upgrading the operating system of network virtual machines is necessary to ensure that they all have the latest security patches and functionality installed.

SAP Commerce Cloud as a whole remains operational during the migration, but certain components will be briefly affected. The migration takes about 10 minutes for one affected environment. SAP reserves a 2-hour-long maintenance window to account for possible delays.

SAP Note 3580151

• Cronjob service (High-availability component unavailable.)
• Data Hub (High-availability component unavailable.)
• Search - Solr
• Platform - ACC storefront (Delayed response time.)
• Platform - Backoffice (Logged-users are logged out. Unsaved changes are lost.)
• Platform API

Zone redundancy of Azure components provide an additional protection against outages and incidents. Azure Container Registry (ACR) created before Q1 2024 isn't zone redundant. SAP has a dedicated process to move all images in the old registries to new, zone-redundant ones so that SAP Commerce Cloud benefits from advantages of Azure availability zones.