Pass Your Microsoft Azure SAP AZ-120 Exam Easy!

Microsoft AZ-120 Planning and Administering Microsoft Azure for SAP Workloads exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Microsoft AZ-120 Planning and Administering Microsoft Azure for SAP Workloads exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Microsoft Azure SAP AZ-120 certification exam dumps & Microsoft Azure SAP AZ-120 practice test questions in vce format.

Azure IaaS for SAP

15. Business Continuity

After you get your service up and running, you need to ensure that you have business continuity capabilities in place in order to manage the service SLA. Let's see how you can achieve this. There are two important services. Azure Backup allows you to take a full VM snapshot, or you can restore files and folders by installing a backup agent called the Mars Agent. Many services now have the ability to backup directly to Azure backup via VM extensions such as SQL Server extension or SAP Hana database extension, which would take consistent application backup of data. Azure backup delivers many benefits, such as on-premise backup shipping. You can upload your backup to the cloud rather than shipping tapes to a secondary location. All of this occurs without requiring any complex infrastructure. Onpremise scale. Azure backup uses the power of Azure's Unlimited. Cloud scale. The system is highly available, and it does not require any maintenance from the customer. Data Security Azure Backup storage is encrypted by default and provides high availability with three regional copies at a minimum. You can also monitor all of your backups from a central glass of glass.Long- and short-term backup retentions are available. The other service that can build and strengthen your disaster recovery posture is Azure Site Recovery. ASR We touched on ASR BR briefly when we covered HLI in this section. ASR is a storage replication technology. It replicates changes, so it is a differential replication at the block level. For Azure, this type of replication is handy. An agent gets installed on the hypervisor that watches for changes on the VMDK or VHD files and replicates those changes in a timely manner. It is not a synchronous replication. You can set replication according to your RTO and RPL. ASR requires the installation of a processing server on premise to collate those replications and push them to Azure. All replication happens over encrypted channels (HTTPS), and they originate from the processing server rather than Azure, so you won't need to open any unnecessary ports on your firewall. As you replicate your VMs—or, shall I say, storage—to Azure, you get to create a recovery plan. This recovery plan will dictate how your failover will start. For example, if your service has three tiers (web, application, and database), you would start your database server first, followed by your application servers, and finally your web servers. This would ensure consistency and reliability as you bring the system up gradually and ensure everything is working appropriately. Speaking of which, you can run manual and automatic scripts for each stage of the failover process. For example, you can put in a manual task to check for services that have started by logging into the server and checking things manually. When everything looks OK, you can finish that task to carry on the failover process. You can also automate your tasks by using automation accounts such as PowerShell or Bash scripts to perform actions on the resource.

16. Monitoring

We have now reached the final part of this section, Azure Monitoring. This is an important piece of the puzzle as it brings data and insights that allow you to make intelligent decisions around your infrastructure, such as scaling services, health alerts, health reports, etc. Azure Monitor is an Azure cloud-native tool for monitoring resources on any cloud or even on premise.You can plug in your Microsoft System Center Operations Manager to Azure Monitor and pipe your logs to Azure to have a central point of alerting and management. Azure Monitor relies on LoganAnalytics to store its data. As mentioned recently, Loganalytics is perfect for storing large data sets and performing complex data analytics on top to drive insights. Lots of services, such as Security Center and Azure Sentinel, in addition to VM diagnostics, use log analytics to store data and organise tables for analytical processing later, either directly using KQL language or through tools such as Azure Monitor. Azure Monitor has VM extensions that can be deployed to specific VM types Linux or Windows to pull performance data from the operating system like Windows event logs, performance counters, SSLog log files, etc. specifically for SAP. There is a monitoring extension called Azure. enhanced monitoring extension for SAP. This extension consumes the diagnostic data collected by the diagnostic extensions and transfers it to an aggregated data set appropriate for the SAP host control process to consume. Both of these extensions are mandatory for VMs running SAP workloads.

17. Demo: Clustering on Azure VMs @ SUSE Linux: Creating Resources

