Be yourself; Everyone else is already taken.
— Oscar Wilde.
This is the first post on my new blog. I’m just getting this new blog going, so stay tuned for more. Subscribe below to get notified when I post new updates.
Be yourself; Everyone else is already taken.
— Oscar Wilde.
This is the first post on my new blog. I’m just getting this new blog going, so stay tuned for more. Subscribe below to get notified when I post new updates.
DB Replication Setup on Primary DB
Sample DMA and Setup_hadr files
DB Replication Setup on Secondary DB
Sample DMA and Setup_hadr files.
Copy/Download the PDF files to create the ‘.rs’ files in text editor.
The Azure Enhanced Monitoring Extension for SAP provides configuration information and performance data of the underlying Azure infrastructure and makes it available to the SAP application. It contains built-in self-diagnostics which enables identification of the health and completeness of the infrastructure data required by SAP services and support.
Having set up the Azure Enhanced Monitoring Extension for SAP, the Windows service AzureEnhancedMonitoring is installed inside the VM and collects all Azure-related data. Afterwards, this data is consumed by SAP Host Agent for further use in the SAP system transaction ST06.

$PSVersionTable.PSVersion
Major Minor Build Revision
—– —– —– ——–
5 1 17763 1007
Azure PowerShell works with PowerShell 5.1 or higher on Windows. To run Azure PowerShell in PowerShell 5.1 on Windows:
Install-Module -Name Az -AllowClobber -Scope AllUsers
$env = Get-AzEnvironment -Name AzureCloud
Connect-AzAccount -Environment $env


Set-AzContext -SubscriptionName <subscription name>

Set-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name>

Above screen shows status as OK for the AEM deployment.
Test-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name>

Perform the check by performing following step.

Health status and Diagnostics status are in OK state. Empty Counters are 0.

This completes the setup of Azure Enhanced Monitoring for SAP on Windows Operating System.
Microsoft has released a New version of AEM for SAP and its suitable for specific scenarios as mentioned below, otherwise its perfectly fine to use the version and steps mentioned above.
Prechecks :
Steps :
Following are the PowerShell commands to run to setup the AEM for SAP.
$env = Get-AzEnvironment -Name <name of the environment>
Connect-AzAccount -Environment $env Set-AzContext -SubscriptionName <subscription name>
Set-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name> -InstallNewExtension

Testing :
Test the AEM deployment by executing the PowerShell script.
Test-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name>

Readiness Check :

DB Replication Setup on Primary DB
Sample DMA and Setup_hadr files.
DB Replication Setup on Secondary DB
Sample DMA and Setup_hadr files.
During the high availability setup of SAP NetWeaver OR S/4 HANA system in Microsoft Azure Cloud, we need to deploy Standard Internal Load Balancer(ILB) to define virtual IP for the Linux Pacemaker Cluster SAP NetWeaver for ASCS OR DB VM nodes which are part of backend pool of Internal Load Balancer(ILB), outgoing internet connections may not be available for those Vms. This causes issues with Azure Fencing agent, SMT server ( for patch update), backup to blob etc.
As a workaround we can setup proxy server in SAP application server VM and direct ASCS and DB cluster nodes to connect to proxy for outbound internet connection.
Steps to follow
1. Install squid proxy server in a application server.
>>zypper in squid
>>systemctl start squid
>>systemctl enable squid
>>vi /etc/squid/squid.conf and add entry to allow the vnet to be connected this proxy.
acl localnet src xx.xx.xx.xx/yy
>>systemctl restart squid
2. In the ASCS Cluster node


Select Enable Proxy.
In HTTP Proxy URL, enter IP address of app server which is running squid proxy and “:3128” (or the http port defined in the file squid.conf in the proxy server.
Select ‘Use the Same Proxy for all Protocols”
3. Test from ASCS Node if outbound connection is working by running
>>curl google.com
>>sudo zypper update
References
https://www.linuxhelp.com/how-to-install-and-configure-squid-proxy-server-on-opensuse-leap-42-1
Anjan Banerjee – Sr. Customer Engineer
Anjan’s area of focus includes SAP on Azure in which he is helping customers in designing SAP solutions with high availability, disaster recovery, performance optimization, Backup & Archive, DevTest scenarios and its smooth deployment on Azure.
Anjan’s IT career spans 20 years, in which he has worked in various industries such as Manufacturing, Finance, Telecom, and Pharma where he has specialized in large enterprises designing & supporting mission critical systems. He has deep experience in SAP project management, technical architecture design, SAP Implementation, Upgrade and Unicode conversion, SAP Migrations, SAP HANA & Oracle database management and infrastructure management in SAP. He specializes in Virtualization technologies, high availability, clustering and disaster recovery scenarios.