Operating system planning and image management for SAP on Bare Metal Server in IBM Cloud VPC

This document provides guidance on operating system selection, planning, and image management strategies for SAP HANA® and SAP application server workloads running on IBM Cloud® Bare Metal Servers for Virtual Private Cloud for IBM Cloud® Virtual Private Cloud. Understanding the available operating systems, their support levels, and deployment options is essential for a successful SAP system implementation on bare metal infrastructure.

Overview

SAP HANA and SAP application server deployments on Bare Metal Servers for VPC require carefully selected operating systems that are certified for both the bare metal hardware and your specific SAP applications. The supported operating systems include:

Red Hat® Enterprise Linux® (RHEL)
SUSE Linux® Enterprise Server (SLES)
Microsoft Windows Server

Selecting the appropriate operating system depends on SAP solution requirements, existing infrastructure, in-house expertise, and preferred support model.

Key considerations for OS selection

When defining your operating system strategy for running SAP workloads on Bare Metal Servers for VPC, evaluate the following key factors:

SAP application compatibility: Verify that the selected operating system and version are certified for the SAP solution you plan to deploy (for example, SAP HANA, SAP application server, SAP S/4HANA, SAP BW/4HANA, SAP ASE, SAP IQ, or SAP MaxDB).
Application compatibility of other vendors: Verify that the selected operating system and version are certified for the third-party solution you plan to deploy (for example, IBM Db2, Microsoft SQL Server).
Hardware compatibility: Make sure that your selected bare metal server profile supports the required operating system, version, and technology levels.
Licensing model: Determine whether to use IBM-provided stock images with included licensing or bring your own license (BYOL) options based on your procurement and cost-management strategy.
Support lifecycle: Use operating system versions that align with SAP maintenance timelines to ensure long‑term support.
Performance requirements: Consider operating system-specific optimizations and tuning parameters required for your SAP workload on bare metal infrastructure.

Image deployment options

IBM Cloud VPC offers multiple options for deploying operating systems on bare metal servers:

Stock images: Preconfigured, ready-to-deploy operating system images maintained by IBM with integrated support and SAP certifications.
Custom images: Customer-created or modified images imported from IBM Cloud Object Storage, allowing for standardized configurations and specific customizations.

Supported operating systems

Bare Metal Servers for VPC supports multiple operating systems for SAP workloads. Verify that the operating system version you select is compatible with both your bare metal server profile and your SAP application requirements.

Minor versions or releases of the listed operating systems are still supported by SAP but no longer offered through IBM Cloud.

The following operating systems are available for SAP workloads on Bare Metal Servers for VPC:

Red Hat Enterprise Linux (RHEL): Version 8.6 or higher for SAP Applications
SUSE Linux Enterprise Server (SLES): Version 15 SP3 or higher for SAP Applications
Microsoft Windows Server: 2016, 2019, 2022, and 2025

For the most current list of supported operating system versions and their compatibility with specific SAP products, see:

Operating system deployment requirements:

Configure kernel parameters according to SAP guidelines and the recommendations for your selected operating system.
Install all required packages, libraries, and dependencies for the SAP applications being deployed.
Apply security hardening and compliance configurations as required by your organization.
Configure network settings, hostname resolution, and time synchronization.
For bare metal servers, ensure proper RAID configuration and disk management for optimal performance.

IBM-provided stock images

IBM provides preconfigured stock operating system images optimized for IBM Cloud VPC bare metal environments. These images are the recommended starting point for SAP HANA and SAP application server deployments on bare metal infrastructure.

Benefits of stock images

Preconfigured for cloud with cloud‑init integration for automated configuration.
Tested and validated for compatibility with IBM Cloud VPC bare metal infrastructure.
Maintained and updated by IBM with security patches and improvements.
Certified by SAP for SAP HANA and SAP application server workloads.
Support faster provisioning through predefined configurations.
Include SAP-recommended kernel parameters and system configurations for bare metal servers.

Stock image categories

OS images for SAP HANA systems:

Configured and certified for SAP HANA workloads on bare metal.
Include operating system configurations, kernel parameters, and optimizations for SAP HANA workloads.
Apply required OS settings according to SAP support notes.
Recommended for all SAP HANA production environments on bare metal.
Image names typically include "sap-hana" designation.

OS images for SAP application server systems:

Configured and certified for SAP application server deployments on bare metal.
Include required packages and configurations for SAP application server workloads.
Image names typically include "sap-applications" designation.
Support both Linux and Windows Server operating systems.

Generic operating system images:

General-purpose operating system images for non-SAP workloads.
Can be used for infrastructure components (proxies, jump servers, monitoring systems).
May require additional configuration and certification for SAP workloads.
Not recommended for SAP production environments.

Image selection guidelines

When selecting stock images for SAP workloads on Bare Metal Servers for VPC:

Identify SAP requirements: Use SAP-certified images (sap-hana or sap-applications) for SAP workloads.
Choose appropriate version: Select operating system version compatible with your bare metal server profile and SAP applications.
Determine licensing model: Decide between included licensing or BYOL based on your licensing strategy and existing subscriptions.
Plan for updates: Establish update and patching strategy aligned with SAP maintenance windows.
Verify SAP certification: Confirm the image is listed in SAP Product Availability Matrix (PAM) and SAP Note 2927211.

