Microsoft Azure Training - [38] Azure Storage - Part 1 - Introduction (Exam 70-533) Video Lecture | Microsoft Azure: A-Z Guide - Database Management

hi everyone welcome to cloud Rangers
Microsoft edge your training today we
are going to discuss as your storage
this is the introduction series part 1
there's going to be many other parts in
Azure storage to cover the whole
curriculum that Microsoft expects you to
know for your exam so as some of you
know me I'm Shaun is Mel I'm currently a
Microsoft MVP for Azure and that's my
contact information down there my email
Twitter Linkedin as well as YouTube
where you're most likely viewing this
right now and the slides and this is a
question I keep getting a lot of emails
come in we're getting quite the slides
are that's where my slides are
slideshare.net /on is mail you'll find
all the past slides already posted there
as well as the session that we are
having today this is going to be posted
there as well so before we get started
as you all might have known that I
haven't had a session up in a while it's
been a couple of months actually and I
wasn't able to respond to a lot of
comments over YouTube it's interesting a
lot of people emailed asking if
everything was ok well everything is OK
and I apologize for not getting back to
some of you there's there has been a lot
going on I changed my jobs in between
Microsoft terrified worrying me with the
MVP earlier this year so thanks to all
of you who have send in the nominations
absolutely it works as a great
encouragement to you know create these
sessions and the reason that I did not
come up with any more session was due to
the lack of time I wanted to absolutely
make sure that when I come out with a
session that you are getting some
quality out of this it's it's easy to
come up with the session knowing that
most of the stuff I already know and the
demonstrations are not that hard but
going through a quality session where
you get the most value out of it takes a
little bit of time and I want it to be
very fair and make sure that I'm not
just putting up a session just because I
have to do one but I'd rather have a
quality session out there that you will
benefit from so it took a little bit of
time now that things are a little bit
settled what I'm assuming is that we
will be able to continue
you know having more conversations
regarding decisions on the YouTube
comments as well as emails and I still
try to get back to most of you through
email it's just that so many emails come
in every day not to mention my day job
there's a lot going on it's hard to
reply to all of you but I'm I'm hoping
in the next few months I'll be able to
produce more sessions getting more
conversations with you and there are
going to be some live most likely
webinars or presentations if you live
around in Canada near the GT area I'll
be providing some sessions as well so
I'll have the details on that up on my
blog site or Twitter as they come along
so let's not waste time and get started
with Azure storage a lot of you emailed
me Twitter as well is that what is this
as your storage station going to be live
well here it is now and we are going to
deep dive into the introduction so let's
get started as your storage is where all
the storage in as your takes place it's
a very broad statement but that's what
it is anything related to storing data
is happening on edge or storage and I'm
going to make this really really simple
by the time we are done with all the
sessions you'll be absolutely
comfortable dealing with all this all
right so let us start with some analogy
here a bit of history currently if you
are an enterprise administrator like a
system admin network admin or whatever
infrastructure I think they call out
these days you know where storage is
happening back in the days we just put
we'll take a server put your you know
you'll have it read over there and
you'll have local storage on your server
just like local storage in a computer
that's where you would store your data
things change a lot of things happened
fast forward what we started doing is we
needed more flexibility so if your
servers local storage gets full on the
option for you to is add more hard
drives and exchange that storage and not
always that would be the easiest thing
to do you have to copy data over make
sure everything's there there will be a
maintenance window there will be a
downtime a lot of things is to happen so
for the flexibility or scalability what
they started doing was we started
putting you know network attached to
stories like an as system or more in
enterprise II thing would be a sad
storage area network where you can have
as much as storage you want at a
moment's notice as long as your sand had
enough storage over there so it was a
pool of data bunch of disks and drives
together and it was not only just a
storage on sand it's also if a drive
fails you'll still be fine so it's it's
it's its raid great and you would also
have these days tear of datas so some of
your data will be solid-state drive some
of them would be just Sarah and you'd
also tear tear your data based on the
kind of performance you want from there
so that's all great on premises this is
how on previous implementations are
dealing with the storage someone wants
an added volume to your server somebody
wants a file share
lately I was working with EMC and as
well as HP is a storage where you could
have a thief's on the side so you could
actually have a file share directly from
the send your storage subsystem and you
did not have to create a file share on a
server and spin up another VM or under
physical server to do that so a lot has
happened so as your storage serves all
of the above and more so in Azure
you can do everything that we are doing
on premises and much much much more so
let's get into that what do I mean by
much much much more so as your storage
is part of an overall thing that's
called as your data services it's a
component of Azure so under data
services you have as your storage you
have as or as your site recovery as your
backup and they're all part of as your
data services okay
so anywhere you're storing data is going
on as your storage or the other to site
recovery or as your backup so what says
your store is used for well it's used
for storing everything so it storing
files you can store website you can also
store virtual machines right so in the
previous in the previous sessions when
we were creating a virtual machine the
storage account that I kept talking
about and we never got into details of
that was that your virtual machine needs
to be stored somewhere in a journal so
as your storage account was where your
storage was bring
stored there so every time we were
creating a virtual machine we were
creating or we used one of the azure
accounts where we are storing all this
data the same happened when we were
dealing with as your websites you might
have noticed that you know when we are
doing that your website we never really
talked about where all these are being
stored if this was on-premises
infrastructure those would be something
you would be looking into right now that
hey what do I store this data well in
Azure storage account we were storing
the data so even for the paths or
platform-as-a-service
you are still using Azure storage to
store all the data not just one liter
virtual machines okay so we'll get into
the data types in a bit but let's
continue into them so the first first
thing you need to do in Azure to store
data is to create something called as as
your storage account okay so that's the
first thing you need that we'll have in
our subscription we need to create a
storage account where things will get
stored now with the Azure subscription
and this is 2016 now you can have
multiple storage accounts in a single
subscription so some of you might have a
question right now that you know why is
one storage account where I can store
everything can do everything right I
mean why do we need multiple storage
accounts if it is a pool of data and as
your gives you almost unlimited amount
of data I can just have one storage
account and put everything there yeah
I'll have a little bit of structure
there so I'll get into that in the the
next slide where we are going to talk
about why you might need separate
storage accounts in one single
subscription okay but for now just
remember you can have like one multiple
storage accounts in a subscription while
recording this video in 2016 I think
each storage account and you know don't
take me on for this one do a little bit
of TechNet searching on this one I think
each storage account has a limitation of
something ridiculous like 500 terabytes
of data per storage account so obviously
if you need more than 500 terabytes of
data you'll have to have
storage account edo subscription so
unless you need in you have a need for
that you'll need multiple storage
accounts for that okay and creating this
as agile as your storage account is
quite simple you need a URL and this is
called also an endpoints that will come
out of this URL and I'll get into that
later as well but you'll need an URL so
this is pretty similar to how we used to
create cloud service if you remember
you'd have a name for your storage
account and this name has to be unique
and the reason it has to be unique is
because this urls will have endpoints
that might be able to I mean users might
be able to access this from the public
domain so these endpoints have to have
an unique URL and I'll show you that how
that happens it will also need a
location
so each storage account is located in a
single location so for example I use a
central US or East us - you might
depending on which location you are
close to you might have a location where
you want to store your data so that's
one thing you have to remember for
creating storage account and you need an
account type which is the replication
option actually they call it account
type or replication option there's a
little bit of replication going on with
this data in the next slide we'll see
that so these are the primary three
things there are there's another thing
the resource group and all that I'll
show you that in the demo but for
creating a storage account that's all
you need so if you are creating so from
what we discussed right now if you are
trying to create a virtual machine right
now and that machine needs to be stored
somewhere
ideally in your subscription if you want
to structure this and you are doing this
in a corporation in an enterprise level
you probably want to create a storage
account first and make sure that that's
ready before you go and create a virtual
machine the virtual machine wizard gives
you an option to choose an existing
storage account to store your virtual
machine data or crew or have the virtual
machine VHD located there or as you must
have noticed in the previous sessions
when you bring up the virtual machine
creation wizard it gives you an option
to create a new storage account if you
do not already have one chances are in
our enterprise environment you
want that option because you want all
the virtual machines perhaps to be
together in one storage account in one
single folder all organized so that's
something you'll have to know as well
okay so let's move on and I'm going to
talk a little bit about the storage
account details here like what does the
URL mean the location mean as well as
the character the most important one for
your real-life implementations as well
as exam will be the replication options
so let's deep dive into that a little
bit so account types which really mean
replication options in storage accounts
context okay so there are four actually
there are five but there are four we
want to discuss about here and the fifth
one I'll I'll talk to you when I give
the demo and why this is not part of
this yet as far as your exam is
concerned remember this for now like
some of you note as your is moving fast
forward at such a speed they keep adding
more stuff and it's hard to keep up but
the exam the way it works is it takes a
snapshot of time and it says this is
exactly what's going to be on your exam
so remember this but you know I want
this videos to be very real life as well
so I'll explore the fifth option with
you once we get to the demo so when you
are creating a storage account you are
basically creating a little space so you
know if you are thinking in a sand point
of view it's basically carving or it's
creating a LAN for you in the back end
it's like a volume right in a server
term the whole LUN thing is like a
volume that you are creating so when
you're creating a storage account think
of that that way that you're curving a
volume but in San what happens is that
on Paris's in your storage area network
you will already have the sand
configured in such a way that you will
you will think that does this server
need this 100 gigs of data should this
data be on Saturday off source
solid-state drives
what kind of storage will it be on so
you can handle that from the backend
obviously right and in a sewer it's
almost the same thing when you are doing
this a store storage it's it's asking
you that what kind of
four disks it will be on for example and
it will also give you that what kind of
failover or replication or what kind of
data redundancy it should be on as well
so assuming that in your local storage
on your server you will have raid and
this rate could be just a mirror that
you know I'm going to have two hard
drives if data is going to fail in one
hard drive it is going to be it's going
to be fine because the other hard drive
is still has a data or you might have a
raid five with parity and data striping
what if multiple disks fail your data
will still be ok same thing happens in
your Nass as well as you're saying you
would still have the raid concept the
data is going to be all replicated
between these disks so image here we
have four different ways of doing this
but it is way more advanced and robust
and I'll explain how so your first
option and this is probably the cheapest
option that you have is locally
redundant or standard underscore LR is
locally redundant store storage you need
to know the standard underscore LRS in
the brackets over there or the
parentheses because this is what
PowerShell uses to identify these
storage types or this replication
options okay so you can always refer to
this one and I'll show you how to find
that out from PowerShell as well so
locally redundant storage it's basically
saying we know that in as your data
centers or as your regions or locations
this is how it is you have a region or a
location for example east USA Eden East
USA location you might have multiple
facilities or multiple data centers so
you might have two data centers in East
US locations okay so in locally
redundant it's saying that three data
copies in single facility in single
location here single facility means in a
single data center in a single location
so if you're choosing the locally
redundant your data will be in one data
center in one data center it will be
three different copies okay so somehow
if your data that is residing on this
story
system in the data center breaks there
are still two other copies in the same
data center in the same location okay
this is great it's one of the cheapest
because the data still stays in the same
data center it does not even go out of
the data center but it but it is most
likely already redundant then what you
have on premise right in on premise you
probably just have one Sam with a raid
and everything but what happens if that
whole send system breaks you are pretty
much done this is similar to having
multiple or three sands in one data
center and this data is located in all
three of them pretty redundant already
but as you like everything else take
this a little bit further then you have
the zone redundant or standard
underscores z r s so what this one says
is that I'm going to have three data
copies in two or three facilities or
data centers in a single location so if
you are going to store the data in East
us a location what it will do is in each
location like I said it could have two
or three data centers which are
completely separate from each other
they are going to have this three copies
in like these three data centers so you
are now living the entire data center so
forget even the servers forget if even
the sense if your entire data center
breaks you have your data in another
data center in the same region means you
are still in East USA in three separate
data centers with your data very highly
redundant some of you spend a lot of
money on premises to actually have some
kind of implementation like that but in
Azure is just like a click to make sure
it did your data is replicated like that
the little catch with the zone redundant
is it's only for blob storage or I'll
get to what does a storage types are but
it's only for blob and you have to
remember that in real life if you're
trying to have like a table data or
queue data you can't do that but for
most people blob storage is all you need
and this is great because now you
already have redundancy but it's still
going to be in the same geographical
area okay the next one is geo redundant
or standard G
our s this is amazing and it's the most
resilient of all storage because this
one actually takes care of your dr
scenarios so your geo redundant storage
type is LRS which is locally redundant
you have three copies in a single data
center already in the same location plus
three data copies stored in a secondary
location so what's happening here in
East USA you are going to have your data
in the data center with three copies as
well as now it will have another three
copy of your same data in a totally
different location geographically and
that location could be West USA it could
be anywhere else any other data center
okay but it's just not going to be the
same region so guess what it already
took care of your storage subsystem
subsystems dr or disaster recovery what
happens if all of West USA you know have
has this huge disaster at the data
center and everything is broke heaven
forbid that ever happens but just
imagine if that happens it actually will
have data in another geographical
location in a different site like east
of the US coast where your data is going
to be located so it happens to be one of
the most resilient because this data is
copied so many times in so many places
it's the most resilient it's expensive
as well and the fourth one it's read
access zero zero redundant or standard
are a GRS is the same as GRS it's you're
going to have three copies in the local
data center three copies in a different
region or location in a local data
center but the difference with read
access geo redundant is if there is a
failover situation like if ever there is
an issue where there is a failure in one
of the locations the other location is
not going to give you a breed right
option it's only going to give you a
read one the option so although all the
options are the replication options that
we have seen over here gives you a
readwrite both access to your storage
doesn't matter if
one data center or the other data center
one location or the other location but
there might be reason where you think
that I'm going to replicate my dis data
to a different location but in case
there is a failover in my primary region
my secondary region is one lis going to
have it read one lis access I am quite
sure there are business reasons for this
you might want to make sure that when
you run in a failover state people are
not really writing data because you guys
have tried to get over I don't know some
you you're going to recover from all
this disaster and everything but you
want to make sure nobody's writing any
data to your systems during that time
you might have a business reason for
that okay so these are the four
replication options of your data that
Azure storage provides the fifth one and
I'll show this one in the demo it's
actually premium storage with premium
storage that your your storage subsystem
is faster the solid-state drives it's
not part of this but there is a premium
storage option as well your subscription
actually had has to have access to that
and you might have to request Microsoft
support to provide you with premium
storage option you just have to
basically open a ticket and be like hey
I need premium storage for whatever I'm
trying to do and they'll enable that for
you so you can store data in premium
storage for people who are looking for
higher cups with solid-state drives and
things like that so there is a fifth
option there another thing important
thing I want you to take away from this
is that each storage account can have a
single replication option uh-huh this is
where you'll find out why we might need
multiple storage accounts so your one
storage account can have only one
replication option so if you have one
storage account where you are keeping
all your virtual hard disk drives or the
VHDs
you if you have an account which is
locally redundant that's all the type of
replication you can have in that storage
account you can still store other type
of data don't get me wrong you can store
files and folders and everything else
but it will only be locally redundant
you cannot have a storage account and be
like I want part of this data to be
locally redundant or part of this data
to be zone redundant you
and so for that you'll have to have
another storage account where you will
specify the replication option so that's
another reason you might need multiple
account types or multiple storage
accounts with different replication
options depending on the kind of data so
I'll give you one very nice example for
enterprise people out there is that you
create a you create a server a VM and
it's using locally redundant which is
great three copies of data in the same
data center you do not have any specific
disaster recovery plans besides the
single zone or single location but the
data you put in that server on another
volume like in volume D or volume e or
whatever that data needs to be
replicated you know from one region to
another region you have to make sure you
have that data replicated somewhere else
which is not in the same location let's
think that it's a compliance requirement
or it's a corporate requirement so you
can actually have your server be on a
storage account and another storage that
needs to be there attached to it where
the data is going to be replicated using
another storage account so you can do
that there nice fancy ways to do that to
store that kind of data okay so those
are the reasons you might have different
account types like I'm mentioning okay
so that's cool so let's move on and
we'll come to the types of storage in
the storage accounts I probably don't
need to show you this before I jump into
a demo but I thought that it's important
to understand the types of storage you
have so we have we created a storage
account we chose our account type or our
replication option now I'm telling you
the kind of data you can actually put in
there okay for most of you might not
care but for there's a lot of you who
might care as you as well depending on
the type of storage you are trying to do
because I exam or I have to assume that
some of you are going to use this as
infrastructure as a service the storage
some of you might actually use this as a
pass or platform-as-a-service a storage
and things like that so let's deep dive
into that so we have four kind of
storage
that you are for kind of things that you
can store in your storage accounts one
and the most important and the common
one is the blob storage I mean if you
are doing infrastructure-as-a-service
this is what you'll be mostly using all
the time in fact most of our sessions we
have been using this so far okay so in
blob storage blob which is binary large
objects that's what it stands for
it's basically for any type of
unstructured data coming structured over
here really means files or binary data
documents images videos logs even
virtual hard drives these are
surprisingly unstructured data pins
these are kinda kind of datas that do
not follow any structure you have
different kind of files different kind
of file types all can be stored in this
one bucket okay so this is what blob
storage is these are text files or
binary data files VHDs when you create a
VM it's all blob storage okay and this
is what we have been using so far then
you have a table storage table storage
is if you are familiar and they develop
developer and familiar with sequel
you'll understand what table storage is
it's basically relational data you're
putting in a table right however there's
a little difference with table storage
here and do not confuse this with as
your PA's offering of sequel okay if you
are doing all of that this is not that
table storage is something similar where
you have a storage where you have
multiple tables but the data in this
table do not follow a schema I know the
sequel guys are going crazy right now
what do you mean no schema
well this data is going to be in a table
but it does not have to have any schema
or structure so I might have data where
I have my first name last name and my
address and the second record might be
first name last name address and all of
a sudden it will also have something
like my sex right so it is structured
but it does not have any schema like
there's no strong type and these are
table storage you are restoring this
data in a table and the reason you need
this kind of storages is for developers
who are actually doing a prototype
or they're just working on an
environment where the data type is
changing really fast you do not know how
much more data or information you're
going to put in there
so you're just rapidly developing it in
data width which requires tables and you
are not set on a schema yet but you want
to store that so you can store that in
Azure storage as a table store I've been
as a table storage in Azure storage
accounts okay then you have the cue
storage a lot of infrastructure people
might not be familiar with what this key
will skills are but your developers will
be perfectly comfortable or should be
comfortable with what cue cueing is so
what happens is just to give you a
little feedback in a very very simplest
terms is that distributed applications
might need to communicate with each
other and one of the ways it
communicates is using a cue mechanism so
if one process is trying to communicate
with another process or end of service
and you have a constant flow of data
that is coming in the destination
processor service might not be fast
enough to process all this data when
let's assume that there is a transaction
going on thousand times per second for
example for some big banks or things
like that so what will happen is all
this instructions or all these things
will be stored in a queue to be
processed by the service at the
destination at a certain amount of after
certain amount of capacity you know it
takes this data or this transaction it
does something on it done it takes the
next transaction so it will go into the
queue storage and find out all that
things are there in the queue and start
processing them one at a time or how
many it can handle at a single time but
it requires this storage to store this
communication somewhere and one of the
reasons they would actually do this
queue storage just way to a little bit
of a detail is if you have thousands of
transactions and the service cannot
handle it you don't want this
transactions to fail you just want them
to wait right and you want them to wait
for the other transactions to happen
when this is done and as your storage
account can store this queue data for
you and that's one of the things now the
next one and this is going to be really
interesting for the infrastructure guys
is the file storage it's like a file
share so you can use your Azure storage
account like a completely a file share
think of it as a file server
okay so if you are on a virtual machine
or a client computer you can actually
map it drive to get to this file storage
back in the days oh well not backing
that is even today you have file servers
which does nothing but people go there
and they map the file share to a UNC
path on their computer as a bap drive so
they go over there they have access to
all this files so as your storage and
this is this used to be previewed now
it's public right now it has something
called as file storage so you can use
your as your storage account to store
this as an SMB share or a file share and
you can literally go to these virtual
machines and just be like a map it Drive
this is the UNC path connect to it and
you have access to all that I have been
using this file storage quite a bit and
I will tell you how so I do a lot of POC
proof of concepts and things like that
and for example I have to download all
the ISO files for for example sequel
share / end exchange and all that so
what I think it was in my your account I
have a storage account which is like a
file storage where I kept all these ISO
files so it doesn't matter if I destroy
all these virtual machines I do not have
to download all these ISO files all the
time I just have to map the drive and
pretty much get Daiso files from there
ok and it's cheaper in the long run
because I'm not downloading all this
data all this time and as your storage
is quite cheap so if I even store like
about 200-300 gigs of iso files it
doesn't really cost a whole lot few
bucks a month so it's not really that
bad for the kind of work I do so that's
one thing I've been using from a
prototyping or proof of concepts all the
time you might have something similar in
your organization and you can do all of
that and with this file storage you can
also do a different kind of access like
how you want to access this data and you
know who has permissions to access this
data and we'll definitely get into a
demo in that in the future and show you
how that is done okay
all right so let's move on the last
thing I want to talk about before we
jump into a demo is as your data account
endpoints now that we know the kind of
for storages you can store it in for
store well yeah for storage things that
you can store in as your account
I want to talk about a little bit of
creating the account and the URL you
remember out in the backend
I had this URL thing when I said when
you create a storage account you need to
put in a URL and what happens let's
actually see that let me grab my pointer
here so for a when you create a storage
account it will already have a provision
for this for storage types like you have
a blob storage table queue and file we
just discussed that so this is going to
be your account name this is going to be
unique and now it will make sense why
you will need to be unique because each
storage type will have an endpoint how
your storage storage is going to be
consumed or accessed so for blob storage
let's say I'm going to have a storage
name called Ranger store that's my
account name so it will be HTTPS or HTTP
by the way it does it both over here I'm
obviously showing you the secure way of
doing this but you could access this
with HTTP as well so make your
application use HTTPS is the secure way
to do it so HTTP Ranger store blob core
dot windows.net so I'm by looking at
this you know that this endpoint will
only access the blob storage okay so
then you can have the table name it will
be the same it will be table for the
queue it will be queue for the file it
will be file but it will always have the
account name in the URL to exactly
identify what storage which is storage
this is it's pretty interesting with
this endpoints because if you're writing
an application the application might use
table or queue storage or file when you
need to create the UNC path you can
actually take the UNC path out of this
URL some of you might be wondering how
in a second
you're telling me blob storage is where
I put all my virtual hard drives for my
VMs or bi files and everything what
happens if I really go to this URL do I
have access to this data publicly
because that kind of defies all purpose
of security because the data is
available online do not worry about that
those are the endpoints but there are
security stuff in place so if you
actually just have a blob storage so you
know you have like a /v HD
follower /my VMV HD now you are not
going to be able to access that directly
because there is security in place to
make sure that you can't but there is
also provision in place to make sure
that you can if you really want to so
just like onedrive public you remember
in onedrive you have this option where
you can make this entire folder as a
public folder so where everybody can
access that well guess what this is how
they're most likely doing it you are
going to have a storage account where
that where you are making it public and
in the backend it's going to nur l like
that where you can see all this data
stored there or you cannot see all the
data that is stored there because you
have the right storage access in place
so by default it's not going to be
public I'm going to show you the details
in a bit or what that is
alright I think I've talked quite a bit
in the last half an hour let's go ahead
jump into my client system in my Azure
subscription and I'm going to show you
what I'm going to or how we can do some
of this and get you started with in a
storage account so you can take care of
this there are two things I want to
mention first of all one is that I'm not
going to use a classic portal that we
always use the manage dot windows azure
comm or whatever that was I'm going to
use the new azure portal which used to
be preview but that's now final and it's
generally available to everybody I'm
going to use that portal and I think you
should be as well that's where things
are happening
that's where Microsoft is supporting
most of the things ok so I'm going to
use the new portal and the second thing
I'm going to absolutely make sure you
understand is this for this exam there
are two models out there in as you're
right now one is a classic model of
deployment and another one is actually a
resource manager
deployment model if you do not know what
it is you really need to look that up
what is the difference between a classic
deployment model integer and a resource
manager model but your exam right now
with the storage point of view for now
in 2016 you know it's actually almost
the end of January 2016 but I mean right
now it's all classic model so everything
I'm going to deploy is going to be in a
classic model
the newer model is the resource manager
it's almost similar but there are
architectural differences that makes it
completely different in the backend as
well so that you can do on your own time
or I'll have a different video but for
the sessions we have here it's going to
follow the Microsoft MOC of shell
curriculum which is Aston using the
classic model okay and I'll show the
difference in the portal as well what I
really mean so let's jump into the
portal already so I'm in my portal right
next portal azure calm if you recall
there is to be preview thing written
over here somewhere it's gone right now
so this is no longer in portal this is
the newer portal okay and this is where
you are I'm logged in to my subscription
the thing that I'm going to do right now
and if you go to all resources here you
will see my subscription is empty
there's no resource to display there's
nothing it's like almost a brand new
subscription this is where ideally you
would be with your trial account right
and depending on where you where you are
using this you might have other
resources as well so what I'm going to
do is I'm going to create a storage
account before anything and the way I'm
going to do that is I'm going to go to
new in new over here I'm going to go
under data plus storage this is where
the storage account will be created and
if you come over here scroll down a
little bit there is something called as
a storage account use blobs table queues
and files for reliable economical cloud
storage this is exactly what you want
that's what we were talking about you
need a storage account first let's click
on that this is where it actually makes
a difference so look over here it's
actually asking you select a deployment
model and by default there's a resource
management model you can click a little
bit over here and go to learn more and
find out what resource manager for new
workloads are and what it is we are
going to go use the classic model over
here because that's what you know exams
covering right now that's what most of
you people might already have out there
so that's fine let's go ahead and create
a classic storage account
let's go click on create here it's going
to bring under pane and it's going to
ask us given that wizard so you remember
that URLs that we talked about cord
windows.net this is where it will start
coming out of right so it's asking for
that unique name so if I do something
like I know it's going to be taken for
for sure like Microsoft let's see if
it's taken or not and click outside it
actually tells you over here the storage
occurred Microsoft is not available and
this is again the same explanation I
have that it has to be unique because
you might be able to access or might
need to be able to access this publicly
so it has to be something unique so I'm
going to put Ranger store one two three
I'm assuming nobody has that yet click
outside it's ok so it's a green
checkmark over here so I know that this
storage account is not taken already now
it's asking for the type this type is
actually replication type right and the
one that we are talking about you see
that standard are a GRS so by default is
doing the most resilient ones and well
it's doing the resonant one with the
read access rate the last option of the
4th one we had was are a GRS let's click
on that
by default it gets that but I do not
want that one because for this demo it's
probably going to be a little expensive
and the other thing is that it will
actually show you the one over here so
the one we are taking is read access geo
return date it's 7:40 to you you know
cost per 100 gigs it's it well 400 gigs
of data it's only 742 Canadian dollars
it's actually pretty cheap but even
cheaper than that is locally redundant
but you can actually see that what's
included in locally redundant so I can
have a block and page blobs table Q's
500 maximum I up Saunders this 99.99
well 99.9 my SLA so most of them are
going to be same with geo redundant it
actually says read access to secondary
one Lee so this is not gonna be read
right so there are some differences over
here so I told you there's 4 and there's
the fifth one which is premium locally
redundant so it's locally redundant but
it could be on premium storage do you
see what's the difference
look at this the regular locally
redundant has 500 ions the premium
locally redundant disk has 5000 IRS
Wow like that tens times more than the
regular locally redundant you have so
this is for I don't know some of you
might require sequel database to won't
be on a very fast I ops based on your
data so this is like 292 bucks for per
hundred gigs and this one for 1e 128
gigs is $23 that's quite a big of a jump
over here so you can see how expensive
this is because this is on really really
fast it's as these or you know pull of
high ops data over there
so anyways for for our and you have to
be sure I mean you have to be absolutely
sure that what kind of architectural
decisions you need to take that needs to
take place when you choose this data for
my demonstration purpose I'll take the
cheapest one which is locally redundant
and I'll go select see change to
standard - LRS which is great so I have
my storage account I have this my Visual
Studio enterprise with a bazillion is
the subscription name you'll have your
subscription name here resource groups
we have chatted before you know you do
need a resource group where all things
are going to be located so for classic
the resource group used to be created at
the backend resource group is actually
very important in a resource manager
model of deployment in this one I'm
going to just give it with Ranger
resource group it's a random resource
group that I'm going to put in where all
my workloads are so resource group is
just grouping all the workloads together
I'm going to just choose a central US on
my subscription pane to dashboard I do
not want so that's all that is required
for a storage account to be created okay
we did not put any data in here nothing
sorry nothing is happening in here it's
just creating the data so it's a
deployment started let me give it some
time it doesn't take too long actually
to finish that but I'll come back when
it's done all right looks like the
deployment was done if anybody was
looking the clock here it was twelve ten
PM is twelve eleven so took like a
minute to actually deploy the resource
group over there so let's go to all
resources over here and see the
resources I have so Ranger store one two
three was my name for my storage account
and it actually is telling you over here
that it's classic
okay it's a storage account which is a
classic model location where this
storage account is as well and that's it
so let's go click on that and see the
details we can find out from the storage
account we currently do not have any
data in there okay so it's actually
telling with the type it's a standard l
RS so it's locally redundant storage so
that means it's got three copies in the
single data center in a single region
this is the name this the location it's
available right now and it tells you the
blobs the files the tables and queues
the four types of storage that you can
have over there but it opened all
settings or the properties here directly
so let's go in back so if I go to the
properties here of this strategic and it
gives few details it's online they can
type location primary status is
available last geo replication failover
neighbors so this is never going to
happen because we do not have any geo
replication enabled and these are the
endpoints so if you recall the endpoints
that we were talking about was HTTP your
account name dot block or the windows
net so it's telling you
by default this four endpoints were
already created for your storage so it's
ready to go it's got a resource group
rare Society subscription name those are
the details so if you are developer you
need the queue service endpoint or table
or you are creating that map for the
network drive file service endpoint you
can actually can take those from here
right I mean this is where you come to
take that URL and you know once you work
with this too much I don't even come
here because I sort of know it's always
going to be my storage name Turk blob so
I can just pretty much figure that
there's something called as keys over
here these keys are the one which are
mentioning about having access to this
so if you are going and creating a you
know any table data or queue data or
even using codes to access your data you
will need the connection strings or
you'll need the primary and secondary
access key these are the keys that
actually protects your data online
unless you have access to this key
there's no way you can access this data
publicly just like that you have to use
something else to get to this key I mean
use this key to get to those storage
right so this is one of the security
mechanisms that are there we'll get into
details of the access keys and how to
access key I mean data we
that later in different things storage
account type let's go over there there
it will actually show you that this is
locally redundant or this the standard
allure s that we were using and there
are all the other options over here
right there are stuff that I have that's
not available for me the premium a local
rhythm that premium locally redundant
over here I do not have access to so
this is showing you on your replication
tab
that's the labor edition that we have
right now okay you can have one
replication type at the time so you can
proud perhaps change that but right now
you just have locally redundant you
cannot have two of them together like
invention custom domains this is not
something we have touched custom domains
is when you want to actually rather than
having the Ranger stored blob the
coordinates you can associate a custom
domain or your domain with this is
storage maybe for your developers to
make things easier or to do whatever
thing right there is a way you can
associate a custom domain and we'll go
through that in a future session over
there okay and then you have bunch of
monitoring I'm not going to get into
details over here you have diagnostic
audit logs you can actually see who has
been accessing what you can have Ellard
rules to let you know what's going on
there as well this is something we'll go
into session when we talk about
monitoring and alerting of storage
accounts right let's go click on the
services so the blob service I want to
click on that we are not going to get
into this in this session but it
actually shows you how to go store data
so it just says you don't have any
containers yet for the blob storage so
it basically tells you or gives you more
details of these storage types blobs
files tables queues and all that okay so
that's one thing you can do to actually
access that and the next session this
will be more important where we'll be
going through each and every data type
and see what we can do there so that's
all that is to there for storage
accounts and we are going to jump into
PowerShell to see how to do this in
PowerShell just when you thought you
were done all right so this is how
empower shell you can actually create a
storage account it's very simple you put
a storage account name you put the
location and the type is a standard
underscore LRS
okay so I'm saying by default I mean I
want this a storage account to be in
locally redundant storage you can ignore
this if you really want to this will
still work so it will put a default
storage account type if you remember
when we were creating it by default it
picked one up you can pick a default one
it might be the read access dual
redundant most likely that's one it will
print by default so I'm saying that now
I'm going to have the I'm going to have
the type over there mentioned when I'm
doing this right so I don't want to I
don't want to I don't want to I want to
specify I don't want to pick up a
default one so before we create one
let's actually go and see the one we
already have and you do that we get as
your storage account command layer so
let's go ahead and run one leave that
this is where you come to run this let's
go ahead and run that we will see the
one we already had created which is what
in Central USA we created one it was
called
Ranger store one two three these are the
endpoints these are the account types
replication so it gives you a bunch of
information to actually see what you
have right now so that is get as your
storage account so let's go ahead and
create one so I'm going to do exactly
what we did in the portal and you do
that we knew as your storage account
it's very understandable so let's let's
take only this line and you can actually
just create over here and it will if you
could click on this one run selection
it'll do that but I like highlighting
this just to make sure that I'm
absolutely doing this one so run
selection it takes a little bit of time
while this happens to create that for
you so when we do get as your storage
account it will show you now there are
two accounts and I'll show you from the
portal as well but before I do that you
remember I mentioned that how do you get
this kind of information like I mean if
you I mean yeah you can go to TechNet or
you can watch my videos and figure that
out you can bring it google it whatever
you do but how you can find that I'll
show you a nice trick over here and this
is how sometimes I do this in a very
fast way so in any command so if you
have a command let that is new as your
for once you for the ones who already
know this it's not a big deal you
probably know what I'm talking about but
what I do is I come home over here I do
help help out and it will give you the
help on this account it will show you
what this command lab can actually do in
this one is not obviously giving me more
so what I'm going to do is I'm going to
go and do help and it's giving you an
option over here with detailed okay so I
want detailed information on full
information on that clip so detailed and
full it will give you more information
about that commandant right so let's do
detailed in detailed it's just telling
you all the switches or parameters that
you have so we used storage account we
used location you can use label the
bunch of stuff that are that are like
you know that are not compulsory I mean
you don't have to put them there but
they're there so you can see over here I
have type standard LRS but it's telling
you in type what are the ones you can
actually put there so you can put a
standard LRS you can do zero as the zone
redundant zero in and then read one
leader in and then and remember the
fifth one I talked talked about inste
premium locally redundant so this is the
fifth one you can put over there too so
by doing this help and detailed you can
actually find more information or more
things you can put in the parameters
over here so I picked up the standard
underscore l RS from there for our
account over here anyways so that's one
pretty nice way to actually figure that
out and you know get more details about
these parameters that you can of course
go to TechNet and do that sometimes I
just like being over here I'm so
involved in the PowerShell console that
I'll just go there and get all the
information so let's wait for this one
to happen here it's taking it takes
about a minute so I'm going to pause
this a bit obviously surprisingly it's
taking a long time for this to happen
all right let this happen in the back
end actually we need to go back to the
slides to cover more stuff so I'm going
to keep this up and running over here
this is definitely taking longer than I
expected from the poro for sure so
anyways it's not created yet but it's
doing that so let's go back to our
slides here and I want to just touch
base on two things because this is part
of the as your data services there's two
other things
what is a as your site recovery or
disaster recovery in general and as your
backups of what these are
so as your site recovery it's an amazing
thing which is the entire PR thing we
used to do on premises but it takes a
lot of planning a lot of you know
infrastructure in place a lot of moving
parts that needs to happen but Azure
makes this very very simple with as your
site recovery you can protect your
virtual machines or physical servers or
even your inter hyper-v or VMware
infrastructure on-premises to Azure or
another data center so technically if
someone says these virtual machines
which you have on-premises right now
needs to be on a DRA location you just
enable the service it obviously there is
cost associated with it what it does is
that it will take this entire virtual
machine and it will take the data take
everything there and put it on Azure or
it could be another data center that you
have so as you will coordinate this for
you as your site recovery will
coordinate this for you
and take the data and take it to Azure
or another data center for you so
there's a lot of moving parts that
happen in the back end but Azure says
that they will handle it for you and
they'd make it really really really
simple
so you're basically protecting virtual
machines and these virtual machines
point primarily as your site recovery
came out it used to be only hyper-v
virtual machines with or without a CMM
so a CV mmm actually sorry there's a
type of their virtual machine manager it
does not have to be on a virtual machine
manager okay or it could be a VM on a
VMware implementation as well it does
not have to be hyper-v can be a vSphere
or VMware or it can be an entire
physical server that you kind of
replicate to eighth-year location okay
and like I mentioned the secondary site
can be in Azure or a data center that's
your data center so you have a data
center in Toronto you have another data
center in British Columbia for example
or somewhere you know in New York all
you have to do is use that as your site
recovery point the data and tell them
where you want dislocated they'll do in
the package there's a lot going on there
I make it sound simple but Azure does a
lot through virtual machine replication
it could use always-on from sequel to
replicate your sequel data there's a lot
of thing that happens in the backend and
we'll go through this in a future
session but I just wanted to give you a
brief introduction of as your site
recovery if any one of you in who's
involved in infrastructure and have done
ad our site before you'll really
appreciate this service because you know
how many things you have to do for ad
are said to be up and running you need
to have the VPN tunnel you need to have
another infrastructure over there
powered redundancy everything else as
your does that for you okay and then
there is as your backups I I like this
alright so I mean it's not the most
robust out there but it's I like it what
it does is that it basically makes Azure
as one of your backup mediums so rather
than having a hard disk drive where
you're doing this or most organizations
they do backups on tapes you can say I
want to do the entire thing on Azure
storage okay so what you basically do is
create an azure vault and you get the
vault credentials and then you download
in and as your backup agent on your
server so if you have a server called
server 1 and you want to backup the data
of the server to Azure what you'll do is
you download the backup agent and you
basically put the vault credentials that
you created on Azure
and you run windows backup yeah you run
windows backup to configure it and
schedule the backups you don't use
anything fancy the backup agent what it
does is it creates this destination type
or data destination in your windows
backup so in windows backup you'll all
of a sudden find an option what it gives
you a destination to save that data on
when on Microsoft Azure and at that
point you put in the credentials that
you downloaded from the vault and you
take it backup of your server or the
data on the server and it will be stored
in Azure it works great I have a bunch
of servers that I you know backup
through this method I just go and put in
all the data in Azure it can sit over
there in the vault it's very secure and
I do that a couple of things for you to
remember is that if you are doing as
your backup or if you are doing as your
site recovery do not forget that there
are rules and regulations that are in
place where you can store data all right
so for now in Canada
you cannot store government personally
identifiable data in USA there are in
Ontario at least there are regulations
that you cannot so you cannot take
people's you know information as a
database and it stored them in as your
backups because we do not yet have a
data center in Canada Fraser there is
there there there are two on the way
that are being made in Toronto as well
in Montreal we do not have a final date
on the release yet so the closest for
means is the UST which is not located in
candidates in USS so there are
regulations that prevent you from
storing data so be careful or make sure
you understand your regulations before
you go do that because you might be
violating some you know some regulations
somewhere if you do that if you do not
have it it's a private organisation this
is absolutely secure to do so because
you're creating secure vault nobody has
access to that and it's great so you can
do as your site recovery and backup that
way I will have a future session which
will go and do that I mean we'll get
into details and go through a demo on
how exactly you do that cool I think
that's all I have from part one
introduction actually I'm curious if the
if the as your account was created from
PowerShell let's go and see all
resources let me go over here oh it's
none good good good
so looks like it succeeded it definitely
took more time than I initially thought
it's going to take so let's do a get as
your account I'll run this and I would
see what it tells right now it should
shows there are two accounts sorry this
is a little out of band I usually wait
for you know showing this but okay so I
have one over here which is Ranger Store
one two three-and Rangers door four five
six
this is there as well okay so if I come
over here alright I created all
resources as you can see it has Ranger
Store one two three and ranges store
four five six the Builder gradient over
here boater classic so that was the way
you can actually do this in PowerShell
as well cool
so anyways I'm done over here with all
the information for now we are at our
last slide so in this session we talked
about creating what is Azure storage
account or what as your storage is all
about that
services like as your site recovery as
your backup we went through discussing
what are the different data types you
have in there or the replications
options you have in there and we went
through a demo both in PowerShell as
well as the portal for Azure where we
can create as your account and things
that you have to do in there so this is
an introduction in the next one's will
deep dive into more technical stuff and
we'll have demos on that as well
so as usual at the end of the slide over
here we have the training site that's
located their YouTube channel cloud
Ranger Network that's where you are at
right now most likely my slides that I
receive so many emails on that and I'm
sorry for not putting this on there
before they have been on the SlideShare
for a while it just that I hadn't put in
there in any of my slides this is where
all the slides are all the old slides
new slides you can get there you can
download them from there do whatever you
want it's there my Twitter is that Shawn
is well you can follow me over there
whenever it is a video I definitely put
a twit out there saying that this video
is out my email is Shawn at cloud range
of net please email me I'll try to get
to you as much as possible or as soon as
possible I'm still following and
catching up if you want to connect on
LinkedIn that's where I am and let's
connect and have a chat thank you for
viewing and please like the videos on
YouTube I mean it's definitely nice to
know that people are liking the videos
pass any comments you know if you have
any any ideas or if you want things to
be done a different way definitely let
me know but to like the videos it helps
a lot I like knowing that people are
liking the videos and things are working
out and definitely if you pass your
exams if you have 80 big changes with
clouds that you're having in your
organization I always like hearing
stories definitely let me know
challenges you faced things you have
done cool things that are coming out of
this training for you if you're passing
the exam and as such alright or it guys
thank you for viewing and I will
definitely see you in the next session