MySQL Database Service Webinar: Upgrading from on-premise MySQL to MDS

Frédéric Descamps
Community Manager
MySQL
September 2020
MySQL Webinar Series
Migrate MySQL from on-premise to MDS
1 / 92

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purpose only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied up in
making purchasing decisions. The development, release, timing and pricing of any features
or functionality described for Oracle´s product may change and remains at the sole
discretion of Oracle Corporation.
Copyright @ 2020 Oracle and/or its affiliates.
2 / 92

Who am I ?
about.me/lefred
3 / 92

Frédéric Descamps
@lefred
MySQL Evangelist
Managing MySQL since 3.20
devops believer
living in Belgium
h ps://lefred.be
4 / 92

What do we need ?
Migrating to MySQL Database Service
5 / 92

Requirements
a running MySQL Server
6 / 92

Requirements
mine is running 8.0 and can access Internet
7 / 92

Requirements
an OCI account
8 / 92

Requirements
an OCI account
you can get a free trial on h ps://www.oracle.com/mysql/
9 / 92

Requirements
an OCI account
you can get a free trial on h ps://www.oracle.com/mysql/
10 /
92

The Plan
11 /
92

The Plan
. create a VCN with two subnets, the public and the private one
12 /
92

The Plan
. create a MDS instance
13 /
92

The Plan
. create a VPN
14 /
92

The Plan
. create a VPN
. create an Object Storage Bucket
15 /
92

The Plan
. create a VPN
. dump the data to be loaded in MDS
16 /
92

The Plan
. create a VPN
. load the data in MDS
17 /
92

The Plan
. create a VPN
. load the data in MDS
. create an in-bound replication channel in MDS
18 /
92

Architecture
19 /
92

on premise MySQL instance
OpenVPN client with a static ip:
172.27232.134
MySQL Shell (>= 8.0.21)
Architecture - on-premise
20 /
92

one VCN (10.0.0.0/16)
one Internet Gateway
two subnets
one public (10.0.0.0/24)
on private (10.0.1.0/24)
one OpenVPN Server Instance
one MDS Instance
In-bound replication channel
Architecture - on OCI
21 /
92

Object Storage
Architecture - on OCI (2)
22 /
92

Virtual Cloud Network
23 /
92

We create a VCN for
10.0.0.0/16 using the
OCI Dashboard
Virtual Cloud Network
24 /
92

Virtual Cloud Network (2)
25 /
92

Subnets
We create 2 subnets: 1 public and 1 private:
26 /
92

Range: 10.0.0.0/24
Instances in this
subnet can be
reachable via a public
IP
Subnet - Public
27 /
92

Subnet - Public (2)
Don't forget to set it as public:
28 /
92

Range: 10.0.1.0/24
Instances in this
subnet cannot be
addressed from the
Internet
Subnet - Private (3)
29 /
92

Subnet - Public (4)
Don't forget to set it as private:
30 /
92

Subnet - Summary (5)
31 /
92

MDS Instance
32 /
92

Let's create a MySQL
instance
CLOUD
MDS Instance
33 /
92

MDS Instance (2)
34 /
92

MDS Instance (3)
35 /
92

MDS Instance (4)
36 /
92

MDS Instance (5)
37 /
92

MDS Instance (6)
38 /
92

VPN
39 /
92

Let's create a VPN
using OCI's dashboard
VPN
40 /
92

Yamaha
Cisco
Libreswan
Fortinet
NEC
WatchGuard
Juniper
Furukawa
Check Point
Palo Alto
Other
VPN - CPE Vendors list (2)
41 /
92

VPN - OpenVPN (3)
42 /
92

VPN - OpenVPN (4)
43 /
92

The deployment is made using Terraform.
VPN - OpenVPN (5)
44 /
92

A login and a password must be provided to
be used OpenVPN's admin interface.
VPN - OpenVPN (6)
45 /
92

The instance must be located in the Public
Subnet.
VPN - OpenVPN (7)
46 /
92

The information to connect to the VPN
admin interface is shown in the log of that
stack deployment
VPN - OpenVPN (8)
47 /
92

VPN - OpenVPN con guration (9)
48 /
92

setup 2 networks:
dynamic
static
use routing
add the VCN
Subnets
49 /
92

We create a dedicate user
50 /
92

assigned static IP
use routing
51 /
92

VPN - OpenVPN ge ing the certi cate (13)
52 /
92

VPN - OpenVPN client on-premise (14)
We need to install OpenVPN on the MySQL server on-premise:
$ sudo yum install -y openvpn
We put the client.ovpn le we downloaded as /etc/openvpn/client/client.conf.
And we start the VPN client:
$ sudo systemctl status openvpn-client@client
Enter Auth Username: lefred
Enter Auth Password: ******
53 /
92

VPN - OpenVPN client on-premise (14)
54 /
92

Object Storage
55 /
92

