Text Description automatically generated

Box 1: Ev3 series M Azure virtual machines

The Ev3 series pricing is starting from $58.40 /per month.

The E-series Azure VMs are optimized for heavy in-memory applications such as SAP HANA. These VMs are configured with high memory-to-core ratios, which makes them well-suited for memory-intensive enterprise applications, large relational database servers, in-memory analytics workloads etc.

The Ev3-series VMs range from 2 to 64 vCPUs and 16-432 GiB of RAM, respectively.

Example workloads include SAP HANA (e.g., E64s v3, E20ds v4, E32ds v4, E48ds v4, E64ds v4), SAP S/4 HANA application layer, SAP NetWeaver application layer, and more broadly memory-intensive enterprise applications, large relational database servers, data warehousing workloads, business intelligence applications, in-memory analytics workloads, and additional business-critical applications, including systems that process financial transactions of various nature...

Note: The M-series family of Azure virtual machines are memory optimized and are ideal for heavy in-memory workloads such as SAP HANA. The M-Series offer up to 4 TB of RAM on a single VM. In addition, these VMs offer a virtual CPU count of up to 128 vCPUs on a single VM to enable high performance parallel processing.

Example workloads include SAP HANA, SAP S/4 HANA, SQL Hekaton and other large in-memory business critical workloads requiring massive parallel compute power.

Box 2: Hana on Azure (Large Instances)

The storage used in HANA Large Instances has a file size limitation. The size limitation is 16 TB per file.

References:

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-hana-availability-one-region

In a Hybrid-IT scenario, Active Directory from on-premises can be extended to serve as the

authentication mechanism through an Azure deployed domain controller (as well as potentially using the integrated DNS).

It is important to distinguish between traditional Active Directory Servers and Microsoft Azure Active Directory that provides only a subset of the traditional on-premises AD offering. This subset include Identity and Access Management, but does not have the full AD schema or services that many 3rd party application take advantage of. While Azure Active Directory IS a requirement to establish authentication for the Azure virtual machines in use, and it can synchronize users with customers’ on-premises AD, the two are explicitly different and customers will likely continue to require full Active Directory servers deployed in Microsoft Azure.

References:

https://www.suse.com/media/guide/sap_hana_on_azure_101.pdf

The SAP Database Migration Option (DMO) with System Move option of SUM, used as part of the migration allows customer the options to perform the migration in a single step, from source system on-premises, or to the target system residing in Microsoft Azure, minimizing overall downtime.

References:

https://blogs.sap.com/2017/10/05/your-sap-on-azure-part-2-dmo-with-system-move/

YES

YES

NO

Scenario: Increase the performance of SAP ECC applications by moving to SAP HANA.

References:

https://azure.microsoft.com/en-us/pricing/details/virtual-machines/rhel- sap-hana/

https://help.sap.com/viewer/f2ad7797884249eeb2e91dc26a991196/3.0.3.0/en-US

Scenario: Upgrade and migrate SAP ECC to SAP Business Suite on HANA Enhancement Pack 8.

With the SAP LoadRunner application by Micro Focus, you can accelerate testing and development, reduce slowdowns and expenses, and gain a better understanding of performance issues. Validate software performance, virtualize your network, simulate workloads, benchmark production system performance, and optimize your deployment of SAP HANA software

References:

https://www.sap.com/products/loadrunner.html

Box 1: No

SAP HANA Replication consists of one primary node and at least one secondary node. Changes to the data on the primary node are replicated to the secondary node synchronously or asynchronously.

‎

Box 2: No

Since SPS11 SAP HANA system replication can be run in two different operation

modes:

delta_datashipping

logreplay

Box 3: Yes

Get-AzDisk & Primium_LRS

https://docs.microsoft.co m/en-us/powershell/module/az.compute/get-azvmimage?view=azps-4.6.1 https://docs. microsoft.com/en-us/powershell/module/az.compute/get-azdisk?view=azps-4.6.1

Box 1: Yes

Scenario: Technical requirements: Ensure that an application server can be restored from a backup created during the last five days within 15 minutes.

Instant Restore has 'The instance recovery snapshot(s) for 5 Day(s)'.

Box 2: No

Scenario: Ensure that all the production application servers can restore daily backups from the last 21 days.

The Retention of daily backup point is set to for 14 days only.

Box 3: Yes

ExpressRoute circuits are configured to allow you to burst up to two times the bandwidth limit you procured for no additional cost.

Scenario: It is estimated that during the migration, the bandwidth required between Azure and the New York office will be 1 Gbps. After the migration, a traffic burst of up to 3 Gbps will occur.

References:

https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs

AD connect, it's not mandatory to have AD FS, you can use Password HAsh Synch or Passthrough Authentication, but AD Connect is mandatory to synch you on-promises accounts to Azure AD

References:

https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/sap-hana-cloud-platform- identity-authentication-tutorial

Box 1: 4

Scenario: the Azure Resource Manager template that will be used to provision the production application servers.

Ensure that each production application server has four 1-TB data disks.

Box 2: Standard_LRS

Scenario: Minimize costs whenever possible.

Box 3: contoso.onmicrosoft.com

The network contains an on-premises Active Directory domain named ad.contoso.com.

The Initial domain: The default domain (onmicrosoft.com) in the Azure AD Tenant. For example, contoso.onmicrosoft.com.

References:

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/p lan-connect-userprincipalname