It's now time for our first hands-on demonstration. I appreciate that this section was quite long on the theoretical part, and I'm excited to show you some practical concepts. So let's get started. We will look at the scenario where we arein preparation for deployment of SAP Hana on Azure. This demo will explore the process of implementing clustering on Azure VMs running the SUC distribution of Linux. after completing this demo. You will be able to achieve the following provision of Azure compute resources necessary to support highly available SAP Hana deployments During the first part of the demo, configure the operating system of Azure VMs running Linux to support the highly available SAP Hana installation and provision the Azure Network resources required to support the highly available SAP Hana deployment. We will deploy Azure infrastructure components necessary to configure Linux clustering. This will involve creating a pair of Azure VMs running Linux SuSE in the same availability set. So, from your computer, use a browser and navigate to the Azure Portal. If prompted, login to the Azure Portal using your Azure account that has owner or admin rights in the Azure Portal. Use the search field in all services to filter for Proximity Placement Group. Just type proximity click on "Proximity placement group" and then click on "create proximity placement group." This will create the proximity placement group. Tile. Please make sure that you select your correct subscription. Select or create a new resource group if you don't have one. So I will create a new one and click Okay. Select the correct region for your deployment (West Europe in our case) and then give the proximity placement group a name according to your naming convention. Click on "Review and Create." And click on Create. It will take a few seconds for it to create the resource. And there you go, all created. Now click on the resource group name, which will take you to the resource group, and click on Add. We are now going to create the virtual machine. So under compute, click on "virtual machine." Make sure the correct subscription and resource group are pre selected.Type your virtual machine name while remembering to follow your naming convention. Choose your region and availability. You have Availability Sets, which we will go for. Create a new availability set. Go with the defaults. And for the image, we will stick with SuSE Enterprise Linux for SAP 15 SP 2. I am going to change the size and select the VM that can take up to eight data disks. So I will go for Standard D for S. Set the admin username and password and make sure that your password is unique and at least eight characters long. Now click on "disks." Make sure the OS is a premium SSD We aren't going to create data discs yet. We just need to make sure we are using managed discs at this point. Please proceed to networking now. We will create a new network. We don't have one yet. So let's create a VNET. Let's change the IP address range, and I will go with 192 address range 20. I will create the first subnet. Use 192 as the subnet mask. Click OK. The default settings will create a public IP for DVM with energy attached to it, which is a feature of the Nick we talked about previously. Now click on Management. I will go with the defaults here. Now under Advanced, please make sure that you scroll down to Proximity Placement Group and select the proximity group that you have created with regards to tags. You can add your tags here. Click on Review and Create, and when validation has passed, just click on Create. This will start the process to create the VM. The deployment process will walk you through each step, from creating the VNet to creating the virtual machine and all resources in between. It might take a few minutes, depending on resources and regional service status. We'll give it a bit of time and come back to check on progress. Now the virtual machine has been created, so if we go to the resource group, we can see the virtual machine and all of its resources. We will be following the same steps to add the second virtual machine. Go to Compute Virtual Machine, follow the same steps to create the virtual machine, give it a new name, make sure it's in the same region, select the availability we created earlier, and make sure the same image and skew size are selected. Fill out the username and password details, and before going to review, just go back to double check. All configuration discs are the same, so there is no need to make any changes. For networking, please make sure it's in the same subnet. Under management, we will stick with the defaults, and for advanced settings, please make sure the Proximity Placement Group is selected. Click on "Create" and review again. It will take a few seconds to validate, and then click on Create. The process will take a few minutes, but it might be a bit shorter than last time as we have fewer resources to create, and as soon as it's done, all resources will appear here. Next, I have opened the Azure CLI, and we will create old discs to attach to each of the VMs. The first step is to select the subscription we are working on. I am setting the Resource Group variable name, which is the resource group name we created earlier. Setting the location via a variable, either by hardcoding the location name or by querying the previously created resource group, We are saying "Resource Group List query ResourceGroup variable Location," which gives us the location of that resource group, and just make sure that the output is in TSV format. In order to create all eight disks, we are going through a for loop from zero to seven. Run through and do azdisc create research group. Type the research group name that we have set at the beginning, then the name for the disks, which should follow your naming convention In our scenario, it will fix a value of data disc from zero to seven at the end of the VM name and give it a size in gigabytes, so we are setting it to128 Set the ski of the disc to premium LRS, and that's what we need for our SAP system, and it's done. This will create all eight discs inside the same resource group. By the way, this will only create disks. You can add another loop to cycle through all discs and attach them to the VM, but I will demonstrate that from the portal, so I will wait for that to finish and then create the second set of discs for the second VM. If you press the up arrow button and change VM zero to VM one, this will go through the cycle again to create the second set of disks. All discs are now created so you may close theAzure CLI window and navigate to each of the VMand click on the discs option and attach each ofthe discs I'm going through each disk. Attaching them in sequence for VM zero, and as previously mentioned, you can write a batch command to automate disc attachment, so you don't have to do it through the GUI. When you're finished attaching them to the portal, click save that configuration and wait a few seconds. Now, please go to the second VM and attach each of the discs like we have done for the first VM after creation. We just need to make sure everything is mapped. The next demo will take you through configuring these discs and the operating system for a highly available SAP HANA installation. We have now concluded this hands-on demonstration.

