Microsoft Azure Training - [22] Azure Virtual Machines - Part 9 - Azure VM Storage (Exam 70-533) Video Lecture | Microsoft Azure: A-Z Guide - Database Management

hi everyone this is Shauna smell from
cloud Ranger and you're viewing the
Microsoft Azure training today is the
part 9 of azure virtual machines and
we're going to talk about vm storage now
before we start this I know we have come
a long way this is part 9 of virtual
machines because there was just a whole
lot to cover and these are stuff you are
going to do on a daily basis in your
production so I didn't spend quite a bit
of time on these virtual machines having
said that I did mention before that we
able to have separates you know sessions
on VMs storage I mean on a storage in
general but what I want to do in this
session is actually you know talk about
some storage stuff that we have just
been ignoring for now and that are
directly related to virtual machines so
this is not going to be a session on
storage accounts and storage in general
but some storage a staff on virtual
machines and I'm going to try to keep
this as brief as possible so let's get
started
so the first topic today is VM disk
caching so what happens on premise is
that you have your resources always
close to each other so you'd have a
server that's probably connected to your
Sun or mass or direct-attached storage
whatever but they're going to be very
close proximity with each other so for
example you're not going to have a
server sitting somewhere in your data
center or in your office and they'd have
the storage of the send totally on a
when link miles away you wouldn't do
that
but in Azure or in cloud there are
chances that they're certain I mean you
don't have to go like thousands of miles
apart but there are chances that the
resources are not going to be together
all in the same rack or in the same
cabinet or even in the same data center
facility it would still be in the same
location like for example is the US or
West US but they might not be very close
to each other so what Microsoft did is
like when you're creating a virtual
machine it has given some options for
disk caching so it basically says that
there's going to be some read and write
buffer and this read and write buffer is
going to be for both the operating
system disk and data disk
like you've known as your operating
system disk and data days they're very
well distinct from each other right and
this cache itself is actually located on
the physical server disk on the host
server so if your virtual machine is
created on a physical server there is
going to be some disks in there whereas
you know if the temporary drive is there
from our previous issues like every
virtual machine has a temporary drive
that's sitting on a physical disk on the
host server so this cache is actually in
the same location on the server so the
physical disk okay now I've got some
conflicted documentation on this but OS
disk cache settings can only be set
using PowerShell a data disc from
management portal and partial but it
seems like in the management portal
I do see a setting for OS disk caching
from the portal itself and not only from
PowerShell okay I'll show that to you
momentarily and the other thing I want
to talk about is that this caching can
be created or modified while the virtual
machine is being created or after the
virtual machine has been created this is
similar to a lot of other things we have
done you know in both scenarios while
the virtual machine is creating or later
and the default cache setting is read
and write so by default the cache
setting would be read and write for both
OS disk and data disk now frankly I have
never had to change the cache settings
for OS disk or data discs they are read
and write they're set for efficiency and
whatever the case is right unless you
have any very compelling reason that you
want to do that for the OS disk do it
but otherwise leave it alone because
that's probably the best setting that as
your has for you by default now with
your data disk
you know the default cache there might
be certain scenarios where you want to
make it only read-only or no caching
whatsoever and you know what when you
make domain controllers and look go
through there's your best practices to
make domain controllers you will see
that this cache setting plays a big role
in how your domain controller will
installed you know for example I do want
to get into much details about it for
example when you create a domain
controller they say that your active
directory in data sources volunteers and
all that should not be on your C Drive
it should actually be on a data disk
which is completely different from how
you might have made domain controllers
all your life really in as York they
want the data disk to have your Active
Directory database is located in there
and this is the best practice for
normally best practice is the safest way
to have a domain controller in a zero
and the reason behind that is exactly
cause of this cache setting the domain
controllers are not too friendly with
the cache that it is your has so you
probably want to keep this on a data
drive where the host caching is set to
none so there's no host question caching
whatsoever so you know Active Directory
stays same but there are situations
where you will do that but nevertheless
I have never seen a scenario where I had
to go and change the OS disk caching
however for data sure for the main
controllers this and that but for is
disk never so leave it alone if you have
to unless you have this very specific
configuration where you want to go and
change something
bring your operating system disk ok so
moving on I do have two partial command
let's hear one for the OS disk cache and
one for the data disk cache so the first
thing we do for example here is we get
hold of the VM object see range of VM
ones reserve one that's the virtual
machine named virtual machine name and
the service name and after we have got
the VM object this is the command let
you use and we have not used this
command late before set as your OS disk
so set as your OS disk with the switch
host caching read-only would actually go
and make the disk read-only caching if
you do not go and do this by default
it's read and write ok with your data
disk however we have used this command
late before
set as your data disk for creating data
discs or you know making modifications
to it but this time it's the same switch
host caching and we are going to make it
readwrite for DES your data disk so they
are pretty simple command let's here ok
so let's go through a quick demo
I want to show you how this is done in
the management poro so this is what I
was mentioning so if you come to your
virtual machine here see arrangers or
one I by the way I have this two virtual
machines already created basic virtual
machines really default settings anyways
so if I go to disks here I can see that
see Ranger zero zero one is attached
this disk is attached to see Ranger zero
one so I know this is the operating
system disk okay so I do have this edit
cash option here where you know that
this can be made to read one of your
read/write by default it's readwrite
like I mentioned for the host caching
for preference so this document a the
documentation where it says that you can
only change this setting for OS disk
from PowerShell is not really accurate
any longer you can actually do this from
power from management console okay and
if you wanted to have a data desk so for
example you attach it an empty disk to
this one so far we had always just put
for example five gigs here and we have
moved on but as you can see host cache
preference by default has no setting for
caching but you could change it to read
only and great right okay
before the documentation at one point
was that this was readwrite as well but
you leave this one is none and this is
what I use but I go with the default
settings all the time and this is the
setting you probably want for when
you're creating a domain controller as
well you do not want to host caching
preference on the data disc okay so
that's all that really there is to it
with host caching and now let's move on
to the next topic back onto our slides
we are going to start talking about disk
redundancy and we could talk about both
durability and performance now this is
something we are going to talk in
details in storage accounts when we go
through the storage sessions but I'm
gonna briefly touch this and just go
through this so you understand while
your virtual machine disks are located
if you actually are just here to watch
this video and you are not following
through the entire series of this
trainings that are you know that already
they are going to happen so there are
three tiers I mean I wouldn't call it
four tiers
there are three tiers for three good
reasons okay so this is your storage
account that your your disk is created
in the discourage account so when you
create your storage account you are
given that option that how do you want
your disks to be so the first one is
local redundant tier this is the default
one okay so by default what it's saying
is that each disk is replicated three
times in a given data center or facility
what it means is that in your own
previous systems we'll buy a server
you'll have rate right you will have
your disk geometry you'll have probably
mirrors you'll have red 0 raid 1 raid 5
mirror raid whatever and what do you do
is that basically you're trying to you
know prevent disk failures that's why
you have a durability of those disks and
for your operating system for example
you'd have red one mirror or whatever
now with a zero we have not done that so
far
and this is no different from your
on-premise virtual machines when you go
to create your virtual machines you just
give it some storage now underlying fan
or local disk you don't go and set the
geometry of that on the virtual machine
and it's similar
so in Azure we do not do rates but what
Azure does for you in the back end is
that when you have local redundant tier
it will have your data or each disk
replicated three times in a given data
center okay so if one of the disks fail
or you know whatever happens you still
have the data in that same data center
in two other locations
so that will ensure that breaking a task
is not going to be an issue but then
there might be some issues that you
might say that okay I don't want my data
to be in the same location or in the
same data center that's why we have the
zone redundant here so here each disk is
replicated three times across two or
more data centers however they're in the
same zone and the word zone I want you
to get used to this terminology
terminology because we call it location
or we call it region but when it comes
to storage
they call it zone but essentially it's
the same thing
so what like I mentioned in my previous
sessions that a single location might
have multiple data centers or facilities
where you have your resources so you
could have East us two which might have
five data centers they are in five
separate data centers but they're still
located in the same region same location
or same zone that's what we call it that
those terms are synonymous here so what
Microsoft will say there okay if
something happens to this data center if
you go through a zone redundant here
I'll make sure that a copy of your data
is actually there in another data center
in the same region so will it still be
an instance too but you'll have three
you know three locations or three or
more do you know Daughtry and more into
two or more data centers will have your
base data okay so which is pretty good
now
the next one is geo redundant tear and
this is chances are this is what you
might use in your production most of the
times because this happens to be the
most safest and I'll explain in a bit
why each disk is replicated three times
in the primary zone as well as three at
a remote zone so for example we go
create a virtual machine in a storage
account with geo redundant ear means
will not only have the three copies of
that disc in East us two but it will
randomly pick another location for
example West us or I don't know central
us or not us whatever another completely
different regional location and stored
three more copies with that so take a
guess what did this just address some of
you might have got this right away
people who are really veterans and you
know who have worked on systems for a
long time this actually basically takes
care of your disaster recovery or
this takes care of your dr scenario what
happens if California goes on the water
where does my data go so that's where
your data goes when you do geo redundant
is that you might be in West US and you
might have your primary data there but
chances are East you know when you are
in geo redundant here
you know the East u.s. probably has
three copies of that data as well so
this kid takes care of dr so in
production this might be something you
want to do now the next one is not
exactly a tear but it's dual redundant
read access means that your data is read
only in the secondary zone so your
primary zone will have read/write but
your secondary one will only be read one
day so you know again in dr scenario you
might want a situation where the data
that's located in the dr site or the
secondary site in as your terms or
secondary zone you want that to be only
read one lis so if there isn't damage
done to the data right damage done to a
data on the primary zone the you know
the secondary zone will be read access
one day so the damage over there will
not be done now I'm not gonna get into
details on how these are configured a
lot you know because we are going to
have a session dedicated to all of that
okay so but I do want to show you
something really really quick so if you
go to storage account new storage
account and quick create as you can see
when we create a storage account here
let's call it C Ranger software or
something like that and let's call it
East us - this is going to be my
location it gives you the replication
option that do you want to locally
return that you read and then zone recon
date so these are all your tears
remember these are the ones we have
talked about and this is how you set up
the storage account so anything that's
created in this storage account will end
up being end up being you know based on
the tier so then I will be located so
I'm gonna just keep this locally
redundant and I'm gonna click OK and you
can do similar thing with PowerShell but
I'm not going to go over all of that
right now ok so the next next thing I
want to talk about is disk redundancy
from a performance point of view and
this is entirely or based on AI ups and
disk I up so we have not talked about
this before but I did show you that site
before I am quite sure this is the URL
please pause the video and make sure you
have it these are the things you should
actually bookmark
because you will be referencing them
quite a bit and this data does change
quite a bit
well if with more previews coming to
general releases you will see this data
change quite a bit like for example this
was updated March 27th which is quite
recent 2015 at least when this video is
being recorded ok so here you can
actually see there was something I did
go touch before is the eye ops ok the
math.max eye ops and the amount of data
discs so this might be a document that's
familiar to you guys so what I want to
show you is that every single disk has
an eye ops of 500 per disk okay
input/output per second 500 so that's a
standard across Microsoft Azure that
every disk will have 500 now you could
have you know two disks over here like
data disks for example it'll be 2 into
500 ok so that means it's not saying
that it is going to be 1,000 it just
that each this will have 500 so you
might get a total of a thousand arms not
from single disk but both the disks this
is actually both the disks
we have a lot of confusion with that
where people will come in to me also
have a list large VM which is a three
and seems like you know there are eight
data disks I can attach to it good for
me and I have 8 x 500 so what is it like
I am I getting 4000 higher-ups from one
disk no you are not you are getting
still 500 per disk just how its
represented here
however I'll show you how to get more
apps in a bit now as you go down you'll
find out that there are other very
extent extensive series of data disks
with des series and D series where you
have you know these are only two days
you can put them but you know you can
have 3200 I apps from each desk and then
this can go you know it can get quite
crazy with the des series it's new
series of virtual machines that just
came out with ok
so I'm going to show you a nice trick to
see what's going on and how to increase
your a UPS okay it seems like we do have
a little bit of time I know this is
going a little bit out of scope but this
is something you will be doing in
production so give me a moment here okay
so I do have everything ready here so
like you notice that I had two virtual
machines created so I'm going to go to
sea Ranger zero zero one and I am on the
virtual machine
oh by the way Microsoft just released
the image for Server 2016
so I'm right now on a 2016 server you
could be very well on it 2012 r2
datacenter it does not matter what
server you want but this is actually a
2016 server it's a it's anyways it's an
evaluation copy it's a technical preview
it's not release released to the public
but you can use this from Israel okay so
I'm just using that over there so this
is the link you want to go and download
a tool called sequel IO so this is what
you are going to download and you
install this sequel IO tool it's a very
small tool does very basic things so
once you have installed that you go to
your counselor powershell whatever and
this is the location you want to go to
Program Files x86 sequel IO okay and in
here you'll actually see the tool sequel
IO dot exe okay so that's that one we
want to use anyway so what we have to do
is we're going to run this tool to
actually run some sort of a stress test
on the disk itself and to see that how
it performs I ops wise okay input
outputs per second and what we're going
to do is there are bunch of switches
here the K option specifies that it's
going to be a read/write so we are going
to do both read and write on that disk
- s means we would run the test for 60
seconds 60 seconds might be too much so
let's make it thirty seconds for us - oh
eight here Oh indicates the number of
iOS that can be outstanding in a single
thread so it actually creates multiple
threads to actually run this tests
and B option is actually the i/o block
size in kilobytes right so you know
eight would be like about 64 kilobytes
of the block size input/output block
size okay and what we want to do is we
are going to test file we're going to
run first a test on the C Drive so did
is this is the operating system drive
that we are going to run this on ok so
let's go ahead and run this test and
what we are expecting is well let's
first actually get there before we talk
about what are we expecting C Drive so
test ok in case in your if you are
wondering why disk you know all of a
sudden PowerShell is showing these
colors seems like it's a new feature
that's going to be on Server 2016 so
sequel i/o cannot be found okay so let's
see what happened here
I am pretty sure it's there sequel i/o
it's the full path - oh eight this is
something that might be used as a proof
of concept or this might be something
that can be used in a production to
actually run a test and see what kind of
helps you get there are applications
which are very particular about the
Disgaea ops so you have to remember that
so anyways this test is going to run for
like you know a few seconds I think 30
seconds in total and it's going to you
know come and give us the results so I'm
going to pause this video and come back
come back when the results are up okay
so I've ran the test few times I
actually means that - is 30 switch over
here but as you can see it came back
with the I ups it ran for 30 seconds by
default anyways it came back with 23,000
582 I opps I ran at the same time second
time it's pretty close so it's almost
easy to deduce from here is that it's on
your C Drive you are getting up to
24,000 miles per second okay so what we
had to do is that and this was on the C
Drive this was the primary disk drive
okay
what we are going to do is we are going
to attach a data disk an empty data disk
to this one okay and VHD is grayble to
called one data here and this is going
to be like five I'm not going to have
any caching down here let's add that
desk here okay that took few seconds to
create so we do have a data disk now
that's attached to see Rangers reserve
one okay
this one does to have the operating
system so this one is the desk so let's
come over here we will need to
initialize that disk so let's go to disk
management by default let's see okay so
it's showing up here this is the five
gigs disk we have attached so we can see
that okay so let's go ahead and create a
new simple volume on this one five gigs
let's call it the F Drive keep
everything normal the way it is chrome
finish should be up and running moment
early cancel I don't want to format the
disk it's formatting already it's very
small this should be done okay so it's
up and running so let's go over here and
you can see there's an F Drive that's
created it's nice and empty okay so
we're gonna run the test on this one so
let's go ahead clear this screen here so
we go to run the same command but this
time we're going to do this on the F
Drive because this is the data disk we
have attached okay so probably shouldn't
have cleared up the screen but okay
let's run this test so this test is now
going to go to F Drive and it's actually
going to create a data disk as you see
it created the data disk and it's doing
its thing so we'll come back after 30
seconds okay
thirty seconds over now you can look at
the data that came back here and you can
see it's 503 to 33 so it's only 500 I
ops per second when you attach a single
data disc this actually corresponds to
our our standard here's where you can
see that one database will go up to 500
okay so you could get a back 'some of
500 a ups from a single data disc and
this is actually a proof of that live on
how to check that 503 which is close to
500 so what happens if you actually want
a database to actually go more than 500
I ops just like for example we did our C
Drive
well the C Drive is already created
first so you do not know better
it had like something insane like 40
24,000 I believe apps so how do you get
your apps more than 500 by design it's
500 for a single disk so some of you
guys who actually do a lot of servers to
have server have been stuff the answer
to that is you take multiple disks and
create a rate okay so you will have like
a raid 5 for example you'll have a
higher I ups from there because you are
reading and writing at a much faster
speed then you would ideally have a
single speed with a single spindle right
this is how data is distributed on rate
so I'm not getting to the geometry of
how rates are but if you have actually
five disks kind of created in a pool of
disks and you represent that as a data
disc you do that so the way you do that
in a 0 and you might actually have to do
that for certain applications so for
example think about sequel the more I
ops you have the faster your data is
going to be accessed so chances are you
do not want one data disc with just 500
I ops
you probably want 5000 or even more like
50,000 on your AI ops but how do you do
that in a 0 we cannot obviously do raid
here well the way you do that is by
creating something that's part of Server
2012 and it is called well it was there
since 2012 it's called as your you know
storage spaces or disc spaces and I'm
going to show you how to do that with
three disks here
this is not a 2012 server it's a 2016
server it preview so I will try doing
that and this will be a nice experiment
okay
so let's actually delete this volume we
do not want this volume to be anything
to be done with this I'm good actually
in fact just make this offline at this
point okay so we have two disks I mean
we just have one data disk I'm going to
attach two more data discs to see Ranger
0:01 okay so it's going to be similar I
would just comp this Wow what do they
call this guy interesting let's go to
the storage let's try to find out what I
might have called it
not this one that's why you should
actually dammit appropriately
anyways so I called it one day the VHD
so this one I'll call to data VHD okay
just to give some consistent to data so
this will be five gigs you need them to
be all of same size so let me create the
other one as well and once all three are
created I'll come back okay so all disks
were created let's dismiss this so let's
go back to see Ranger zero zero one okay
just come over here you should see five
five five so we attached three data
disks and it's all here okay so what we
want to do is let's go to the server
manager in server manager by default
since Server 2012 I'm on Server 2016 but
you'll find similar it's same steps
you'll come over here and some of you
might already know this these are all
the disks that you have on this
operating system I basically want to go
to storage pools and I'll see primarily
all here and these are all the three
disks that are available to me so these
are the three data disks attached from
Monsieur I'm going to press on shift go
over here oops and select all of this
disks they have to be all of the same
capacity here right click on that and go
new storage pool so I'm going to create
a storage pool from these three data
disks click on next storage pool name
data pool whatever you want to name it
it's saying that how much do you want
allocation everything I'm going to keep
it default create so it's creating the
storage pool for me take a couple of
seconds and it's completed click on
close as you can see there's a pulldown
called data pool the primordial is gone
and these are the three disks that are
all part of the pool okay so the total
capacity now became well it's not gonna
be 15 it's 5:55 each it's 12.8
that's the total with the overhead so
come over here on the disks and this is
the seed right by the way so if you go
to this one well there is a D Drive so I
guess we have to create a new volume
here so create a new volume next
rescanned
second you know what I did not create a
virtual disk and so now that the storage
pool is created here I do need to create
a virtual disk so let's go ahead and do
that first so come back to a storage
pulls here and go to new virtual disk
actually harnessing it so this is why we
created the pool right this is where the
primer reel was I went at select at all
three created the storage pool now the
storage people showed up now under
virtual disks here we want to create a
virtual disk it's asking which pull do
you want this is the pool I want named
the virtual disk name we just call it
data storage layout we'll just do it
parity these are three options you have
simple bigger and parry I'll do a parity
over here or you know what I could do
data straps actual fist let's keep it
simple
I am going to keep this as fixed size
specify the size let's take it maximum
size that comes out of all three disks
Confirmation create so let it create the
virtual disk okay now it does give you
an option right after that do you want
to create a volume so we do not have to
jump to that volume page so I say okay
let's create a volume right after so
server and desk this is the disk we have
the size is 12 so it has some overhead
we will call it f drive again let's keep
everything the same confirmation create
took about ten seconds and now
technically we should have F Drive okay
so we had three disks five gigs each and
we have taken them and created a storage
pool using the built-in features with
Server 2012 onwards and we created a
storage space and we named it we create
a virtual disk and create a volume out
of that virtual disk and we call it F
Drive okay so this is no longer just a
regular data days because three data
disks combined together and it's a
simple volume now I want to run the same
test on this this is from our previous
one where it was 500 I ops and I'm going
to run the same test on this this time I
know this F Drive is not a regular
single data disc okay so let's go ahead
and run the test I'll come back after 30
seconds with the results okay so the
results are back look at this the I ops
actually jumped to 1,000 from the
previous where it was 500 so when it was
a single data disc that we connected to
the virtual machine by itself it could
not give us more than 500 I ops but we
three combined to one single storage
space or one single in point of storage
it actually increased the I ups so you
could add more disks to this and
increase the amount number of spindles
and technically you know increase your
apps to like some enormous you know
capability where if you have some
serious data that sequel server needs to
do so this is something you will be
doing with your virtual machines in
production in certain scenarios like
sequel exchange and stuff like that okay
and do remember that as your now has
premium storage and with premium storage
rather than the 500 apps you can
actually get a lot more I ops so if
you're building a sequel server you can
use premium storage and you can have the
DS size virtual machine connect to each
other and have a very nice hunky-dory
high capability sequel server
but this is more of increasing the
efficiency or IUP's of a single VM
attaching three data disks and creating
a storage space and doing all of that
funky stuff to increase your I apps to
increase performance so this goes back
to our disk redundancy and performance
aspect of as your virtual machine I know
this went a little bit out of topic but
this is what I am trying to provide a
value of hands-on production level you
know insights to what you need to do in
real life to do something like this
sequel there are more tools out there
from Microsoft
I like sequel IO because it's very basic
this tool helps me get the IUP's really
quick and this is good for a proof of
concept if you're you know demonstrating
something to your client internally or
externally so that's all there is to
disk redundancy the next thing I want to
talk about is as your files this is a
preview feature in 2015 right now at
least at the time when I'm recording
this it's a preview feature means
chances are this is not part or are
activated on your subscription the only
way you can actually play with this and
activate on your subscription is if you
go through your as your contact support
created ticket it's very easy actually
the way you do that is you come over
here let's go here Kluber and your ball
you see contact Microsoft support okay
you click on that and it creates a
ticket and it gives you a little forum
where you can create a ticket it gives
you a little place where you put the
description of the ticket with your if
you're running in as your trial in fact
pay-as-you-go I do not have any
technical support so make sure you
choose the billing support okay
part of billing support is enabling
preview features on your subscription by
default it's not a subscription that is
given to you that includes premium
storage as well premium storage and as
your files these are not released to
general audience yet so you might have
to you know do enable it on your
subscription opener to get into that
could take up to a day or two for that
to happen so you know pause the video
here come back later go
then create the ticket for us your files
for you know if you have to do this
hands-on and practice so what is your
files do as your files is basically an
SMB endpoint from an azure storage
account so that's the technical
mumbo-jumbo right what it is in basic
terms is that it lets your as you're a
storage account
act or kind of portray itself as a file
share you might see the benefits of this
in is your leg right away like where do
you store the files in your you know in
your on-premise today it's probably a
file share it's probably a file share on
your sand if you have this MP support or
your Nez or a file share server well you
could do the same over here with a
virtual machine create a data disk and
put all the ISO files on there for
example or your data tastes like you
know installation files for sequels
sharepoint exchange whatever or you can
use something like as your files what as
your files will do is it basically gives
you a endpoint which you can access
through files share okay so i'm going to
demonstrate this like in record speed
and i'm going to show you how this can
be done so let's go over here we already
have two virtual machines see Ranger 0 0
1 and 0 0 2 and I am going to create a
storage here
you know what I'm going to create a
totally different storage account for
this I'm going to call this actually I
did create something before yeah I have
a ranger software storage here right so
let's go in here let's go to the
containers there's no container there's
nothing going on it's just I think I
just created this to show you the
jewelry tendency and all that redundancy
ok but it's a basic storage account
where nothing else is going on
ok so it's called sea Ranger software so
I do have a little script here so the
name of the storage account is sea
Ranger software so the storage account
is the range of software you need the
storage account key okay so let's start
getting too much details on what this
kids are but for this example let's go
to manage keys
I'm gonna take the primary key so click
on this button it actually copies it so
it's a very nice handy nifty feature so
this is this is a special character key
that's only going to be known to you
it's very unique it almost almost acts
as a password and I'm going to create if
shared folder called I don't know my
software may be ok next time we'll
create an azure storage context which
will take two parameters one is the
storage account and the storage key so
this is storage account this key goes to
the new storage context so I'm going to
store that in here and with the new
storage context where I'm going to do is
I'm going to create a new storage share
as your storage share this is the
command lit that I want to show actually
for there's your files this is basically
going and saying that create my software
share on this storage context means in
this a storage account so let's not get
into too much details on this this is
the part I want you to concentrate that
basically new as your storage share it
creates the file share ok so let's go
ahead and run that that's it it actually
went it created that there is no way for
you to view that from here if you now go
over here like for example was to see
the containers and stuff over here this
it does not show this over here the only
place unfortunately you can see that is
in the preview portal so the way you go
to the preview portal is there's your
preview portal here I know we are not
working on the preview pearl much I'm
keeping us in the manage the management
portal but preview portal is going to be
Microsoft's pretty much de facto the new
portal so someday they are going to
completely you know get rid of this
portal and this is where it will be you
have a lot more capabilities on this
portal but on your exam there will be
both so you know I'm concentrating more
on the management but feel free to come
over here and explore you can do the
same things you do over here it's just
that it's separately or differently
organized and you will see that there
are certain things that are available
here that's not their own management
portal and there are still stuff that's
on management portal they did not bring
it
over here okay so let's go over here I
want to go to browse in browse I think I
need to close that go to browse these
are stuff I had done before I'm going to
go to scroll down to storage accounts
the storage account I want to go to you
see Ranger software once I'm at see
Ranger software I can actually see file
shares okay so let's create click on
file shares and you can see it actually
created a file share named my software
this is the stuff that we created okay
so the URL to that is pretty much the
Ranger software which is pretty much our
usual one if you remember from before
when we go over here and we have looked
into some of this when we were creating
the image we were working on the blob
the blob core to store our image and all
that but with this one if you if you see
right now it's actually file core so
this is the zero files
okay so let's copy that because I will
be requiring this information over here
so let's comment and piss this over here
the part that I will actually need is
this part see you ain't just software
software okay so the share is actually
created what I'm trying to demonstrate
right now is that how do you get to that
share so we have one of our virtual
machines here see Ranger zero one that
we were working with let's go ahead and
map that right so if I come over here
and I go to computer map a network drive
so I'm gonna call this for example
software so I'll just call it s over
here this is what we need we need this
guy so I'm going to put backslash
backslash
and I need a back slash over here so
converting this to UNC okay this is no
different from how you do this on
premise backslash backslash this is how
you connect to a file share server with
UNC so this is what you put for the
folder okay do you want to reconnect
that sign sure whatever you need to
connect using different credentials
right because you will need different
credentials so what's going to be the
username and password if this was a
domain you do your Echols or ACLs and
you do that here your account name is
going to be your storage account babe
see you Ranger software so let's go
ahead and do that
see Ranger software and your password is
going to be this long key that we had
got from your storage account this is
very unique to that storage account so
this becomes technically your password I
would remember my credentials click OK
and let's see if we can connect well we
just did so come to this PC and you see
that there is something called as well
it's not showing what it's called here
let's see if I can list this and make
this better it's an S Drive okay so this
is the S Drive we created you go in
there and this is pretty much this is
pretty much your shared folder so let's
create something over here you can put
anything over here this is how you can
upload information I'm calculate a test
document here I'm going to put this for
example sequel IO tool in here I'm going
to do this this is where you could
probably put your other ISO files for
sequel for your SharePoint so you have a
single location with no software repo so
let's go access that from C venture zero
- so this is a completely different you
know VM we haven't worked with yet map a
network dive map network drive I would
do similar thing over here as well I'm
just basically going through this double
process to show you that you know this
is nothing but if I'll share that
everybody can access well people you
give access to through this username and
password can have access to okay and
it's something new that's why it's still
it's still in preview it's something new
that Microsoft is doing and you know
chances are
information like on this might be on
your exams and you know this is very
handy thing in production so I'm already
using it in production for you know at
least destroying all my Zoar files and
stuff like that
so put this information here myron
scholes okay and voila this is where we
are so we are on see ranger zero to
server as you can see and this is the
information we have right here and see
Ranger zero one you can see it's also
information we have on this both servers
so it's basically nothing but a shared
folder that we can access from all the
virtual machines it's a perfect tool to
store stuff rather than speeding up an
interval machine to do that okay so
basically it's a file share on Azure on
a single storage account and that's what
it is they're a bunch of partial stuff
that you can do on that I don't want to
get into details on this right now but
there are stuff you can do there so I
think that pretty much wraps up today's
session it's not really a super long one
but there's a lot of hands-on value that
you can get out of this session stuff
that you will be doing in production
most likely so we will be doing a lot
more in storage sessions but this is
something that's very very related to
your virtual machines so I went a little
bit ahead I mean a little bit more you
know to do the sequel IO test those are
definitely not going to be there for
your exams
but that stress test or that little
performance test that we did over there
is something you'll be doing in
production and that's my goal to give
you some value out of these videos even
in your production as well okay so as
usual my training site is at Club Ranger
net forward slash as your training
YouTube channel is at cloud Ranger
Network follow me on Twitter at cloud
Ranger blog and you can always email me
Shawn at cloud Ranger dotnet and I will
be seeing you in your next session we
have one more small session for virtual
machines and I promise that that'll be
the last on virtual machines and we're
going to talk about virtual machine
monitoring it's not going to be a very
long session it's gonna be short session
nice and sweet to give you a wrap
but you know exam point of view on most
virtual machine stuff and then we'll go
to the next sessions okay so thank you
for viewing and I am good to see you in
the next session