If you have inactive environments you still want to keep, you can place them in hibernation. Later, if you want to reactivate the environments, you can re-awaken them.
For more information, see Hibernate Environments.
Maintenance and Operations
Objective
After completing this lesson, you will be able to identify Maintenance and Operational Updates
Environment Hibernation
Selective Data Backup
Data Backup and Restore now supports Selective Data Backup, enabling you to perform backups of Commerce Databases and Media Storages independently.
For more information, see Creating a Data Backup.
Consumption Credits
Upgrading and Downgrading Disaster Recovery Plan
Disaster Recovery now offers a self-service option of upgrading from Standard to Premium recovery plan, including scheduling the upgrade for selected eligible environments. You also have an option to downgrade from Premium to Standard.
For more information, see Change your Disaster Recovery Package
Review Environment Infrastructure
You can now inspect settings of your environments and services on a single page to have an overview of environment configuration, types of used databases, and properties of virtual machines.
For more information, see Infrastructure Review.
Importing/Exporting Environment Settings
From the Infrastructure page, you can export settings of your current services as a JSON file and import them to the Estimator instead of entering them manually. You can also export a configuration from the Estimator as a JSON file.
For more information, see Importing/Exporting Configuration Properties
Storage size support for Service Scaling
You can now inspect the database performance by viewing its usage in the Scaling Configuration page. You can also view the number of virtual machines used by the node pool.
For more information, see Scaling Service Resources.
Apache NAT Ingress Downscaling
SAP Commerce Cloud implements Apache NAT Ingress downscaling to reduce infrastructure resource usage when this service is not in use. This process allows saved resources to be allocated elsewhere while maintaining compliance with the Fair Use policy.
Impact
Your SAP Commerce Cloud applications will continue running normally during this maintenance window. A window of one hour per environment has been allocated to account for any unexpected delays.
To mitigate potential issues, please avoid starting new deployments during the maintenance window. Deployments can temporarily lock your environment, which may interfere with the downscaling process and cause it to time out.
This one-time maintenance event is expected to complete smoothly with no disruption to your running services.
Related Information
Why?
This downscaling initiative helps SAP Commerce Cloud use resources more efficiently by freeing up unused infrastructure capacity. By removing waste, downscaling lowers infrastructure costs, improves margins, and redirects those saved resources to services that you use more often.
Migration of DTU Databases to Azure SQL Hyperscale
To benefit from an advanced, scalable database designed for performance and constant, high throughput, you can now migrate from a DTU database to an Azure SQL Hyperscale database.
Prerequisites
You qualify for the database migration if your SAP Commerce Cloud runs on either of the following types of database:
DTU Standard tier
DTU Premium tier
Impact
SAP has designed the migration process to minimize the impact on your business operations. It involves:
- Creating an asynchronous data copy. SAP will transfer your data to the new Azure SQL Hyperscale database instance without any performance impact on your current operations. You can continue using your existing Azure SQL Database service.
- Performing a database connection switch. Once the data copy is ready and the target database is ready to process queries, all database connections will be switched to the new database. The switch can result in a brief service interruption where the database is unavailable for a short period of time. The interruption doesn't last longer than 30 seconds. The connection switch may take longer if long-running operations are active in the system.
To reduce the possibility of a longer database unavailability, you can:
- Determine a low activity period to use the dedicated scheduled update in the Cloud Portal.
- Avoid deploying applications when the update is running.
- Avoid running catalog loads and syncs, big data imports, cronjobs, and other data-intensive operations when the update is running.
Related Information
Why?
Azure SQL Hyperscale offers a scalable, high-performance, cloud-native database. Migration to it doesn't require any changes to your Commerce programming, connectivity, and query processing configuration. It doesn't affect any data backups you have.
Soft Deletion of Unused Builds
To optimize the utilization of resources and infrastructure, SAP occasionally identifies and marks for deletion unused and outdated Commerce builds.
Related Information
Impact
Enablement of a build limit doesn't impact your Commerce application in any way.
Why?
Builds that aren't deployed or attached to a snapshot image use resources that can be allocated to active applications. SAP runs a process that identifies such builds older than 6 months and marks them for deletion. Afterward, such builds are unavailable to you, but can still be recovered within 14 days. To recover them, contact SAP Commerce Cloud Support.
Cloud Extension Update
Updated Cloud Hot Folders
The code of the Cloud Hot Folder extensions has been updated. Install the cloudhotfolders-2211azuresdk12-SNAPSHOT-202501101831836 as described in 2817992.
Microsoft Azure Storage Client SDK 8.6.6 library has been removed from SAP Commerce Cloud in Q1 2025. It is replaced with selected Microsoft Azure Java Client 12.x libraries. The new libraries are now available so that you have additional time to adjust your custom code to the new libraries and update the Cloud Hot Folders extensions before SDK 8.6.6 is removed.