Azure IaaS for SAP

25. Demo: Clustering on Azure VMs @ Windows Server 2019: OS Configuration

Welcome back. We'll now configure the OS of Azure VMs running Windows Server 2019 in order to support the highly available SAP NetWeaver installation. Please note: before you start this task, ensure that the template deployment we needed to initiate in the previous demos has successfully completed. In the Azure Portal, navigate to the blade of the Virtual Network Ad VNet which was provisioned in the first part of this demo. Display the Ad VNet DNS server blade. Please note that the Virtual Network is configured with private IP addresses assigned to the domain controllers deployed in the first part of this demo as its DNS servers in the Azure Portal start aPowerShell session in Cloud Shell. In the Cloud Shell pane, run the following command to set the value of the variable Resource GroupName to the name of the Resource Group containing the pair of Windows Server 2019 VMs you provisioned in the previous part of the demo, so ResourceGroup name equals AZ 12001 b CLRG. In the Cloud Shell pane, run the following command to join the Windows Server 2019 Azure VMs you deployed in the second task of the previous day. The active directory domain location equals Get AzureRM Resource Group Name resource group name location: Next, let's set some settings to join the domain. The first one is the name of the domain, and the user to join the domain next restart option. After joining the domain and finally setting the options to three, we then set the password in clear text in a variable called protected setting string VM names contain theVM names and are self-explanatory. We'll now do this for each loop for VM name and VM name and we will issue a set azvm extension. The Resource Group name is the Resource Group name. JSON ad domain extensionname join domain Publisher microsoft compute type handlerversion 10 variable extension type The VM name is the VM namevariable, and the location is the location variable setting string is the variable for the setting string, and protected settingstring is the variable for the protected setting string. So let's run it and see what happens. Okay, we have an error. Let's fix it. We have to construct the protected setting string into a key value structure rather than provide it directly as a value. So let's run it again, and we just need to wait for the script to complete before proceeding to the next task. Everything looks good. We will now proceed to configure the storage of Azure VMs running Windows Server 2019 to support a highly available SAP Net Weaver installation. In the Azure Portal, navigate to the blade of the Virtual Machine VM Zero, which was provisioned in the previous parts of this demo. And from this VM zero blade, connect to the virtual machine guest OS by using Remote Desktop. To do so, let's download the RDP file and, when prompted to authenticate, provide the following credentials You can use the value shown on screen for both a username and a password. Inside RDP session to VM zero, inside Server Manager, navigate to the localserver view and turn off temporarily, ie., Enhanced security configuration and again within the RTP session to VM zero. Also in Server Manager, navigate to the File and StorageServices Servers Node, then to the Storage Pools view and verify that you see all the discs you attached to the Azure VM in the previous exercise. great. We can now see some of the results of our previous work. Now let's use the new Storage Pools Wizard to create a new storage pool with the following settings. name, information, and storage Pool physical To select the three discs with disc numbers corresponding to the first three LAN numbers, zero to two, and then set their allocation to automatic. The tip is to use the entry in the chassis column to identify the loan number next and then create the now Let's use the new Virtual DiskWizard to create a new virtual disc with the following settings data You don't need to worry about the next step storage layout,simple provisioning, fixed size, max size, and that's okay. That's all done now. And we'll now use the new Volume Wizard to create a new volume with the following settings: server and disc You can accept all the default values for size. You can also accept the default values for drive letter, file system refs allocation, unit size, default volume,label, data and back in the Storage Pools view. We now need to use the new Storage PoolsWizard to create a new storage pool with the following settings. Let's call it Log Storage Poolphysical Disks Select the last of four discs and set it to automatic allocation automatic.And we'll now use the new Virtual Disk Wizard to create a new virtual disc with the following settings: virtualdisk name log, virtual disc storage layout simple provisioning, fixedsize max size, and that's also done. Now, finally, we'll again use the new Volume Wizards to create a new volume with the following settings: The server and disc accept all default values for size. You can also accept the default values for drive letter,l, file system refs, allocation, unit size, and default volume label. That's all done too. Now, your individual task is to repeat the previous steps in the final part of this demo in order to configure storage on the other VM that is on VM one.

