Everyone, and welcome back to the Knowledge Portal video series.
Now, today, we will be speaking about the important topic are due and IPO and these are two factors
are very important, specifically when you are designing your architecture and environment, business,
high availability.
So let's go ahead and understand what Arduino Rabu means.
Now, if you remember high availability, I should always be driven by your requirements.
Now, whenever you design a highly available for doldrum infrastructure, which is also multi availability
zone, there is always a cost associated with it.
Now you're within a lower balance.
There are other ways now I can always even decide to have five servers, a way that will basically improve
my availability aspect as well.
But I cannot always do that because if you try to increase your service, the cost of your infrastructure
will also increase and the business is always after the beam, or I would say after the infrastructure
trying to decrease the infrastructure cost.
So whenever you design a highly available environment, you need to design in such a way that not only
does not increase the cost to a very high level, but it also has a very good ratio to the cost vs.
availability.
Now, there are two important factors when you design a high availability environment.
One is the recovery time objective, which is also quite an ordeal.
And second is recovery point.
Objectivity is known as IP.
So when you talk about recovery time objective, it is the amount of time frame it takes for your environment
to recover in case that infrastructure goes down.
So let me give you one other example.
So let's assume that your infrastructure is located in Mumbai region.
Now, you and due to some natural disaster, something happened in the Mumbai region went down.
Now, what will you do?
How long will it take for you to migrate your infrastructure to a new region so that your business operation
can continue?
And that question, the answer to that question is given by a recovery time objective.
So let's assume that your article is three hours, then you need to invest quite a good amount of money
in designing the region.
So in case your main region goes down to engage the Mumbai region, goes down, your diary then should
always be there so that you can migrate your traffic and your domain to a new region and your business
operation can continue from there.
So this is why ideas should always be defined.
Now, next important topic is a recovery point object, which is directly concerned with the data and
maximum.
It basically tells about the maximum tolerance period to which data can be lost.
I think it should be lost over here.
Now, again, this is a very simple example.
If an IPO is five hours for a database, then you should be taking back off of your database every five
hours.
So you basically test on how much data can be lost as far as business is concerned.
So if business is okay, if I lose last five hours of data, it is fine with me.
It is not a very big issue, but if I lose data of past 12 hours, it is a major issue for me.
So in such case, if business your attributes should be favored, then you should be taking the backup
of your database or important data every five hours.
So when we.
And talk about the relationship between Dewing RPO, this diagram can basically experience a very simple
diagram to understand Suja operations is going on and suddenly a disaster has struck down.
So I do basically.
Dayson, how long will it take for you to recover from this disaster?
Now, again, if a Mumbai region is down and your entire infrastructure is in Mumbai region, you cannot
really rely on the cloud provider to make it up within your ideal time.
So you need to be ready with the backup region, maybe a backup region in Singapore.
So you need to be ready with the backup region and depending upon the deal, the overall preparedness
for you to migrate your entire infrastructure changes.
So just this is the ideal.
I repeat again, it says, how far back can you lose the data?
Now, again, our report is very important in our decision making process, is because when you're migrating,
a region of Mumbai region is gone.
And if you're taking your database backup, let's assume 10 hours back.
So whenever you're migrating the new to the new region, let's assume Singapore, then you will have
the database backup of a hours back.
So that is something which is not really recommended because business will not really like it.
So you're RPO and you're very much interconnected, and whenever you design a highly available environment,
you should consider and you should design your environment in such a way that the ideal and ideal matrix
are fulfilled.
So this is the basic related to our Bernabeu.
I hope the basic concept has been understood by you.
And if you have any questions or suggestions, doubts, feel free to connect us at Twitter, Facebook
and LinkedIn or Millar's instructors Atteridgeville have started.
Thanks for watching.