Storage Snapshots of SAP HANA on Azure (Large Instances)

By Ashwin Venugopal -

 




The storage infrastructure in SAP HANA on Azure (Large Instances) supports storage snapshots of volumes while both backup as well as restoration of volumes is supported by the following considerations:

  • Instead of full database backup, storage volume snapshots are taken on a frequent basis.

  • Whenever a snapshot is triggered over /hana/data and /hana/shared, which includes /usr/sap, volumes, the snapshot technology initiates a SAP HANA snapshot before it runs the storage snapshot. You need an active HANA instance, for a HANA snapshot to be successful. A storage snapshot is not supported on the current secondary node where a HANA snapshot can't be performed, in an HSR scenario.

  • After the storage snapshot runs successfully, the SAP HANA snapshot is deleted.

  • Transaction log backups are taken frequently and stored in the /hana/logbackups volume that consists of the transaction log backups or in Azure and can be triggered to take a snapshot separately. 

  • If you want to restore a database to a certain point in time, for a production outage, you can easily request that Microsoft Azure Support or SAP HANA on Azure restore to certain storage snapshot. 

  • The SAP HANA snapshot that's included in the storage snapshot is an offset point for applying transaction log backups that ran and were stored after the storage snapshot was taken. 

  • These transaction log backups can restore the database back to a certain point in time. 

Storage Snapshot Considerations

Storage snapshot consumes the storage space allocated to the HANA Large Instance Units. The specific mechanics of storage snapshots for SAP HANA on Azure (Large Instances) includes:
  • A specific storage snapshot at the point in time when it's taken consumes little storage.
  • As data content changes and the content in SAP HANA data files change on the storage volume, the snapshot needs to store the original block content and the data changes. 
  • As a result, the storage snapshot increases in size. The longer the snapshot exists, the larger the storage snapshot becomes. 
  • As the more changes are made to the SAP HANA database volume over the lifetime of a storage snapshot, the space consumption of the storage snapshot will be larger.

SAP HANA on Azure Monitoring Considerations

You can easily monitor HANA Large Instances resources like CPU, memory, network bandwidth, and storage space using SAP HANA Studio, SAP HANA Cockpit, SAP Solution Manager as well as native Linux tools. Microsoft readily provides you with the resources to help you troubleshoot and monitor according to your organization's requirements, as well as the Microsoft support team to assist you in solving technical issues. 






Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more