26. Demo: Clustering on Azure VMs @ Windows Server 2019: Failover Clustering Prep.

Welcome back to another part of this demo. We will now prepare for the configuration of failover clustering on Azure VMs running Windows Server 2019. In order to support a highly available SAP NetWeaver installation, let's proceed within the RTP session to VM zero. That was our first VM. We will start a PowerShell session. Let's run it as an admin and we will install failover clustering and remote administrative tool features on both VM zero and VM one by running the following. Please note we will do this from VMzero to install it on both VMs. Let's define the VMs in a variable. Now we can invoke the relevant command. invokecommand nodes. install Windows feature failover clustering, includeall sub-feature, and include management tools. So let's run it and wait for it to complete. The error you see on screen is because you logged in as a local user, which means that it cannot run on VM ten. You can see that it worked for VM 0 though. So what I'm going to do to solve this is log off and log in as administrator back to VM zero. So I'll run PowerShell again, but as admin this time. I will, of course, run the same command and expect that it will work on VM one. Let's run it and see if we get zero errors. We see that it worked for VM twelve. That's great. Next, we will install RSAT for both nodes too. So let's issue the relevant command: invoke command nodesinstall Windows feature RSAT includes a feature restart Please note that this will result in the restart of the guest OS of both Azure VMs. In scope, the command worked and it is rebooting. Now on your computer, Go back to the Azure Portal and we will create a storage account from the new blade. Initiate the creation of a new storage account with the following settings The title of your Azure subscription. The name of the resource group containing the pair of Windows Server 2019 data centre AzureVMs that he provisioned in the previous demo. Any unique name consisting of three to 24 letters and digits can be used for a part storage account. I will use my own naming convention again,but please do ensure to follow yours. Also, please ensure that special characters are used. Location: the same Azure region where you deploy the Azure VMs in the previous performance choice, Standard Redundancy as LRS. This is locally redundant storage. Next, onto the advanced tab. Please leave them all as default networking connectivity methods at public endpoints on all networks. Now on to data protection, where we will keep alloptions as default tags and then review and create andcreate. It's now in progress and it worked. The next task is to configure failover clustering on the VMs that we provisioned through the Azure Portal. Navigate to the blade of the VM zero which you provisioned in the first part of this demo and then ensure that you connect to VM zero within the RDP session to AZ 12001 Bclvm zero. After we installed the failover clustering in RSAT, we went to the Tools menu and server manager launch the Active Directory Administrative Center In Active Directory AdministrativeCenter, create a new organisational unit named Clusters at the root of the domain you created. In the Active Directory Administrative Center, we will now move the computer accounts of VMzero and VMone from the computer containers to the Clusters organisational unit. And now under Clusters, you should see two VMs. Start a Windows PowerShell session and create a brand new cluster by running the following commands We'll first declare the VMs in a node variable. And now let's declare the actual command. AZ 12001 Bclcl zero node nodes nostorage static address 100 one six new cluster name Let's run it. We have a typo. Let's fix the typo and try and run it again. Great, it now worked within the RDPsession to the first VM, switch to the Active Directory Administrative Center console. In the Active Directory administrative center Navigate to the Clusters organisational unit and display its properties window. In the Properties window, navigate to the Extensions section and display the Security tab. In the Security tab, click on the advanced button to open the Advanced Security Settings for Clusters window. On the permissions tab of the AdvancedSecurity Settings for Computers window, click Add. In the Permission Entry for Clusters window, click Select Principle. And then in the Select User Service Account or Groupdialog box, click Object Types and enable the checkbox next to the computer's entry, and then click OK. Back in the Select User Computer Service Account or Group dialogbox, in the Enter the object name to select, type the cluster name AZ 120 CLC zero and click OK. In the Permission entry for a Clusters window, ensure that Allow appears in the type dropdown list. Next, in the Applies to Dropdown list, ensure that you select this object and all descendant objects. In the Permissions list, select the CreateComputer object and delete the computerobjects checkboxes. We need to find them first. There are quite a few checkboxes. We'll then click OK. Twice within the Windows PowerShell session. Install the AZ PowerShell module by running the following install module name AZ force within the Windows PowerShell session now that it has finishedinstalling the AZ Tools. Authenticate by using your Azure AD credentials by running the following addAzet account when prompted. Sign in with the account that has the owner or contributor role in the Azure subscription you're using for this demonstration. Okay, it all works and we are all logged in. Now, within the same PowerShell session, set the cloud witness quorum of our new cluster by running the following commands. Let's first define the Resource Group name variable. Now we'll get the storage account name by running the following command, and now we can check that we have the correct value. Within the variable Next, let's fetch the storage account key by running a different command. There's an error here. We actually ran the wrong command. So let's do that again on the clean screen. And that word now? Which means that we can finally issue a command where we set the cloud witness quorum. Set the name of the cluster quorum cloud witness account. We reference the variable here. We reference another variable here. great. That works. We can now verify the resulting configuration within the RDP session to VM 0 from the Tools menu and Server Manager. Let's start. The failover cluster manager In the Failover Cluster Manager console, review the AZ12001 Bclcl zero cluster configuration, including its nodes, as well as its width and network settings. Please note that the cluster does not have any shared storage at the moment. You may now terminate the RDP session to VM 0. Let's summarise what we achieved in this hands-on. In the Azure Demonstration, we have configured the operating system of Azure VMs running Windows Server 2019 to support the highly available SAP NetWeaver installation.

