7 hours 31 minutes
welcome back to is your stack sure is a heart attack. Gonna bust out some rhymes and spend some time with some lyrical lines. This is modulate 0.3, So let's go and see.
So in the tech industry, a technology stack, also called a solution stack or a data eco system is a list of all. The technology service is used to build and run one single application. There are server stacks, application stacks and network stacks. The bottom line is that for the purposes of this discussion that a stack or a suite of products
run well together and by adding each new technology to your stack, you have the power to do more things quicker and more efficiently.
So when an organization goes to a public cloud provider like Microsoft Azure, they can get there a bunch of different ways. But you rarely get to the cloud and just do one thing. You end up with several products that work together. You build your clown stack and you get amazing things done.
We have talked about V EMS and Dr Containers, and we've talked about blobs and storage and azure,
but we're gonna go a little bit deeper into the stack to see what we can get done to make our cloud platform better. And we're going to start with this networking component we call load balancers
with a load balancer like in Microsoft Azure. You can scale your applications and create a high availability type of service, as as your load balancer supports inbound and outbound scenarios and can scale up to millions of your applications transactions. A load balancer distributes new inbound data flows that arrive on your load balancers, front end
toe a back in pool of virtual machine instances and does so according to rules that you program,
such as the health and performance of your virtual machines. You can load balance across virtual machines in the same Microsoft Data Center, or even across different data centers and different regions. With a load balancer, you can balance your incoming Internet traffic to your virtual machines. This is called a public load balancer,
and you can load balance traffic across virtual machines inside your virtual network, and this is called an internal load balancer.
What is cool about the cloud and now Azure, for example, orchestrates or uses software to control how things run in your data center. Is that an azure? When you set up a load balancer either a public load balancer or internal load balancer you aren't carving out? Resource is
there is no virtual load balancer, machine or platform to stand up and azure a load balancers simply expressed his functions or rules that you set up,
such as health probes on your virtual machines are on the bike back end How you want to pool and service your data flows in azure. Your load balancers an object you controlled. It expresses how azure should program. It's multi tenant infrastructure to achieve the scenario you went to create. There is no direct relationship
between load balancing. Resource is an actual infrastructure,
creating a load balancer doesn't create an instance, and capacity is always available.
So as your backup will back up your virtual machines, you've stood up and have running in azure. But you can also service backups of your on premise machines and workloads as well as your backup offers an organization a simple solution to backing up. It's on premises. Resource is short term and long term backups without the need to deploy complex on premise, backup solutions
you can back up your azure infrastructure is a service. Virtual machines.
Where's your backup? Provides independent and isolated backups to guard against accident. Destruction of original data backups are stored in recovery. Service is vaults with built in management of your data recovery points configuration. A. Simple backups are optimized
and easily allows you to restore what is needed. You get lots of scale security and no limits to the amount of data you transfer
with azure security. You encrypt the data in transit and at rest, and you get easy and consistent backups. At a data recovery point, you will have all the required data to restore a backup copy of your instance, application and data and with as your backup. Your storage and data is always highly available. You're instances.
Applications and data can be lRS locally redundant storage, where it is replicated three times meanings. That meaning that there are three copies of your data in a storage unit
in a data center. Or it can be GRS Geo redundant storage. And this is the default and a recommended replication option. GRS. Replicate your data to a secondary region hundreds of miles away from the primary location source of your data
as your sight recovery helps protect your applications in the event of a disaster by orchestrating recovery options from an easy to use. Never sleeps 24 by seven as your service as your help your organization with its business continuity and disaster recovery. D our plan.
So there are a few parts of azure site recovery that I want to talk about. There is a management portal that provides a single management interface
for customers who are managing all of their azure assets across multiple disaster recovery sites with 24 by seven. Access as your sight recovery provider is an on premise component, which is installed as a virtual machine and connects to the azure site Recovery Service. And then the third component as your recovery service agent,
is a piece of software that runs on your virtual machines.
For a non premise azure protection. The software agents connect to the Internet and are ultimately connecting you and your future. Virtual machines to the Azure Cloud site, Recovery service and all communications are fully encrypted and secure. All of these things in azure site recovery, like the management portal site, recovery provider
and as your recovery service agents
work as a team and perform like fail over Service's and health monitoring service is with azure site recovery. You can recover quickly when your applications fail, or stall on premise in the azure cloud or hybrid in both places across the globe
as your monitor collects, analyzes and reports on your cloud and catch this on premise environment. So once again, Microsoft understands that you will likely always maintain data center. So let's get in there and mix it up and make it better by creating an implementing hybrid tools so that you monitor and manage Service is in your own data center and in the azure cloud,
seamlessly and in single panes of glass.
So is your monitor helps you understand how your applications are performing and proactively identify issues affecting them, and the resource is they depend on you. Monitor to two fundamental types of data with is your monitor metrics and logs. Metrics. Air numerical values that describe some aspect of your system at a particular point in time
and logs are data records with different properties telling you about your system, events and activities.
So logs, or how you get performance data. And when you combine your metrics and logs with the analysis of the jurors, advanced machine learning and analysis, you get a full view of how your applications, guest operating systems and your resource is air performing on premise and in the Azure cloud.
And if the azure stack wasn't big enough, as you're even throws in a really cool service called Update Management, you can use the Azure Update Management solution to manage operating system updates for your Windows and Lennox computers in azure, in on premise environments or even in other cloud provider platforms. How cool is that? With the Azure Update management system,
you can quickly access the status of all your available updates
on all of your computers. A. Manage the process of installing required updates on your servers. You unable to service from your azure management portal and from your virtual machine pages and azure Azure Update is available for Lennox and Windows, computers, servers and virtual machines. So it's time to face is a ll for our learning check. Quiza ll
What is a technology stack?
What are the two types of load balancers We can create? An azure?
What did the two data sets that as your monitor Reports on
and Windows Azure site recovery, take a nap. So get out there and work on your lyrics and get in the spirit. And when you are rhyming all the time and get on back and we'll attack this quiz on Azure stack,
where's the Sugar Hill gang would say, We're going to get it right With the lyrics of Rapper's Delight, A technology stack is the suite of products and technologies that work in tandem to produce a technology service or solution. We create two times of load balancers and azure public load balancers that air Internet facing
an internal load balancers. Inside our virtual network, we can report a monitor and a lot of things with azure monitor. But the bottom line is we care about metrics,
which are numbers and points in time and logs, which are the events and the comings and goings in our premise and azure data centers, which lead to keep performance indicators. KP Eyes and Azure site Recovery is a global recovery solution for applications, which consists of our management portals
andare on premise as your sight recovery provider virtual machine that talks to the azure cloud
and our azure site recovery software agents that run on our virtual machines and site recovery is an incredibly effective solution because it sleeps all day and has copy written lyrics so it can't be stolen in the microphone. So let's kick it.
So in today's lecture, we learned about load balancers as your backup in sight. Recovery Service is, and Azure is magical, monitoring lyrics and update managers, rhythms and rhymes. And so next time, we will review what it looks like on a day to day basis
to be an azure cloud administrator. We hope all of you are happy learning, and you're learning to love this Microsoft Azure cloud. And so, until next time, from behalf of all of us Cyber Security and I t Learning Team, we want to say Thank you so much for joining us. Take care,
be well and happy packets