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

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 groups of computers, re
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 of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more