In part 1 of the series about Point-in-Time Recovery in OCI MDS, we saw how to stream the binary log to Object Storage.

In this blog post, we will see how we can restore the data up to certain point.

The high level process is simple:

1. we need to restore the last backup just before the point we want to return to
2. find the last GTID that was executed in that backup (not 100% mandatory but can accelerate the process)
3. choose what is the objective:
   1. just skip one transaction (following transaction could depend on it)
   2. recover up to that transaction and skip all the following ones
4. replay the binary logs taking in consideration the chosen option of point 3

The scenario …

To setup point-in-time recovery for MDS using Object Storage, these are the prerequisites:

• a MDS instance running
• a backup plan (default)
• a compute instance
• an Object Storage Bucket

In this article, I won’t focus on how to create a MDS instance, a compute instance, enable backups and Object Storage Bucket, this is easy and there is already a lot of literature about them (you can also check several of my previous articles).

This is part 1 of the Point-in-Time Recovery in OCI MDS series. It’s only about streaming the binary logs to Object Store. In part 2, we will see how to use them and perform PITR.

Saving the binary logs

In fact most of the work will be to setup the compute instance to store the binary logs coming from MDS (one single compute instance could stream those binlogs from multiple MDS source).

On the compute instance we need …

On MySQL Database Service (aka MDS) on Oracle Cloud Infrastructure (aka OCI), when you create a new instance, you also need to set the credentials for the administrator:

Let’s focus on that account…

Please don’t forget the password, it cannot be recovered !!

First of all that account’s username has some limitations. Indeed, some names are reserved as it’s mentioned in the manual. So you could not use the following usernames:

• administrator
• ociadmin
• ocirpl
• mysql.sys
• mysql.session
• mysql.infoschema

This list can evolve, you can get the list directly from the MySQL DB System creation’s screen:

In fact, those accounts are already existing in the MySQL DB …

Please join our Oracle Live event, on August 10th, 9AM PST, 12 noon ET / 1 PM BRT / 6 PM CEST where Edward Screven, Oracle’s chief corporate architect, will share our latest MySQL innovations, along with the latest benchmarks, that show the speed and cost savings gained with MySQL HeatWave.  

Be sure to register here. 

There has been a recent MySQL innovation in the MySQL/Oracle Cloud partnership that has been very popular among the MySQL community. This new integrated, high performance in-memory analytics engine provides:

• A single database for running OLTP and OLAP workloads
• Real time analytics that accelerates MySQL queries by 400X …

On Oracle Cloud Infrastructure, aka OCI, MySQL Database Service, aka MDS uses the snapshot technology to backup your data.

This article is the second part of multiple part blog series. In part 1, we dealt with taking snapshots as backup. In this part, we deal with restoring the data.

Managed Snapshots

We saw in the post one how to create the snapshots automatically (Backup Plan) or Manually. Both type of backups are what we call Managed Snapshots. This means that as a user, we don’t have access to the Object Storage where the backup is stored.

So what’s the purpose of these snapshots ?

Let’s see them:

Data Restore

Restoring a MDS backup is recommended of course to save the data and in case of issue (hardware or software problem unlikely or human issue more …

On Oracle Cloud Infrastructure, aka OCI, MySQL Database Service, aka MDS uses the snapshot technology to backup your data.

I will explain how it works in the multiple part blog series. In part 1, we will deal with taking snapshots as backup. In part 2, we will see how to restore data and for which usage.

Snapshots

The Oracle Cloud Infrastructure Block Volume service provides you with the capability to group together multiple volumes in a volume group.

This is exactly what MDS uses to store the data.

We can easily see this from some global variables:

+-----------------------------+--------------------------------+ | Variable_name | Value | +-----------------------------+--------------------------------+ | datadir | /db/data/ | | innodb_data_home_dir | /db/data/ | | innodb_log_group_home_dir …

With MySQL 8.0, the version of MySQL Database Service aka MDS, the default character set has changed from latin1 to ut8mb4. The default collation is utf8mb4_0900_ai_ci but what does that mean ? and why are the utf8mb4_0900_* the recommended ones ?

Collations like utf8mb4_unicode_520_ci and utf8mb4_0900_ai_ci are based on Unicode Collation Algorithm (UCA). The number in the collation defines the UCA version:

• UCA 9.0.0 (recommended)
  - example: utf8mb4_0900_ai_ci
• UCA 5.2.0 (not recommended, see problems below)
  - example: utf8mb4_unicode_520_ci

The …

MySQL Database Service with HeatWave is now available in Brazil Southeast (Vinhedo) and Brazil East (Sao Paulo) regions.

With this addition, Oracle Cloud Infrastructure customers have more flexibility to deploy MySQL DB Systems closer to their applications, and it is now possible to select any of the 23 Oracle Cloud Infrastructure regions:

North America  US East (Ashburn)  US West (Phoenix)  US West (San Jose)  Canada Southeast (Toronto)  Canada Southeast (Montreal) Latin America  Brazil East (Sao Paulo)  Brazil Southeast (Vinhedo)  Chile Central (Santiago) EMEA  UK South (London)  UK West (Newport)  Germany Central (Frankfurt)  Switzerland North (Zurich)  Netherlands Northwest (Amsterdam)  Saudi Arabia West (Jeddah)  UAE East (Dubai) APAC  Japan East (Tokyo)  Japan Central (Osaka)  South Korea Central (Seoul)  South Korea North …

Recently I blogged about how to easily deploy a LAMP application to MDS.

Using the Terraform module (OCI Resource Manager’s Stack) you also have the possibility to choose the PHP version to install:

But as you should already know, not all versions support the latest default authentication method in MySQL 8.0: caching_sha2_password [1], [2], [3].

Most of the PHP applications are using mysqli and …

The MySQL Engineering team is proud to announce the Data Import feature in MySQL Database Service (MDS) and HeatWave.

The new Data Import enables faster and easier migrations to the MySQL Database Service. You can migrate from virtually any MySQL source, like AWS RDS/Aurora or MySQL on-premise, and from different versions, including 8.0, 5.7, or 5.6, directly to MySQL Database Service.

To migrate your existing MySQL databases, you perform two easy steps, in sequence or in parallel:

1. Use MySQL Shell to export data from an existing MySQL source into an OCI Object Storage bucket;
2. In MDS, create a new MySQL DB System referencing the bucket using a Pre-Authenticated Request (PAR). The data is imported automatically!

Together with MySQL Shell, MDS Data Import functionality dramatically reduces …