1 00:00:00,100 --> 00:00:01,569 So let's go into DMS 2 00:00:01,569 --> 00:00:04,059 to see how a database migration would work. 3 00:00:04,059 --> 00:00:06,610 We obviously do not have a source in a target database, 4 00:00:06,610 --> 00:00:08,880 so we will not be able to do it entirely, 5 00:00:08,880 --> 00:00:09,970 but it's good to see the options 6 00:00:09,970 --> 00:00:12,070 just to cement what we just learned. 7 00:00:12,070 --> 00:00:16,058 So we need to name our replication, so our FirstReplication, 8 00:00:16,058 --> 00:00:17,920 and then in the description we will not put it. 9 00:00:17,920 --> 00:00:20,680 The instance class which represents the EC2 instance class 10 00:00:20,680 --> 00:00:23,870 that is going to be pulling the data from targets 11 00:00:23,870 --> 00:00:27,350 all the way from the source to the target, 12 00:00:27,350 --> 00:00:29,750 and as we can see we can, from a t2.micro 13 00:00:29,750 --> 00:00:33,800 all the way to some larger instance, such as r4.8xlarge. 14 00:00:33,800 --> 00:00:36,530 So the idea it that if you have a big source database 15 00:00:36,530 --> 00:00:38,520 you may want to have a big instance class in the middle 16 00:00:38,520 --> 00:00:42,350 to perform all the replication continuously fast enough. 17 00:00:42,350 --> 00:00:45,060 Then the engine version for DMS that we want to use. 18 00:00:45,060 --> 00:00:46,920 How much storage is going to be on that instance, 19 00:00:46,920 --> 00:00:48,430 because it needs to buffer 20 00:00:48,430 --> 00:00:50,310 and write some log files and so on, 21 00:00:50,310 --> 00:00:52,440 so maybe you want to have a big storage 22 00:00:52,440 --> 00:00:54,200 if you have a big source database. 23 00:00:54,200 --> 00:00:56,350 A VPC to deploy this database in, 24 00:00:56,350 --> 00:00:59,290 and we can be fully resilient by choosing Multi AZ, 25 00:00:59,290 --> 00:01:01,050 in which case we have a Multi AZ deployment 26 00:01:01,050 --> 00:01:02,273 and we'll have a primary instance in one AZ 27 00:01:02,273 --> 00:01:04,870 and a standby instance in another AZ. 28 00:01:04,870 --> 00:01:06,750 So that makes DMS a Multi AZ service 29 00:01:06,750 --> 00:01:09,780 that is going to be fault tolerant and highly available. 30 00:01:09,780 --> 00:01:13,110 And do we want our DMS instance to be publicly available, 31 00:01:13,110 --> 00:01:16,120 or do we want it to be privately available, okay? 32 00:01:16,120 --> 00:01:18,580 Then we have advanced security and network configuration 33 00:01:18,580 --> 00:01:20,020 where we can choose our subnet group, 34 00:01:20,020 --> 00:01:21,620 we can choose a preferred AZ, 35 00:01:21,620 --> 00:01:23,220 the VPC security groups and so on, 36 00:01:23,220 --> 00:01:25,150 and a KMS key for encryption. 37 00:01:25,150 --> 00:01:26,680 As well as a maintenance hour 38 00:01:26,680 --> 00:01:30,870 in case we need to perform updates to our DMS instance. 39 00:01:30,870 --> 00:01:32,240 And then we go ahead and click on Create, 40 00:01:32,240 --> 00:01:34,540 and we would have our first instance. 41 00:01:34,540 --> 00:01:35,880 Obviously, this will cost you money 42 00:01:35,880 --> 00:01:38,460 if you click on Create, so I will not do this. 43 00:01:38,460 --> 00:01:40,870 And then finally, once everything is done, 44 00:01:40,870 --> 00:01:42,930 you can create a database migration task, 45 00:01:42,930 --> 00:01:45,100 and you would go ahead and create this task. 46 00:01:45,100 --> 00:01:46,477 So we will say MyTask, 47 00:01:48,260 --> 00:01:49,950 and we need to choose a replication instance 48 00:01:49,950 --> 00:01:52,840 that we would have created in the past section. 49 00:01:52,840 --> 00:01:54,810 So choose a database source endpoint. 50 00:01:54,810 --> 00:01:57,380 So for this we would go to the Endpoint tab, 51 00:01:57,380 --> 00:01:59,000 and here we would be able to define 52 00:01:59,000 --> 00:02:01,090 all the source and target endpoints. 53 00:02:01,090 --> 00:02:03,180 So for a source endpoint and a target endpoint 54 00:02:03,180 --> 00:02:04,560 we could choose an RDS DB instance 55 00:02:04,560 --> 00:02:06,840 or enter some information directly. 56 00:02:06,840 --> 00:02:08,389 And for the source we can see 57 00:02:08,389 --> 00:02:10,139 all the technologies that are supported. 58 00:02:10,139 --> 00:02:12,090 Same for the target, all the technologies 59 00:02:12,090 --> 00:02:13,460 that are supported right here. 60 00:02:13,460 --> 00:02:14,700 Makes sense, right? 61 00:02:14,700 --> 00:02:16,450 So we'll say for example, okay, 62 00:02:16,450 --> 00:02:19,020 our first instance is going to be an oracle, 63 00:02:19,020 --> 00:02:20,683 and then we'll say MyOracle. 64 00:02:21,570 --> 00:02:23,650 And obviously we would need to enter some information 65 00:02:23,650 --> 00:02:25,190 such as the server name, the port, 66 00:02:25,190 --> 00:02:26,120 the username, the password 67 00:02:26,120 --> 00:02:28,620 that allows us to start getting into our support database 68 00:02:28,620 --> 00:02:30,080 to perform the replication. 69 00:02:30,080 --> 00:02:32,230 Some endpoint specific settings if we need to, 70 00:02:32,230 --> 00:02:33,610 KMS master key for encryption, 71 00:02:33,610 --> 00:02:36,320 and Test to connection to make sure it works. 72 00:02:36,320 --> 00:02:39,680 We could create a source and a target endpoint. 73 00:02:39,680 --> 00:02:42,000 So back into our migration task now, 74 00:02:42,000 --> 00:02:44,620 we would select that source and the targets, 75 00:02:44,620 --> 00:02:46,640 then we would want to migrate existing data, 76 00:02:46,640 --> 00:02:48,860 and maybe do some replication for ongoing changes, 77 00:02:48,860 --> 00:02:51,840 which is CDC for change data capture. 78 00:02:51,840 --> 00:02:53,040 And then we would have more options, 79 00:02:53,040 --> 00:02:54,500 but we're not going to set them up. 80 00:02:54,500 --> 00:02:55,990 And the idea is that when you're done, 81 00:02:55,990 --> 00:02:57,760 you would create the task. 82 00:02:57,760 --> 00:02:58,593 Now you should remember 83 00:02:58,593 --> 00:03:01,810 that if the source database endpoint 84 00:03:01,810 --> 00:03:04,220 is different than the target database endpoint, 85 00:03:04,220 --> 00:03:06,990 then it would internally use SCT, 86 00:03:06,990 --> 00:03:08,440 for Schema Conversion Tool, 87 00:03:08,440 --> 00:03:10,510 to make sure that the data at the source 88 00:03:10,510 --> 00:03:11,680 is going to be compatible, 89 00:03:11,680 --> 00:03:12,930 and transforming to the right format 90 00:03:12,930 --> 00:03:14,960 for the data at a target. 91 00:03:14,960 --> 00:03:15,890 So that's it for DMS. 92 00:03:15,890 --> 00:03:17,860 Hope you see you'll have two databases to play with. 93 00:03:17,860 --> 00:03:19,120 But you get the idea, 94 00:03:19,120 --> 00:03:21,070 and I will see you in the next lecture.