Hello and welcome to lab number 11
in this lab. We will be migrating virtual machines.
So we'll get all the configuration details taken care of. And then we will
see what's involved in moving, eh?
Of'em from one host to another
or from one day to store to another
switching the host and the day of store at the same time.
So let me get logged into the environment.
Okay? So our first task
will be to change simply the data store
so I can select any of'em that I wish.
we know that all these V ems air on this particular host, The other host that I have available here does not have any of'em is yet,
but I can click the summary tab
and see where my storage is. So it's not a local
effectively. All these
the ems around that same storage.
But I want to migrate this to a different data store so I can right click
and simply select Migrate
Noticed that change data stores My only option.
There's two reasons for that. First, is that we don't have the emotion enabled
on this host yet. Will do that and just a little bit.
And we can't change the host and the day store at the same time.
Unless the V M is powered off,
there's only so much you can do
while of'em is powered on
changing day store. No problem.
click next and pick our New Days store.
I've got another local disc here that's got plenty of storage left. Salt will choose this one.
And as I mentioned before, when you migrate or cloning machine, you can change the disc format at this point.
And this is a really handy feature
because basically, you don't have to live with a decision. If you If you did a thin provisioning and you really wish you would have done thick or the other way around,
you could move the machine around
to a data store and move it back to the original data store and change the format in the process.
So I'll go ahead and pick my my new disc.
I get my summary screen
and we'll start the process.
So since this is one local disc to another, this actually goes pretty quick.
trying to migrate a larger machine
and you were doing it from
local disc to a network attached storage device.
Then the process would take considerably longer. But when we go from one disc to another
within the same host
the transfer of the files is much more quick. Okay, so the migration is completed.
Now, we need to verify that
all of our disks are on
removed for me. A *** one TSX too.
So click my 1st 1 I can see that
hard. Just one is only a *** too
are just too. Also any SX two
and hard. Just three is on the SX two,
if you notice, though, showing my storage is still on the SX one for some reason,
that is because of my CD. Rahm Dr.
It was pointing to a nice o phile.
And because of that, it's still bound to the other storage.
So what I need to do
this is set to a client device.
And now this won't be bound any longer to the *** I
So go ahead and click. Okay.
You'll notice. That s ex I r. Sorry. Yes. X one has now gone away
now everything is fully attached to
is to examine the host
to make sure that we've got a
VM Colonel pour configured for the motion
so I can go to my host
configuration tab networking.
And I already have my standard switch.
So I'm going, Teoh, have a look at its properties.
And what I'm most interested in
is the manager network
of emotion and I p storage.
So I'll click at it for this
and make sure that the V motion check box is checked.
We also have the option for
fault, tolerance, logging and management traffic.
I want to make sure that I've got the motion there.
Now we need to look a little bit more at the host.
What we're interested in here
is CPU compatibility between the two hosts.
As we conceive, our our first host
CPU is for 2.6 98 gigahertz Intel core I seven
and then I look at the summary tab for the other host
and I see that it's the same
so I shouldn't have any problems
migrate of'em between
these two hosts. They appear to be compatible. Okay, so we'll close the minimize that window. For now.
Our next task is to make sure that the virtual machine itself
can meet the requirements for the emotion.
So when seven is the Vienna, I'm going to be migrating.
I need to go to the edit settings
And the first thing I need to check is that my CD is set to client device.
And if you recall, I changed this earlier
Previously was it was connected to A S O phile.
I need to make sure it's a client device
in order to be able to cleanly move it
host to another one day store to another.
Okay. Next. I need to
check a couple other things. Look at my network adapter.
and that should be fine for transferring to the other host.
Other things I need to consider here is the raw device mapping.
I had set this up in a previous lab.
but we don't want to have that
thatjust if when that disk is still in existence,
it may cause problems with with the emotion. So we're gonna have to remove that
and we can say remove from virtual machine and delete files on disk. So I don't need that
storage right now. I'm gonna go ahead and take that away.
Next thing we want to check is
whether or not a any affinity settings are set for the CPU.
So we'll go to the resource is tab
and select Advanced CPU.
And under scheduling affinity, we don't have any
affinity settings here.
We can tell the V m, for instance, to favor one CPU
over another. I've got eight available and I can tell it, you know, I wanted to use ah, the even numbered CPU
and then set another VM to use 135 and seven
So we don't have any settings here, which is good. That's what we want.
Go ahead and click. Okay,
Now I'll verify the settings for my second VM.
It's all right. Click at its settings.
I've got no affinity settings.
Underneath the resource is tab advanced CPU.
My seedy Ron drivers set to client of ice.
I don't have any rod device map ings That shouldn't
cause me any troubles.
Oh, that looks good.
Now what? I'd like to do is
Window seven Clone, too.
Two mice. Other host.
and I can change the host or the data store. We already changed the data store earlier, so this time we'll change the host
and I'll pick my second host
and look what happens. I get a bunch of messages,
so this is very likely to happen,
during initial attempts to do a migration.
the sphere is checking to make sure that there's compatibility and all the parameters are set up correctly
to migrate between hosts.
So let's look at our messages here
saying it's unable to access the file.
it thinks all the storage is
and it's having trouble accessing some of these files.
So I'll need to address these items one by one, and we'll get the problem's fixed.
So the problem appears to be that
this V M is not on shared storage.
So I'm gonna go ahead and cancel,
and what we need to do is migrate the data store
storage that both hosts can see, which is the NFS partition.
So this just goes to show how even
exercises can sometimes run into problems. This is a pretty typical thing that you might see
as it has a V Center administrator.
So we'll select Migrate.
I want to change the data store
and I'm going to pick
as my date of store. I know that that is shared
between the two hosts.
Go ahead and click next,
and that will begin.
This will take a little while to run because it's going over the network incident from disk to disk, but should still be fairly quick.
And it looks like we have some troubles with our other VM here.
Let's see what the air messages.
Virtual machine CPU usage. OK, so CPU usage went went fairly high. Looks like the
the V M actually is no longer running.
Like my console open here.
Oh, I see what's happening.
If I clear this alarm, you can see the little red diamond will go away. We can see that it is actually
running just fine. It kind of blocks a little green triangle.
Minor minor hiccup. The CPU usage got high and the default alarm was triggered.
We will get into alarms
and how those air used in the later lab.
So I'll go ahead and close that counsel for now,
and we will come back once the
VM has been relocated. As I said, this will take
of course, depending on your network speed and size of the VM itself.
we were still only a 38%.
What I often like to do is look at the performance of my
virtual machine while this activity is going on.
So I've gone to my performance tab, Click the overview, and I've selected a real time instead of looking at a particular range. That way it refreshes every 20 seconds,
and I can see that my
balloon driver is doing a lot of work
I've got a fair amount of memory being utilized
a lot, a lot of disk activity, as you would expect and disc requests.
Let's also take a peek at the host and see what it's performance Looks like.
We can see we've got quite a bit of
during the initial stages of doing the V motion.
And then I could just hit the down arrow
to look at some of the other things. I'm looking at my data store.
Obviously, I'm writing a lot of data, so my my just late and see
will be affected by that to relate and see
and right Leighton. See.
any of these indicators and highlight that in the in the text or in the charter should say
from J A store will move down to look a disc.
Concede we've got a lot of disk activity,
And you know what? When I click one of these that that item gets highlighted to make it easier to pick out,
I can also look at my network activity. Since this
migration is going over the network, I would expect to see a lot more
Storage adapter itself,
in the overall system
so we'll go into the performance
in more detail later.
I just want to touch on that While we're waiting for the migration to complete