Okay, welcome to part three of Module seven, Lesson three. Now we're talking about storage of emotion, so this is the ability to move the PM's files from one day to store to another. While the BM is running,
we'll also talk about enhanced the motion in just a moment.
But there's lots of good reasons why you'd want to do a storage the motion action,
for instance. You might need to do maintenance or reconfiguration on your storage devices.
Maybe you're adding more disks or swapping out lower capacity discs for higher capacity discs.
So this gives you the option to
move all the VM storage files to another place while you work on on this one over here and then you could move things back later.
Also, low balancing is a non option.
automatically with ah, storage distributed resource scheduler STRS.
We don't really have a lab for that,
but it is a possibility. Or you can manually load balance and you would as an administrator, you'd be looking at your data stores to see which ones are getting very full. Which ones have some capacity and you could move some things around as needed to balance everything out.
It's not only about the storage, though, you might do load balancing based on the actual Io performance of those different data stores as well.
one day a store that has faster discs than another, for instance.
So you you might want to put your most critical applications on the faster data store
and things that are a little bit less critical on the one that's a little slower. So you do have those kinds of options
that kind of ties in with the idea of storage tearing.
I could have storage that's using S S D, which is the fastest option,
and that might be for my database servers and things that have a lot of transactions per second.
And then I might have some fast disk for Web servers or application servers, and then I might have some less expensive, slower disk for general purpose file servers and things of that nature.
So having those different storage tears gives you the ability to prioritize
the placement of your VMS based on the performance of the underlying data store
and a nice thing about storage. The motion is that we don't have
any restrictions on the storage type between the source and destination data stores.
I can transfer files from Manifest I scuzzy
from ice cosy to SSD at any combination of those different storage technologies.
very flexible neck in that case.
So as far as the way this actually works,
the s an emotion. That's another way of saying storage the motion emotional, easier
that gets initiated,
then the VM Colonel data mover,
which is a functionality within the VM Colonel Hyper visor. This actually starts copying data from the source data store to the destination data store.
Once that process is as underway, a new V M process starts up
the mirror driver can then copy any new changes to the disk
that would have gone to the source data store. Now, those
operations are mirrored to the destination data store.
So as the day is being copied over and new things are happening with the V m. The mirror drivers sending those new data right requests to the destination data store so that it becomes synchronized with what the V M is doing
on the destination storage.
date has been copied over, and the mirror driver has done its last bits of copying itself.
Then the destination VM process can then be enacted or enabled so that users canal access the PM on its new storage area.
This is all transparent to the users, of course,
with the exception of a very tiny
performance hit that you'll take while this is actually happening.
Now we have the concept of enhanced of emotion.
This is combining the Motion and SP motion into one operation. So Aiken,
from one day store to another and change hosts all of one time. There's a really wonderful feature.
I also I don't need shared storage, which is a nice limitation, or I shouldn't say that's a nice limitation. It's a nice way to get around the limitation that it be motion normally has where you have to have
If I do enhance the motion, I don't need that. So as long as both hosts can access
as long as both hosts have access to some storage that can hold the VM,
then I could move the PM's registration from one host to another and its data store at the same time in one operation.
These do need to be on the same later to network as we see here
in some of our requirements for enhanced the motion.
Both the hosts have to manage by the same be center, which makes sense
they have to be the same data center, which also makes sense.
You think about some of the limitations from doing things from one data center to another.
Same layer to network must exist between those two hosts
and distributive resource. Get scheduler and storage distributors. Distributed Resource Scheduler
enhanced the motion automatically. This is a manual process.
Otherwise, DRS and SDRs could move the EMS and storage dynamically as required by changing conditions. But in this case, for hands free motion, it's something you do manually.
So up to two enhanced. The emotions can happen at the same time per host.
And if you have multiple interface cards
between your different hosts enhanced, the motion can spread out the traffic between multiple knicks in order to make the process more efficient and take last time.
So, in any case, when you're doing the storage, the motion or enhanced the motion, you have to make sure that
that you have some coordination with administrators and users
because there will be some potential performance problems
that might get noticed depending on what the application does.
have some agreement out of time that you know that you've got the available storage and that
all the other requirements are met so that you don't have a failure in the middle
and that have to regroup and try to do this another time.
Okay, so we talked about the benefits of storage. The motion went over the steps of what actually happens
when the SP motion are When you ask, the motion is initiated
that we looked at. What enhanced the motion offers us again storage and host being changed the same time
with some of the requirements listed here.
All right, so let's go ahead and do lab number 11
in this lab. You'll you'll see what migrating a machine looks like With SP Motion.
You'll create a virtual switch with Of'em Colonel Port
Poor Group for the motion migration. You'll make sure that your host meet the requirements.
Make sure that your V EMS meet the requirements
and then you'll do the,
uh, the the motion on a share data store.
And then move a of'em to a private data store by doing a storage the motion
and you'll do a little bit of clean up for the next lab.
All right, Thank you.