18. Demo: Clustering on Azure VMs @ SUSE Linux: OS and Storage Configuration

Welcome back to another hands-on demonstration. This second hands-on exercise will focus on configuring the operating system and storage on Azure VMs running Susie Linux Enterprise server in order to accommodate the clustered installation of SAP Hana. In this second demo, we will configure the operating system and map all physical discs to the right directories. We will also create a passwordless login approach to our VM, which means we will be able to log in from VM zero to VM one using SSH keys stored on each of the machines without prompting for a password, and of course vice versa now that we have provisioned our resources and disks. We will configure both of the VMs and map all the disks, and then mount them inside the OS and make sure that they are highly available for SAP Hana installation. So I've just logged into the portal and brought up BASH by clicking this icon, and I've now just maximised it so you can see the full screen. So first things first, we need to make sure that if you have multiple subscriptions under your tenant account, you pick the right one. I've got this in memory, which is basically an ISET accountset subscription to Visual Studio Enterprise, which is my subscription that I use for this demo, and then I'm going to set the resource group name to the resource group that I've created for this demo, and then I'm going to pick the first IP from AZ network's public IPshow resource group name, and I'm querying the first public IP, which is for AZ 12001 a VM zero IP. Then I'm querying the IP address property, and I will output it in TSP. So what we'll do next is do SSH student, which is the username that we use to set up these VMs, and set the public IP to OK. Yes, and now we enter the passwords that we set for this VM. We're stuck in VM Zero, so the first thing we'll do is elevate our permissions. So let's do sudo su If this prompts you for a password, then you have to enter your admin password. again, then issue the command XSS CSI. This will display the discs that are assigned to this VM. Start by running PV create, in order to monitor the physical disks, we are going to create the volumes for six out of the eight disks, so we are going to start by running PvCreate devSDC, then SDD, then SDE, then SDF, SDG, and SDH. Next we will start to create volume groups VG creates VG Hana data for devSDC and SDD. We're going to create a Hana log using devSDC and SDF, and then the group for backup under dev. SDG and SDH The next thing we will do is create the logical volumes logical volume creates a minor cell. 100% free name Hana Data Volume Group Hana Data will do the same thing for Hana Log. So VG Hana log, and the same thing for backup. Backup. The logical volumes have now been created. We are creating a single logical volume for each volume group. So now in the cloud shell, what we're going to do is format the logical volumes using mkfsxfsdef VG Hanade Hanadata using the same commands. I will do the same for the other ones for logs and backups. After the logical volumes have been formatted, we are going to add partitions using the two discs that we have left over, the SDI and SDJ. We are going to partition those discs by running fdisk dev SDI. Using the fdisk tool, we press N to create a new disk. We type p for primary, and then we're going to enter one for one single partition. Press Enter three times to accept the default values, and press W at the end to write the partition table. What we've just accomplished here is that we've partitioned disc SDI. Now we're going to follow the exact same steps to partition the SDJ logical volume as well. So we're going to run "fdisk dev SDJ." So that's going to be a new disc as a primary partition, and enter three times to accept the defaults. Then type W to write the partition table. Next step is to format both drives using MKFS, XFS, FDI, and then SDJ. Now that we have finished formatting these two logical drives, we're going to create a directory that will serve the mount points. So let's start by issuing a make directory-Hana Data command, then Hana log, then Hana backup, next Hana shared, and finally UsrSAP. We will next need to display logical volume IDs by running bldkid. This will give all the logical IDs for each of the physical disks. So you identify the UID values associated with the newly created volume groups and partitions, including the devsdi to be used for Hana shared and the dev SDG to be used for USRSAP. Now, using the list that we got from blkid, before we enter anything in the FS tab, we need to format what we need to enter in the FS tab. So what we'll do here is use UUID to compensate for the values shown here. We need the UID here to paste them into that string and then get those values pasted into the FS tab as a whole. So we need to construct it first. Essentially, what I'm going to dois the first one is Hana. So, let's say Hana data. If you look for Hana Data's UID, copy that to replace that string. The next one is Hana log.Now. Hana backup. Hana shared for SDI. So if we look for SDI, which is there, that's going to be the one that was shared, and the last one is SDJ. Now that we have the format that we needed, the first thing we're going to do is go into vim and we'll just insert it. Let's go to the end of the file and paste it there. So I'm going to copy the list we constructed earlier and paste it at the end of the fSUP file. We're going to write the file and quit. Now that we have written everything, we can go back to the file just to make sure it's saved correctly. The next step is to install them in shell mount A. And if we do the F-minus-H, you can see all the volumes were mounted. We're not finished with VM Zero; you just need to repeat the process for VM One to map all the volumes and the discs as we've gone through the exercise. For VM zero, you just need to do the same steps as for VM one and make sure that you can see them as shown in this demo. We've now concluded this demo.

