Performing Backups & Restores (part 1 of 3)

By Ashwin Venugopal -

 



To read part 2 please click here
To read part 3 please click here



Backup & Restore of Azure VMs

If you want to backup Azure VM, then Azure Backup can easily install an extension on the VM agent running on the machine. To install the VM agent manually, you have to use the following OS-specific instructions:
  • Windowshttps://docs.microsoft.com/azure/virtual-machines/extensions/agent-windows
  • Linuxhttps://docs.microsoft.com/azure/virtual-machines/extensions/agent-linux
After the installation of the agent, Azure Backup will install the backup extension while enabling the backup which can also update and patch the extension without any user intervention. Azure VMs can be backed up with the help of following methods:
  • Single Azure VM- directly from the VM settings in the Azure portal.
  • Multiple Azure VMs- You can setup a Recovery Services Vault and configure backup for multiple Azure VMs. 

Application-consistent backup of Azure Linux VMs

Application consistency refers to the successful starting up of your applications when the VMs boot after being restored while performing the backup snapshots of your VMs. You can also use the Linux pre-script and post-script framework to perform application-consistent backups.

Pre-scripts can invoke native application APIs, which can quiesce the IOs, and flush-in memory contents to the disk ensuring the consistent snapshot application; whi;e post-scripts uses native applications APIs to thaw the IOs enabling the application to resume normal operations after the VM snapshot. 

Steps to configure pre-script & post-script

  • First of all, sign in as the root user to the Linux VM that you want to backup.

  • Now download VMSnapshotScriptPluginConfig.json from the GitHub at https://github.com/MicrosoftAzureBackup/VMSnapshotPluginConfig, and copy it to the /etc/azure directory of all VMs you want to backup and if the directory doesn't exist, then you have to create it.

  • Ensure the following permissions of these files- 

  1. VMSnapshotScriptPluginConfig.json: Permission "600"
  2. Pre-script file: Permission "700"
  3. Post-script Permission "700"

  • Now configure VMSnapshotScriptPluginConfig.json as follows: 

  1. pluginName- Leave this entry as it is, or your script might not work as expected.
  2. preScriptLocation- Provide the full path of pre-script on the VM that's going to be backed up.
  3. postScriptLocation- Provide the full path of the post-script on the VM that's going to be backed up.
  4. preScriptParams- Provide the optional parameters that needed to be passed to the pre-script.
  5. postScriptParams- Provide the optional parameters that needed top be passed to the post-script.
  6. preScriptNoOfRetries- Set the number of times the pre-script should be retried if there is any error before terminating where zero means only one and no retry if there is any failure.
  7. postScriptNoOfRetries- Set the number of tries the post-scripts should be retried if there is any error before terminating where zero means only one try and no retry if there is any failure.
  8. timeoutInSeconds- Specify individual timeouts for the pre-script and the post-script (maximum value can be 1800).
  9. continueBackupOnFailure- Set thei value to true if you want azure Backup to fall back to a file system consistent/crash consistent backup if pre-script or post-script fails. However, if you set it to the false, it fails the backup during script failure.
  10. fsFreezeEnabled- Specify whether Linux fsfreeze should be called while you are taking the VM snapshot to ensure file system consistency. It is recommended to set this setting to true unless your application have a dependency on disabling fsfreeze.

  • Now the script framework as well as the VM backup is already configured, the next backup can invoke the scripts and trigger application-consistent backup.




To read part 2 please click here
To read part 3 please click here




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