1
00:00:01,040 --> 00:00:04,140
Let's go back to replicating servers.

2
00:00:04,140 --> 00:00:06,460
You wanted to do a test migration first,

3
00:00:06,460 --> 00:00:09,660
which again, is directly analogous to Azure Site Recovery.

4
00:00:09,660 --> 00:00:12,840
You do that here from the replicating machines blade.

5
00:00:12,840 --> 00:00:17,040
You do a test migration, which would not turn off the source VM.

6
00:00:17,040 --> 00:00:19,900
It would create the VM in Azure,

7
00:00:19,900 --> 00:00:23,920
but then you could clean up or delete that VM in Azure with

8
00:00:23,920 --> 00:00:27,050
one command using Clean up test migration,

9
00:00:27,050 --> 00:00:28,560
which I think is pretty cool.

10
00:00:28,560 --> 00:00:30,780
If you're familiar with Azure Site Recovery,

11
00:00:30,780 --> 00:00:31,960
you see a lot here,

12
00:00:31,960 --> 00:00:37,190
so I would make an educated hypothesis that Azure Migrate Server Migration

13
00:00:37,190 --> 00:00:41,940
is indeed using a lot of the ASR bits under the hood.

14
00:00:41,940 --> 00:00:44,670
So we've got a migration taking place here.

15
00:00:44,670 --> 00:00:48,110
Remember that all of the storage is synchronized,

16
00:00:48,110 --> 00:00:50,700
so it's not like we've got a big network hit.

17
00:00:50,700 --> 00:00:52,590
I think the big latency we see,

18
00:00:52,590 --> 00:00:55,840
let's actually dip into the deployment details here,

19
00:00:55,840 --> 00:00:59,480
is a prereq check shutting down the source VM,

20
00:00:59,480 --> 00:01:00,720
so that was successful.

21
00:01:00,720 --> 00:01:04,600
If we come back to Hyper‑V virtual machine,

22
00:01:04,600 --> 00:01:08,540
core1 is turned off, preparing for failover,

23
00:01:08,540 --> 00:01:13,070
start failover, and then ultimately, start the replica virtual machine.

24
00:01:13,070 --> 00:01:16,290
And we can expect that once the failover completes and

25
00:01:16,290 --> 00:01:18,540
we start the replica virtual machine,

26
00:01:18,540 --> 00:01:22,640
we'll then have this core1 machine running as an Azure VM,

27
00:01:22,640 --> 00:01:25,340
and then we're free to archive, decommission,

28
00:01:25,340 --> 00:01:31,840
delete, whatever it is that we need to do with our local on‑premises VM.

29
00:01:31,840 --> 00:01:34,670
And replication also would then stop.

30
00:01:34,670 --> 00:01:37,850
It looks like it just finished now as we were waiting.

31
00:01:37,850 --> 00:01:39,040
Good deal.

32
00:01:39,040 --> 00:01:44,040
Let me head on over to the Virtual machines blade in another browser tab,

33
00:01:44,040 --> 00:01:47,840
and there we have our core1 virtual machine up and running.

34
00:01:47,840 --> 00:01:53,740
It looks like the virtual machine agent status isn't ready.

35
00:01:53,740 --> 00:01:57,690
Well that makes sense because it's a newly deployed new virtual machine.

36
00:01:57,690 --> 00:01:58,880
All of its size,

37
00:01:58,880 --> 00:02:04,040
all of its properties have come via that assessment process that we saw before.

38
00:02:04,040 --> 00:02:05,270
Let's close out of here.

39
00:02:05,270 --> 00:02:11,540
Let's go back to Azure Migrate and go back to Servers, databases, and web apps.

40
00:02:11,540 --> 00:02:12,660
Do a hard refresh.

41
00:02:12,660 --> 00:02:16,140
It may take a little while for the portal to update status.

42
00:02:16,140 --> 00:02:18,080
We should see Migrated servers.

43
00:02:18,080 --> 00:02:21,750
This should go to a one before too long, and there you have it.

44
00:02:21,750 --> 00:02:29,000
Hopefully you have a much clearer picture of the end‑to‑end with Azure Migrate Server Migration.