Most of the SAP solutions are supported on workflow. Now, that is a very broad statement. Going into details, you need to verify what are the supported databases, operating systems, for each of these solutions, and which instance types are certified for which workloads. You will learn about all of these details in this module. The information shared in this module is valid as of the recording of this video. In general, Google actively partners with SAP in getting all its latest infrastructure certified to run SAP workloads with SAP. The certifications and applications supported will be updated on an ongoing basis. Please check Google Cloud online documentation at cloud.google.com forward/SAP, as well as SAP OSS notes to view the most up-to-date information on all the SAP applications and VMs supported in Google Cloud. The most prevalent SAP Workload on Google Cloud is the classical SAP stack with a database server and one or more application servers. This configuration covers most of the SAP applications like ECC or BW. These installations have a database server, which can either be SAP HANA or other databases like IBM Db2, SAP ECC, SQL server and so on. Also, the most common operating systems like SUSE Linux Enterprise server, or SLES for short, Red Hat Enterprise Linux or RHEL and Microsoft Windows Server or supported. With respect to instance types, we will cover the memory optimized machine families for SAP HANA in detail a little bit later. For other databases and application servers the general purpose, which are the n1, n2, and n2D machine families, compute optimized machine families are certified by SAP. In general purpose machine families of n1 and n2, you can also customize virtual machines shapes to tailor, the VMs exactly to your application's needs and thus save costs. Other applications like SAP Business one for small enterprises, a new solutions like SAP hybrids that are not architected on the classical SAP stack, are also certified to run on Google Cloud. This table is shown here, shows the supported databases for each of these solutions, the supported operating systems, and the certified instance types on Google Cloud that can run these solutions. SAP Business One can run on SAP HANA for which there are dedicated SAP certified instance types on Google Cloud. For this configuration, SLES is supported operating system. Being a product that addresses SME market, SME Business One can also run on Microsoft SQL server, and this is supported on Google Cloud with any Compute Engine instance type that needs the SAP Business One hardware requirements. Similarly for SAP hybrid, installations with combinations of either SAP HANA that needs Linux or other databases are supported with instance types that satisfy a minimum hardware requirements for SAP hybrids. When it comes to architecting SAP deployments, there are six key areas that you have to look at. Let's start with sizing. First of all, you will look at the tiers of your deployment for your recipient system. In the lower environments like Sandbox and development, you will probably install a two-tier SAP system or a single VM for both database and application server. In case of a productive environment, you will look at a multiple VM installation with separation of database and application servers. Next, comes the instance types. You must choose the right size instance type for SAP workload and verify the certification of this instance type that you selected. I will walk you through the instance type certifications shortly. After that, come the image types. You must select a suitable operating system on your virtual machine. You can either choose Google pro ended OS images or choose to install custom images. Then comes storage. You must choose the right type and size for your primary and backup storages. This selection and sizing must enable your SAP workload with best performance, and best suited recovery times in case of backup. You will learn some important guidelines on this later in the module. In general, regarding deployment locations, guidelines on deployment locations depend on the physical location of customers and their requirements for global access to SAP installations. This varies considerably between customers. We won't go into a general guideline or much detail in this area. Lastly, network and security. You have already looked at network and security services in previous modules. We will not go into more detail in that area. But Google Cloud has all the tools that address the typical network architecture requirements of SAP deployments.
