Lab 11 Part 1 - Migrating virtual machines

Video Activity

Lab 11 part 1. Migrating virtual machines This lesson discusses migrating virtual machines. In this lesson, participants learn step by step instructions in a lab-based class on how to do the following: Move a VM from one host to another Move a VM from one data store to another Switching the host and the data store at the same time

Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
14 hours 13 minutes
Difficulty
Intermediate
CEU/CPE
20
Video Description

Lab 11 part 1. Migrating virtual machines This lesson discusses migrating virtual machines. In this lesson, participants learn step by step instructions in a lab-based class on how to do the following:

  • Move a VM from one host to another

  • Move a VM from one data store to another

  • Switching the host and the data store at the same time

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