Image naming conventions

IBM stock images follow consistent naming patterns:

RHEL SAP HANA images: Include "rhel" followed by version and "sap-hana" (for example, ibm-redhat-9-6-amd64-sap-hana-4).
RHEL SAP Applications images: Include "rhel" followed by version and "sap-applications" (for example, ibm-redhat-9-6-amd64-sap-applications-4).
SLES SAP HANA images: Include "sles" followed by version and "sap-hana" (for example, ibm-sles-15-6-amd64-sap-hana-6).
SLES SAP Applications images: Include "sles" followed by version and "sap-applications" (for example, ibm-sles-15-6-amd64-sap-applications-6).
Windows Server images: Include "windows" followed by version (for example, ibm-windows-server-2025-full-standard-amd64-10).

Bring your own images

Custom image deployment allows organizations to use standardized, preconfigured operating system images tailored to their specific SAP requirements on bare metal infrastructure. This approach is valuable for maintaining consistency across environments and implementing organization-specific configurations.

Custom image use cases

When to use custom images:

Standardized operating system configurations across multiple SAP environments.
Specific security hardening or compliance requirements beyond standard images.
Migration from existing SAP environments with established image standards.
Custom kernel parameters or operating system tuning specific to your SAP workloads on bare metal.
Integration with enterprise configuration management tools.

When to use stock images:

Initial SAP deployments or proof-of-concept environments.
Standard SAP configurations without special requirements.
Environments requiring latest IBM-tested and SAP-certified configurations.
Simplified management and update processes.
Faster deployment timelines.

Custom image requirements

Technical prerequisites:

Images must be in supported formats for IBM Cloud VPC.
Cloud-init must be properly configured for IBM Cloud VPC integration.
Images must be compatible with target bare metal server profiles.
Operating system version must meet minimum requirements for SAP applications.
SAP-required kernel parameters and configurations must be included.
For bare metal, ensure proper disk and RAID configurations are documented.

Infrastructure prerequisites:

IBM Cloud Object Storage account and bucket.
Appropriate identity and access management (IAM) permissions for image import operations.
Network connectivity to Object Storage endpoints.

For detailed requirements, see Planning for custom images.

Custom image creation strategies

Capturing from existing SAP environments:

Capture running Bare Metal Servers for VPC instances using image from volume feature.
Remove SAP instance-specific data before creating reusable images.
Validate captured images in test environment before production use.

Building custom SAP images:

Start with IBM SAP-certified stock image as base.
Apply organization-specific configurations and hardening.
Install required monitoring agents, backup software, or management tools.
Configure cloud-init for IBM Cloud VPC integration and SAP-specific automation.
Document all customizations for maintenance and troubleshooting.
Test thoroughly with SAP applications before production use on bare metal.

Cloud-init configuration:

Install and configure cloud-init packages for your operating system.
Test cloud-init functionality during image validation.
Ensure proper integration with IBM Cloud VPC metadata service.

Custom image import process

Preparation steps:

Create IBM Cloud Object Storage bucket in appropriate region.
Upload operating system image file to Object Storage bucket.
Ensure proper IAM permissions for image import operations.

Import process:

Navigate to IBM Cloud VPC console.
Select Images from the navigation menu.
Click Create and select Import custom image.
Provide image details including name, resource group, and region.
Specify Object Storage bucket and image file location.
Select operating system and version.
Configure encryption settings if required.
Review and create the custom image.

Import considerations:

Large images may take significant time to import (plan accordingly).
Import operations are tracked as jobs in IBM Cloud VPC.
Imported images become available in image catalog after successful import.
For SAP images, ensure proper operating system selection during import.

For more information, see:

Bring your own license (BYOL)

When you have your own operating system license, you can install it on your bare metal server based on the vendor's instructions. The operating system chosen must be certified for SAP and have access to the necessary operating system packages for SAP.

BYOL use cases:

You have existing operating system licenses with support contracts.
You need to maintain license compliance across hybrid cloud environments.
You require specific operating system versions or configurations not available in stock images.
Cost optimization through existing volume licensing agreements.

Licensing considerations:

Valid operating system licenses for the number of bare metal servers.
Active support contracts with operating system vendors.
Compliance with vendor licensing terms for cloud deployments.

For more information, see Bring your own license.

Operating system update and patch management

Update strategies:

Establish regular patching schedules aligned with SAP maintenance windows.
Test updates in non-production environments before applying to production.
Maintain documentation of applied patches and updates.
Consider using automation tools for consistent patch deployment.

SAP-specific considerations:

Follow SAP guidelines for operating system updates.
Verify compatibility with SAP applications before applying updates.
Review SAP Notes for operating system-specific requirements.
Coordinate updates with SAP application maintenance.

Bare metal-specific considerations:

Plan for potential downtime during OS updates on bare metal servers.
Ensure RAID configurations remain intact after updates.
Verify hardware driver compatibility after OS updates.