19. Demo: Clustering on Azure VMs @ SUSE Linux: OS and Storage Configuration cont'd.

Welcome back to another demo. This is actually the second part of the previous demo. We are now in a position where we have mounted all the volumes, created all the disks, and formatted them. And your independent task from the previous part of the demo was to do the same steps on the second VM as well. This second part of the demo will look at creating a passwordless SSH session. So that's exactly what we're going to do now. Enable cross-node, passwordless SSH access. I've opened up two browsers and logged into each of the VMs that we created as part of the previous part of the demo. The next thing is to run through a set of steps to create the SSH keys and exchange them. This will enable us to log in to each of the VMs without requiring any passwords. We are now on VM Zero, and the first thing to do is to run SSH key gentvsa. And then we save the output to the default file, and we just accept the location. We will not place a password on the actual file. So let's just hit Enter twice. Let's have a look at the contents of the file. Catroutes shidsa pop. This will display the public key. Let's copy it to Notepad or somewhere else where you can easily access it later. Right, so the next part is to login to VM 1 and enter this key. We are now on VM 1. as you may notice. The first thing to do is to run Makedirectory routeSSH, which shows that the folder already exists. And the next thing to do is create SSH-authorized Authorized Keys.So we just created this new file, and in the editor we're going to paste the key that we got from VM 0. Let's save it. And now what we'll do is generate the passphrase-less SSH key in VM one. It's exactly the same procedure as we did for VM zero. So SSH key generation accepts all default values. Now let's open the file and read the key. Copy that key and transfer it to VM zero. Again, I'm copying it to Notepad or somewhere similar. Let's switch back to VM Zero now. Okay, so we're back on VM Zero, where we need to do it again Paste the key we just got from VM one into SSH Authorized Keys. Of course, please ensure that you are pasting in the correct key. And with that, we save the changes and we quit. The next step is to generate the passphrase licence key. We now run cutroots using SSH keygen without TRSA. Pop. Sorry about the typo again. We copy the RSA key for VM zero. We pasted it into Notepad. We go back to VM One. Let's just clear the window a bit. Let's open the Authorized Keys file, VI into Authorized Keys, and enter the RSA key onto a new line. Okay, so we've done that. Now we need to save and quit. And while we are on VM 1, we will run the same command: SSH key GenTri. However, cataroos sshidrsa pop. We'll copy it again to Notepad so that we can paste it onto VM zero. We are switching back to VM Zero. Now we are opening the authorised key file and pasting the VM-one RSA key in there. And we can now save and quit. Okay, we now have to open the V-I-E-T-C SSH daemon. inside this file. There are two things which we need tomake sure that they are looking okay. The first one is called Permit route login, and it should be set to yes. and it is. The next step is to check the authorised key file to ensure that it is pointing to authorised keys and that everything is in order. So we can just quit. We'll now need to do a system control restart for the SSH daw so it can take in the new Sshconvig file. Let's do so using "systemctl restart SSHD." And we, of course, need to repeat the same process on VM one. So we're going back to VM One. Now we're opening the file again via TC SSHD configuration. We're making sure that the two entries are correct. Set Permit root login to yes and authorised files to the correct config file once more. It's all looking great. so we can once again quit. And again, we need to do a system control restart. This is HD. Excellent. So it's all done. What we can do now is that we can SSH to VM 1 or VM 2. We do so by just running SSH root AZ VM 0, and you just need to say yes to the prompt. and that's all that's needed. No passwords. The prompts did not ask for passwords. and we are logged in as root. Let's exit and exit again so thatwe may verify the other way around. Let's go to VM zero and verify the same by logging into VM one. As root. We're back here on VM Zero. So let's try to SSH route AZ-12, and we're in. As root. We've now completed configuring the operating system with all the loans. And on top of that, we can log into the two VMs using sh keys. This concludes this demo.

Go to testing centre with ease on our mind when you use Microsoft Azure SAP AZ-120 vce exam dumps, practice test questions and answers. Microsoft AZ-120 Planning and Administering Microsoft Azure for SAP Workloads certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Microsoft Azure SAP AZ-120 exam dumps & practice test questions and answers vce from ExamCollection.