27. Demo: Clustering on Azure VMs @ Windows Server 2019: Azure Network Provisioning

Welcome back to another demo. In this demo, we will provision the Azure network resources necessary to support highly available SAP NetWeaver deployments. We will implement Azure load balancers to accommodate clustering installations of SAP NetWeaver. So let's start by configuring Azure VMs to facilitate the load balancing setup. Since we will be setting up a pair of Azureload balancers of the standard SKU, we need to first remove the public IP addresses associated with the network adapters of the two Azure VMs that will be serving as the load balanced back end pool. So let's get started. From your browser in the Azure Portal, let's navigate to the blade of the Azure VM Zero. From the VM zero blade, navigate to the blade of the public IP address AZ 12001 Bclvm ZeroIP that is associated with its network adapter. Once again, from the VM zero blade, first disassociate the public IP address from the network interface and then set the assignment to Static. Let's give this a bit of time to complete. In the Azure Portal Let's now navigate to the blade of the Azure. VM.VM one. So for VM One, another way to do it is to navigate to the blade of the public IP address associated with its network adapter. From that IP blade, we can disassociate the public IP address. From the network interface in the Azure Portal, navigate to the blade of the VM One Azure VM and from the VM One blade, navigate to its networking blade. And then, from the networking blade, navigate to VM One's network interface, and from the blade of VM One's network interface, navigate to its IP configurations blade, and from there, display its IP Config One blade on the IP Config OneBlade, set the private IP address assignment to Static, and save the change. We can now create and configure the Azure load balancer to handle inbound traffic. So once again, in the Azure Portal internal resource group, click Create a resource. Let's look for a load balancer. From the new blade that appears, initiate the creation of a new Azure load balancer with the following settings The name of your Azuresubscription resource is subscription. Name the name of the resourcegroup containing the pair of Windows Server 2019 data centre Azure VMs you provisioned. In the first exercise of this lab, I will be using AZ 12001 B CLLB Zero. But please do remember to follow your own naming conventions. internal SKU standard virtual network in the same Azure region where you deployed Azure VMs in the first exercise of this demo Let's drop it into our VNet ad VNet, in this case, Subnet ClubNet, ensuring that it is the cluster subnetIP address Assignment static IP Address 100 1240 Availability Zonezone Redundant: We will now wait until the load balancer is provisioned and then we will navigate to its blade in the Azure Portal when it's all done. So, from the AZ 12001 BCLB zero blade, add an abackend pool with the following settings: I would once again use my own naming convention, so let's call thisAZ 12001 B-C-L LB zero backend pool virtual network advnet. We will use the nick and IPV four. Let's add the two VMs. Now next. From the same load balancer blade, add a health probe with the following settings. I'm using the mynaming convention The AZ 12001 BCLB zero H probe protocol will be TCP ports with a 5-9-9 interval and an unhealthy threshold of two consecutive failures from the same load balancer blade. Then add a network load balancing rule with the following settings. the name again using my ownnaming conventions The IP version will be IPV four. For the front end IP address, we're going to use the load balancer frontend address. Ha port should be disabled. TCP is the protocol, and the port number is 14334. The SQL back end port number is 1433. The backend pool is the one which was recently created. BCLB zero must also be specified as the pool health probe. Select none for session persistence. Idle timeout is 4 minutes. Floating IP should be enabled. Let's go ahead and create it. Our next task is to create and configure Azure load balancers to handle outbound traffic from the Azure portal. We will this time start a PowerShell session in the cloud shell, and before we proceed with issuing commands, we will first make sure to set the correct context subscription in the cloud shell pane. Let's start by running a command. This command will set the value of thevariable resource group name to the name of the resource group containing the pair of Windows Server 2019 data centre Azure VMs. In the first part of this demo, the resource group name equals Azet 12001 B CLRG, and again, in the same cloud shell pane, we will run the following command to create a public IP address to be used by the second load balancer. The first part of the command will get thelocation, so location equals getAZ resource group and thename is the resource group name variable location. Then we'll set the public IP name pip nameAZ 12001 B CLLB zero Pip and we will now actually create the public IP address. So let's run the relevant command new AZ public IPaddress resource group name resource group name pip name locationlocation skew is the standard allocation method is static and we'll now run the following commands to create a second loadbalancer. Let's first name it and we'll do so under the LB name variable, so LB name AZ 12001 Bcllbone Let's set a load balancer in front and name a variable. LBFE's name is Azet 12001 BCLLB. We'll now get the public IP pip getsAZ public IP address. resource group name and resource group name, and the name is the Pipname. We now need to create the front end IP configuration, which we will also do by running a command newAZ Load Balancer front End IP config Name lbfe Namepublic IP Address pip, and we also need to create the backend pool configuration again via the running of acommand be Pool Configuration Finally, EndAddress Pool Configuration Name LBE Pool Name We are now in a position where we can actually provision the load balancer again. We'll do so via a command, so let's run it. The variable group name is the variable group name, the variable location is the location, the variable name is the LB name, and the variable scheme is the standard back end address pool. Configuration of the Pool Finally, the front end IP configuration is FELP configuration that's now been created great.So let's close the cloud shell pane. We will now need to go back to the AzurePortal, refresh the page, and navigate to the blade displaying the properties of the Azure Load Balancer LB One in the LB One blade, click Backend Pools on the LBOne Backend pools blade, click ASETS 12001 b CL LBOne Pool, which is empty. So let's specify the following settings and click Save virtualNetwork will select our VNet ad VNet then Nick, then I PV Four and let's add the VMs and save on the LB One blade again. Let's click Health Probes from the new Health Probesblade. Let's add a health probe with the following settings name as usual, following my own naming convention. Unhealthy 5-second interval Thresholds: two consecutive failures, and let's do it again with the LB One blade. Now click Load Balancing Rules Let's add a networkload balancing rule with the following settings: I will again use my naming convention to name something appropriate IP Version IPV will accept the default value protocol TCP port 80back end port 80back end pool the one we recently created health Probe the one we recently created session persistence is none. Idle timeout in minutes is four. Floating IP is disabled, and that's all that's created. Now, let's take a moment to summarise what we achieved in this demo, as it was a bit longer than the others. As a summary at an overall level, you've learned how to create the cluster VMs, the disks, the load balancers, and the load balancing rules. You may now delete the resource groups as an individual task. Since the two cluster Azure VMs are no longer directly accessible from the Internet, you can deploy an Azure VM running Windows Server 2019 Data Center that will serve as a jump host.

ExamSnap's Microsoft AZ-120 Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, Microsoft AZ-120 Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.