Disaster Recovery (part 2 of 4)

By Ashwin Venugopal -

 




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




Setup Disaster Recovery for a Multi-tier SAP NetWeaver app deployment (in Azure)

The following steps can help in setting up of the disaster recovery easily:
  1. Replicate VMs
  2. Replicate a domain controller
  3. Replicate data base tier
  4. Perform a test failover
  5. Perform a failover

You have to follow the steps given below to achieve the same-

Create a Recovery Services Vault- You can create the vault in any region except for the source region:

  1. Sign in to the Azure portal > Recovery Services.
  2. Click Create a resource > Management Tools > Backup and Site Recovery.
  3. In Name, specify a friendly name to recognize a vault and if you have more than one subscription you have to select accordingly.
  4. Create a resource group or select an existing one. Specify the Azure region.

Verify target resource settings- 

  1. Verify that your Azure subscription lets you create VMs in the target region and contact support to enable the required quota.
  2. Determine that your subscription have enough resources to support VM sizes that can match your source VMs. Site Recovery can automatically select the same size, or the closest possible size, for the target VM.  

Set up outbound network connectivity for VMs- You have to allow outbound network connectivity from the VMs that you want to replicate for the Site Recovery to work properly. For URL-based firewall proxy controlling outbound connectivity, you have to allow access to these URLs.

Note- Site Recovery doesn't support the use of an authentication proxy to control network connectivity.

Enable replication for a VM

Select a source

  1. In Recovery Services vaults, click the vault name > +Replicate.
  2. In Source, select Azure.
  3. In Source location, select the source Azure region where your VMs are currently running.
  4. Select the Source subscription where the VMs are running.
  5. Select the Source resource group, and click OK to save the settings. 

Configure Replication settings- Site Recovery can create default settings and replication policy for the target region while allowing to change the settings as required:

  1. Click Settings to vie the target and replication settings.
  2. To override default target settings, click Customize next to Resource group, Network, Storage, and Availability.
  3. Customize the target settings.
  4. Customize Replication policy settings by clicking Customize next to Replication policy, and modify the setting as required.
  5. In Customize, choose Yes for multi-VM consistency to add VMs to a new or existing replication group and then click OK.   

Track replication status

  1. In settings, click Refresh to get the latest status.
  • Track progress and status as follows:
  • Track progress of the Enable protection job in Settings > Jobs > Site Recovery Jobs.

      2. In Settings > Replicated Items, you can easily view the status of VMs and the initial replication              progress. Click VM to drill down into its settings.





To read part 1, 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...
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