---
name: sap-powervs-infrastructure-1-overview
title: Deploying infrastructure for SAP workloads on Power Virtual Server
description: Learn how to plan and deploy the infrastructure components that are required to host SAP workloads on IBM® Power® Virtual Server.
last-updated: 2026-06-16
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/sap?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Deploying infrastructure for SAP workloads on Power Virtual Server
{: #powervs-infra-overview}

Learn how to plan and deploy the infrastructure components that are required to host SAP workloads on IBM® Power® Virtual Server.
{: shortdesc}

## Architecture overview
{: #architecture}

The recommended architecture for SAP on Power Virtual Server consists of two main infrastructure components:

IBM Cloud® Virtual Private Cloud (VPC) landing zone
:   Provides management services including a bastion host, proxy, Network Time Protocol (NTP), Domain Name System (DNS), and Network File System (NFS) services. This component is deployed in IBM Cloud VPC and serves as the entry point and management layer for your SAP landscape.

Power Virtual Server workspace
:   Hosts the SAP workloads, including SAP HANA databases and SAP NetWeaver application servers. This component provides the compute, storage, and network resources for your SAP systems.

![Architecture diagram showing VPC landing zone and Power Virtual Server infrastructure for SAP](../../images/powervs-deploy-arch-ibm-pvs-sap-s4hana-bw4hana.svg){: caption="Infrastructure architecture for SAP on Power Virtual Server" caption-side="bottom"}

The two components are connected through IBM Cloud® Transit Gateway, which enables secure communication between the VPC management services and the Power Virtual Server workloads.

## Deployment workflow
{: #deployment-workflow}

The deployment process consists of the following phases:

1. **Planning and prerequisites**: Review requirements, design the network layout, and prepare the necessary resources
2. **VPC infrastructure deployment**: Set up the VPC landing zone with management services
3. **Power Virtual Server infrastructure deployment**: Create the workspace, networks, and prepare for SAP instances
4. **SAP instance deployment**: Deploy and configure SAP HANA and SAP NetWeaver instances

## Prerequisites
{: #prereqs}

Before you begin the deployment, ensure that you meet the following prerequisites.

### Required permissions
{: #required-permissions}

You need sufficient IBM Cloud® Identity and Access Management (IAM) permissions to create and manage the following resources:

- Services from the IBM Cloud catalog
- IBM Cloud VPC services, virtual server instances, networks, network prefixes, storage volumes, SSH keys, and IBM Cloud® Security Groups
- Power® Virtual Server services, virtual server instances, networks, storage volumes, and SSH keys
- IBM Cloud® Direct Link and IBM Cloud Transit Gateway connections
- IBM Cloud Object Storage services and buckets

For more information about Cloud Identity and Access Management permissions, see [Managing IAM access for VPC Infrastructure Services](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started&format=markdown) and [Managing Power Virtual Server IAM access](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-managing-resources-and-users&format=markdown).

### SSH key preparation
{: #ssh-key-prep}

Create an SSH key pair that you can use to authenticate to all virtual server instances. This key is required to log in to both IBM Cloud VPC and Power Virtual Server instances.

For more information about creating SSH keys, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys&format=markdown).

### SAP software in IBM Cloud Object Storage
{: #sap-software-cos}

Upload your SAP software installation packages and SAP Maintenance Planner XML files to an Object Storage bucket. You need the following information to configure access from your virtual server instances:

- Object Storage endpoint URL
- Object Storage bucket name
- Object Storage HMAC access key
- Object Storage HMAC secret access key

For more information, see [Getting started with IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage&format=markdown) and [Service credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-service-credentials&format=markdown).

### Operating system selection
{: #os-selection}

Choose a Linux operating system for your deployments. For consistency and simplified operations management, use the same OS release for all hosts in your environment.

Supported operating systems for SAP workloads on Power® Virtual Server include:
- Red Hat Enterprise Linux (RHEL) 8.4 or later
- SUSE Linux Enterprise Server (SLES) 15 SP3 or later
- AIX (for SAP application server only)

For detailed information about supported operating systems, see [OS for Power Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-plan-os-powervs&format=markdown).

## Network planning
{: #network-planning}

Proper network planning is critical for a successful deployment. Design the network layout carefully to prevent IP address conflicts between all subnets in the landscape.

### Network design principles
{: #network-design}

All IP address ranges in your subnets must be unique and must not overlap.
{: important}

Consider the following items when you design the network:
- IP address ranges for VPC subnets
- IP address ranges for Power Virtual Server private networks
- IP address ranges in your on-premises environment, if you connect using Direct Link

### Example network layout
{: #network-example}

The following table shows an example network layout for a typical SAP deployment:

| Service                             | Network purpose                                                                   | Example IP address range |
| ----------------------------------- | --------------------------------------------------------------------------------- | ------------------------ |
| Edge VPC                            | Private network for VPN server                                                    | 10.30.10.0/24            |
| Edge VPC                            | Management network for Bastion virtual server instance                            | 10.30.20.0/24            |
| Edge VPC                            | Private network for Cloud Object Storage VPEs                                     | 10.30.30.0/24            |
| Edge VPC                            | Private network for Network services VSI. This subnet has public gateway enabled. | 10.30.40.0/24            |
| Power Virtual Server | SAP network                                                                       | 10.51.0.0/24             |
{: caption="Example private network IP address ranges" caption-side="bottom"}

Adjust these ranges based on your specific requirements and existing network infrastructure.

## Automation options
{: #automation-options}

IBM provides automated deployment solutions for SAP on Power Virtual Server:

Deployable Architecture
:   A complete infrastructure solution that is available in theIBM Cloud catalog. It automates deployment of the VPC landing zone and Power Virtual Server workspace by using Terraform and Ansible.

For more information, see [Power Virtual Server for SAP HANA](https://cloud.ibm.com/docs/sap-powervs?format=markdown).

## Next steps
{: #next-steps}

After you complete the planning and ensure that all prerequisites are met, proceed with the infrastructure deployment:

1. [Prepare IBM Cloud VPC infrastructure for SAP workloads](https://cloud.ibm.com/docs/sap?topic=sap-powervs-set-up-vpc-infrastructure&format=markdown): Deploy the VPC landing zone with management services
2. [Prepare Power Virtual Server workspaces for SAP workloads](https://cloud.ibm.com/docs/sap?topic=sap-powervs-set-up-power-infrastructure&format=markdown): Create and configure the Power Virtual Server workspace