Vertical & Horizontal Scaling

By Ashwin Venugopal -

 



Scaling Azure VMs

Compute

The VM can be scaled up or down by simply changing the VM size which may first require deallocating it. It only happens when a new size is not available on the hardware cluster that is hosting the VM currently which in turn also leads to the deallocation of  all the VMs in the availability set to resize them. After that you may also have to update the size of the other VMs in the availability set after the resizing of one VM.

The resizing can be done from the Azure portal, via PowerShell, Azure CLI, Azure Resource Manager templates, or programmatically (including REST API).

Storage

As the size of the virtual machine controls the number of data disks you can attach, you can detach a data disk without stopping the Azure VM by using PowerShell or Azure CLI after confirming that the particular disk is not being in use currently. You can also expand the attached Azure VM disks.

Scaling SAP HANA on Azure (Large Instances)

Compute

You can easily choose from many sizes of  servers that are categorized as Type I or Type II and tailored for different workloads, available for HANA Large Instances to scale up or down. You can select a size that can grow with your workload for the next three years.

A multi-host scale-out deployment is usually used for BW/4HANA deployments as a kind database partitioning startegy. The multiple hosts can be connected to a shared storage volume, allowing a quick takeover by standby hosts in case one of the compute worker nodes in HANA system fails,from an infrastructure standpoint.

The SAP Quick Sizer is available for greenfield scenarios to easily calculate the memory requirements of the implementation of the SAP  software on top of HANA which may increase with the data volume. you can use you current memory consumption as a basis to predict future consumption, and then plan your demand into one of the HANA Large Instances sizes.

Storage

Storage can be added by buying additional storage in 1-TB units which can also be added as an additional volume. You can't decrease the sizes of the volumes as originally deployed or change the names of the volumes or mount names as they are already attached to the HANA Large Instance units as NFS4 volumes.   




 





Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more