Disaster Recovery (part 1 of 4)

By Ashwin Venugopal -

 



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



Azure Site Recovery

Replicate VMs

You must follow the guidance in replicate a Virtual Machine to Azure to easily replicate Azure VMs to the Azure region serving as the disaster recovery site, which is available at https://docs/microsoft/com/en-us/azure/site-recovery/azure-to-azure-walkthrough-enable-replication

  • To protect Active Directory and DNS, you can refer to Protect Active Directory and DNS document available at https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-active-directory
  • To protect database tier running on SQL server, you can refer to Protect SQL Server document available at https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-active-directory

Configure Networking

If you are using a static IP address, you can easily specify the IP address that you want the VM to take as a part of its Azure Site Recovery settings.

Create a recovery plan

It supports the easy sequencing of various tiers in a multi-tier application during a failover and while creating the plan, you have to complete the steps mentioned in Create a recovery planby using Site Recovery available at https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-create-recovery-plans

Add VMs to failover groups

Generate a recovery plan with the help of an application server, web dispatcher, and SAP Central Services VMs.

Add scripts to the recovery plan

For correct functioning of your applications, you may have to perform some operations on the Azure VMs after the failover or during a test failover and by automating some post-failover operations, the most commonly used Azure Site Recovery Scripts can be deployed into an Automation account. Similarly, you can also add a post action script to attach a load balancer on the failed over Azure VMs.

Run a test failover

  1. In the Azure portal, select your Recovery Services vault.
  2. Select the recovery plan that you created for SAP applications.
  3. Select Test Failover.
  4. To start the test failover process, select the recovery point and the Azure virtual network.
  5. When the secondary environment is up, perform validations.
  6. When validations are complete, to clean the failover environment, select Cleanup test failover.

Run a failover

  1. In the Azure portal, select your Recovery Services vault.
  2. Select the recovery plan that you created for SAP applications.
  3. Select Failover.
  4. To start the failover process, select the recovery point.





To read part 2, please click here
To read part 3, please click here
To read part 4, 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