Azure VM Backup Considerations (part 1)

By Ashwin Venugopal -

 


To read part 2 please click here


Application Backup

SAP applications hosted by VMs can be easily backed up using Azure backup whose agents supports throttling utilized during backups and restores. Azure backup completes a  backup by using following ways for Azure VMs:
  • Azure backup always start the backup job according to the backup schedule you specify for the Azure VMs selected for backups.
  • A backup extension is installed on the VM if the VM is running during the first backup.
  • After the backup takes the snapshot, it transfers the data to the vault.
  • When the data transfer is complete, the snapshot is removed, and a recovery point is created. 

Database Backup

Azure VM-based DBMS' backup can be performed by using DBMS-specific methods which should also facilitate the ability to restore it to any point in time. To achieve this capability two types of backups must be performed:
  1. Database full & differential backups
  2. Transaction log backups

Besides the full database backups performed at the database level, you can also perform backups with storage snapshots. While storage snapshots can accelerate the recovery by quickly providing a roll-forward image of the database, the transaction log backups too remain important to restore the database to a certain point in time or to empty the logs from already committed transactions.

File-snapshot backups are very useful for SAP administrative tasks, like applying SAP support packs. But, the best practice to backup your SAP applications before applying any kind of support packs and upgrades or performing any other major data operations such as archiving.

SAP HANA Backup

The following two methods can be used to backup SAP HANA on Azure VMs:
  1. HANA backup to the file system in an Azure Linux VM
  2. HANA backup based on storage snapshots using either the Azure storage blob snapshot feature manually or Azure VM level backup

The choice between these two methods is not provided by SAP , but pros and cons are offered so that anybody can determine which to use depending on the situation as well as available storage technology.

File system consistency is available while using the SAP HANA snapshot feature, and if there is only single virtual disk is involved. But, this topic becomes more challenging when a single file system spans multiple disks/volumes. 

If there is an XFS file system spanning four Azure virtual disks, the following steps provide a consistent snapshot that represents the HANA data area:

  • HANA snapshot prepare
  • Freeze the file system (for example. use xfs_freeze)
  • Create all necessary blob snapshots on Azure
  • Unfreeze the file system
  • Confirm the HANA snapshot

It is recommended to use the procedure above in all cases to be on the safe side, no matter wḥich file system.



To read part 2 please click here


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