Power Virtual Server for SAP HANA - variation 'SAP ready PowerVS'
The SAP-ready PowerVS variation of the Power Virtual Server for SAP HANA creates a basic and expandable SAP system landscape. The variation builds on the foundation of the VPC landing zone and Power Virtual Server with VPC landing zone. PowerVS instances for SAP HANA, SAP NetWeaver, and optionally for shared SAP files are deployed and preconfigured for SAP installation.
Services such as DNS, NTP, and NFS running in VPC and provided by Power Virtual Server with VPC landing zone are leveraged.
The transit gateway provide the network bridge between the IBM Power infrastructure and the IBM Cloud® VPC and public internet.
The resulting SAP landscape leverages the services such as Activity Tracker, Cloud Object Storage, Key Management from the VPC landing zone and the network connectivity configuration provided by Power Virtual Server with VPC landing zone.
Architecture diagram
Design requirements
IBM Cloud Power Virtual Servers (PowerVS) is a public cloud offering that allows an enterprise to establish its own private IBM Power computing environment on shared public cloud infrastructure. Due to its scalability and resilience, PowerVS is the premium platform for SAP workloads in the cloud world. The reference architecture for 'Power Virtual Server for SAP HANA' - variation 'SAP ready PowerVS' is designed to provide PowerVS Linux instances prepared and configured for SAP HANA and SAP NetWeaver workloads according to the best practices and requirements using IBM Cloud® deployable architectures framework.
Components
PowerVS networks for SAP - architecture decisions
Requirement | Component | Choice | Alternative choice |
---|---|---|---|
|
SAP network | Create a separate SAP network for each SAP system. Tune SAP network in operating system according to SAP on Power best practices. | For very large SAP systems more than one SAP network may be needed. |
|
Backup network | Attach backup network that was created with the PowerVS workspace in 'Power infrastructure for deployable architecture' | For large landscapes with several SAP systems more than one backup network may be needed. |
Provide network for SAP system management | Management network | Attach management network that was created with the PowerVS workspace in 'Power infrastructure for deployable architecture' |
PowerVS instances for SAP - architecture decisions
Requirement | Component | Choice | Alternative choice |
---|---|---|---|
|
PowerVS instance |
|
Allow customer to specify additional parameters, like non-standard file system sizes |
|
PowerVS instance |
|
Allow customer to specify additional parameters, like non-standard file system sizes |
|
PowerVS instance | Host shared SAP system files on one of PowerVS instances for SAP NetWeaver and do not deploy a separate PowerVS instance |
|
Key and password management architecture decisions
Requirement | Component | Choice | Alternative choice |
---|---|---|---|
|
Public SSH key - provided by customer. Private SSH key - provided by customer. | Ask customer to specify the keys. Accept the input as secure parameter or as reference to the key stored in IBM Cloud Secure Storage Manager. Do not print SSH keys in any log files. Do not persist private SSH key. |
Compliance
This deployable architecture is certified for SAP deployments.
Next steps
Install the SAP system.