We use OCI's Object
Storage to migrate the
data to the Cloud
Object Storage
56 /
92

Object Storage (2)
And we create a bucket:
57 /
92

Object Storage (3)
58 /
92

OCI Config File
59 /
92

OCI Con g File
We need an OCI con g le to use Object Storage with MySQL Shell
[DEFAULT]
user=ocid1.user.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ngerprint=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
key_ le=/home/lefred/oci_api_key.pem
tenancy=ocid1.tenancy.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
compartment=ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
region=us-ashburn-1
60 /
92

OCI Con g File
We need an OCI con g le to use Object Storage with MySQL Shell
[DEFAULT]
user=ocid1.user.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ngerprint=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
key_ le=/home/lefred/oci_api_key.pem
tenancy=ocid1.tenancy.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
compartment=ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
region=us-ashburn-1
all ocids can be copied from the OCI's dashboard
61 /
92

GTID's
62 /
92

GTID check
On the on-premise server, GTID's must be enabled to replicate to MDS.
Let's check it:
on-premise mysql> select @@gtid_mode;
+-------------+
| @@gtid_mode |
+-------------+
| OFF |
+-------------+
1 row in set (0.00 sec)
63 /
92

GTID check
On the on-premise server, GTID's must be enabled to replicate to MDS.
Let's check it:
+-------------+
| @@gtid_mode |
+-------------+
| OFF |
+-------------+
1 row in set (0.00 sec)
As GTID is disabled, we need to enable it.
64 /
92

Enabling GTID
To enable GTID without restarting MySQL, we can proceed like this:
on-premise mysql> SET PERSIST server_id=1;
on-premise mysql> SET PERSIST enforce_gtid_consistency=true;
on-premise mysql> SET PERSIST gtid_mode=off_permissive;
on-premise mysql> SET PERSIST gtid_mode=on_permissive;
on-premise mysql> SET PERSIST gtid_mode=on;
65 /
92

Enabling GTID
To enable GTID without restarting MySQL, we can proceed like this:
on-premise mysql> SET PERSIST server_id=1;
on-premise mysql> SET PERSIST enforce_gtid_consistency=true;
on-premise mysql> SET PERSIST gtid_mode=off_permissive;
on-premise mysql> SET PERSIST gtid_mode=on_permissive;
on-premise mysql> SET PERSIST gtid_mode=on;
And now verify:
+-------------+
| @@gtid_mode |
+-------------+
| ON |
+-------------+
66 /
92

Routing & Security
67 /
92

Routing
We need to add some routing rules to our VCN to route to our OpenVPN client.
68 /
92

We need to route the tra c for the VPN static
range (172.27.232.0/24) through the VPN
Server (10.0.0.11).
Routing (2)
69 /
92

Security List
We also need to allow access on the MySQL ports:
70 /
92

Security List (2)
71 /
92

Security List (3)
On the Default Security List for lefred_vcn we also need to allow connections to MySQL
ports. We will use them later to connect to the on-premise MySQL Server from our
Database S instance:
72 /
92

Dump & Load using MySQL Shell
73 /
92

Dumping the data
74 /
92

Dumping the data
75 /
92

Loading the data
76 /
92

Loading the data
77 /
92

We still need to set the GTID purged
information from when the dump was taken.
In MDS, this operation can be achieved
calling sys.set_gtid_purged().
The GTID executed value is in the le @.json.
Set GTID Purged
78 /
92

We still need to set the GTID purged
information from when the dump was taken.
In MDS, this operation can be achieved
calling sys.set_gtid_purged().
The GTID executed value is in the le @.json.
Set GTID Purged
79 /
92

In-bound Replication to MDS
80 /
92

Replication User Creation
A dedicated user for replication needs to be created on the on-premise MySQL instance:
mysql> CREATE USER 'repl'@'10.0.1.%'
IDENTIFIED BY 'C0mpl1c4t3d!Paddw0rd' REQUIRE SSL;
mysql> GRANT REPLICATION SLAVE ON *.* TO 'repl'@'10.0.1.%';
81 /
92

MDS Replication Channel
82 /
92

MDS Replication Channel (2)
And we follow the Channel Wizard Creation.
83 /
92

84 /
92

85 /
92

86 /
92

Conclusion
87 /
92

Now the Instance in MDS is kept updated with the data from
the on-premise MySQL.
When ready, you can move your complete workload to OCI,
stop the replication channel and decommissioned your on-
premise server.
Now relax and rely on MySQL Database Service!
Conclusion
88 /
92

MySQL Database Service Webinar: Upgrading from on-premise MySQL to MDS

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to MySQL Database Service Webinar: Upgrading from on-premise MySQL to MDS

Similar to MySQL Database Service Webinar: Upgrading from on-premise MySQL to MDS (20)

More from Frederic Descamps

More from Frederic Descamps (8)

Recently uploaded

Recently uploaded (20)

MySQL Database Service Webinar: Upgrading from on-premise MySQL to MDS