Need up to 30 seconds to load.
hi friends
in my previous videos i have covered how
to create sql server database and how to
deploy to the azure sql
also few important
parameters which are
performance insights and azure sql
analytics enablement and stuff
in my current video i'm going to show
you how to create
backups for azure sql databases
so it's very simple and straightforward
let us just directly go to the sql
server i'm not going to the database
this is your database but i'm going to
the sql server so all your databases are
under the
sql server so i'm just going to the sql
server
click on the backups here it's a
straightforward option just click on the
backups
so it is one of the key parameter for
any azure admin
or
even azure devops or sometimes
and especially if you are a database
administrator this is a must option for
you
you can see i have already configured
few backups and it was taken
uh earliest patr restore point is
maybe somewhere february 3rd 2022 utc
so what is patr here
point in time
restore
so how does it work there are two
parameters which you have to remember
one is ltr long term backup retention
and the patr point in time restored
lt policy is actually
copied to the blob storage whatever the
backup it is taken that is actually
copied to the blob storage as a long
term storage
so the copy is a
background job that has no performance
impact on the database workloads at all
so it will automatically happen
uh coming to the pitr
it has a full form service like p80 or
point in time restore so you have taken
one particular backup so other point of
time whatever you have taken as a backup
that can be restored other point of time
data can be restored anytime when you
have when you're lost with your
databases
so moving on
let us just simply click on the
retention policies how do you set up
right so select what is the database all
your databases will be shown here in
this list so select one of your database
so i'm selecting here adventure works
and then click on the configure policies
so here you can see it is very
straightforward how many days would you
like to pat your backup to be kept so i
am keeping seven days you can even keep
it five days based on your type of
requirement that means my pitl backup is
going to be available for seven days and
how frequently you want to take a backup
copy that you can select here whether
you have only two options two all of us
or 24 hours so usually people prefer to
go with the 24 hours and you have to be
ready or to be prepared to lose that 24
hours data as a least case in case if
some disaster occurs or if the data
center is collapsed think about it like
exceptional cases so in that case is you
are ready to lose 24 hours data in case
if your business says that i'm not ready
for that i'm fine to go lose that 12
hours data then you can set it up 12
hours okay so this is exceptional cases
i'm talking about it is not like you
know
frequently happens so i'm just selecting
24 hours and
keep weekly backups or monthly ltr
backups are ela ltr backups what is that
you want to keep it long term retention
you can either
select weekly okay i'm just say one week
that means you will have the
retention period of the one week but
there are many requirements from the
customers or from your business that you
know my backup should be there even for
one year to verify or 10 years also
right so those type of things you can
configure here
you can select your weekly monthly or
yearly right so
definitely there are plenty of
requirements uh people doesn't want to
lose the backups for a least case uh
then they may go with months under years
but but for time being i'm selecting
weekly healthier backups so
just leave it all other options really
that's based on again your requirement
or if you want to apply yes so as soon
as you click on that
it will process that let us just wait
for a few minutes so after few minutes
the deployment is succeeded so just
click on the backup policies
so this is the backup policy what we
have created
so you can see
what you have configured but the result
will be under the database uh
just go back to the sql server and you
will be able to
you will be able to notice that backup
copy every 24 hours here eventually so i
have already created one that it is
appearing but you have to wait 24 hours
to see your another backup copy of the
database okay so this is how it works
and it is not
a one-time job it will keep on happening
it's in the loop so once you configure
the database backup you don't need to
really worry but you just need to verify
as a administrator database
administrator as your administrator
whether backups are being taken
timely if the requirement is business
requirement is changing you have to
again come back and change your
parameters accordingly so those things
you have to keep on changing and another
extra mile if you want to go you can
take this copy and try to restore and
verify whether all the database data is
being
uh backed up properly or not because it
should be in the in a state to restore
at any point of time in the future when
the disaster comes right so that is the
reason it's good practice like every
three months or six months at least once
you just
check that copy whether it is in the
restorable condition or any other issues
that are occurring it's just practice
it's not mandatory so thanks for
watching my videos
