Point-in-time recovery in MySQL - Mini Project: Build & Apply

Point-in-time Recovery Setup in MySQL

📖 Scenario: You are a database administrator for a small online store. You want to prepare your MySQL database for point-in-time recovery so that you can restore data to any specific moment in time after a failure or accidental data loss.

🎯 Goal: Set up the MySQL database to enable point-in-time recovery by configuring binary logging, creating a backup, and preparing the recovery process.

📋 What You'll Learn

Enable binary logging in MySQL configuration

Create a full backup of the database

Record the binary log file name and position after the backup

Write a command to restore the backup and apply binary logs up to a specific point in time

💡 Why This Matters

🌍 Real World

Point-in-time recovery is essential for recovering from accidental data deletions or corruption by restoring the database to a precise moment before the issue occurred.

💼 Career

Database administrators and developers use point-in-time recovery to minimize data loss and downtime in production environments.

1

Enable Binary Logging

Edit the MySQL configuration file to enable binary logging by adding the line log_bin=mysql-bin under the [mysqld] section.

MySQL

# Add the line 'log_bin=mysql-bin' under the [mysqld] section in the MySQL config file
# Your code here

Hint

Binary logging records all changes to the database, which is necessary for point-in-time recovery.

2

Create a Full Backup

Use the mysqldump command to create a full backup of the database named store_db and save it to a file called store_backup.sql.

MySQL

[mysqld]
log_bin=mysql-bin
# Run mysqldump to backup store_db to store_backup.sql
# Your code here

Hint

Use mysqldump with the database name and redirect output to a file.

3

Record Binary Log Position

After the backup, run the SQL command SHOW MASTER STATUS; to get the current binary log file name and position. Store these values in variables binlog_file and binlog_pos.

MySQL

[mysqld]
log_bin=mysql-bin

mysqldump -u root -p store_db > store_backup.sql
# Run SHOW MASTER STATUS and save results to binlog_file and binlog_pos
# Your code here

Hint

SHOW MASTER STATUS shows the current binary log file and position. Assign them to variables for later use.

4

Prepare Point-in-Time Recovery Command

Write the command to restore the backup from store_backup.sql and apply binary logs up to a specific datetime, using mysqlbinlog with --stop-datetime="2024-06-01 12:00:00". Use the variables @binlog_file and @binlog_pos for the binary log file and position.

MySQL

[mysqld]
log_bin=mysql-bin

mysqldump -u root -p store_db > store_backup.sql

SHOW MASTER STATUS;
SET @binlog_file = 'mysql-bin.000001';
SET @binlog_pos = 154;
# Write the command to restore backup and apply binary logs up to 2024-06-01 12:00:00
# Your code here

Hint

First restore the backup, then apply binary logs up to the stop datetime using mysqlbinlog.

Practice

1. What is the main purpose of point-in-time recovery in MySQL?

easy

A. To create a full backup of the database

B. To restore the database to a specific moment using binary logs

C. To optimize query performance

D. To delete old data automatically

Solution

1. Step 1: Understand point-in-time recovery concept

   Point-in-time recovery allows restoring the database to a specific moment in time, usually after a backup, by replaying changes from binary logs.

2. Step 2: Identify the correct purpose

   Options A, C, and D describe other database tasks, not point-in-time recovery.

3. Final Answer:

   To restore the database to a specific moment using binary logs -> Option B

4. Quick Check:

   Point-in-time recovery = restore specific moment [OK]

Hint: Point-in-time recovery = restore using binary logs [OK]

Common Mistakes:

• Confusing point-in-time recovery with full backup
• Thinking it optimizes queries
• Assuming it deletes data automatically

2. Which of the following is the correct syntax to start point-in-time recovery using mysqlbinlog from a binary log file named binlog.000001 starting at '2024-06-01 10:00:00'?

easy

A. mysqlbinlog --start-datetime='2024-06-01 10:00:00' binlog.000001 | mysql -u root -p

B. mysqlbinlog --stop-datetime='2024-06-01 10:00:00' binlog.000001 | mysql -u root -p

C. mysqlbinlog --start='2024-06-01 10:00:00' binlog.000001 | mysql -u root -p

D. mysqlbinlog --datetime='2024-06-01 10:00:00' binlog.000001 | mysql -u root -p

Solution

1. Step 1: Recall mysqlbinlog options for point-in-time recovery

   The correct option to specify start time is --start-datetime.

2. Step 2: Check the syntax correctness

   mysqlbinlog --start-datetime='2024-06-01 10:00:00' binlog.000001 | mysql -u root -p uses --start-datetime correctly. Options B, C, and D use incorrect or non-existent flags.

3. Final Answer:

   mysqlbinlog --start-datetime='2024-06-01 10:00:00' binlog.000001 | mysql -u root -p -> Option A

4. Quick Check:

   Use --start-datetime to begin recovery [OK]

Hint: Use --start-datetime to specify recovery start time [OK]

Common Mistakes:

• Using --stop-datetime instead of --start-datetime
• Using incorrect option names like --start or --datetime
• Omitting the binary log file name

3. Given the command:
mysqlbinlog --start-datetime='2024-06-01 09:00:00' --stop-datetime='2024-06-01 10:00:00' binlog.000002 | mysql -u root -p
What will this command do?

medium

A. Restore the entire binary log file without time filtering

B. Restore changes only after 10 AM on June 1, 2024

C. Create a backup of the binary log file

D. Restore all changes from the binary log starting at 9 AM until 10 AM on June 1, 2024

Solution

1. Step 1: Understand the command options

   The command uses --start-datetime and --stop-datetime to limit the replay of changes between 9 AM and 10 AM on June 1, 2024.

2. Step 2: Interpret the command effect

   It replays only the changes in that time window, restoring the database state for that period.

3. Final Answer:

   Restore all changes from the binary log starting at 9 AM until 10 AM on June 1, 2024 -> Option D

4. Quick Check:

   Start and stop datetime limit recovery range [OK]

Hint: Start and stop datetime limit replay range [OK]

Common Mistakes:

• Thinking it restores after stop time only
• Assuming it restores entire log ignoring time
• Confusing backup creation with recovery

4. You run the command:
mysqlbinlog --start-datetime='2024-06-01 08:00:00' --stop-datetime='2024-06-01 07:00:00' binlog.000003 | mysql -u root -p
What is the problem with this command?

medium

A. The stop datetime is earlier than the start datetime, causing an error

B. The binary log file name is incorrect

C. The command is missing the user password

D. The command will restore the entire binary log file

Solution

1. Step 1: Check the datetime order

   The --stop-datetime is set to '2024-06-01 07:00:00', which is before the --start-datetime '2024-06-01 08:00:00'. This is logically incorrect.

2. Step 2: Understand the effect of reversed times

   This causes mysqlbinlog to fail or produce no output because the stop time cannot be before the start time.

3. Final Answer:

   The stop datetime is earlier than the start datetime, causing an error -> Option A

4. Quick Check:

   Stop datetime must be after start datetime [OK]

Hint: Stop datetime must be after start datetime [OK]

Common Mistakes:

• Ignoring datetime order
• Assuming missing password causes this error
• Thinking binary log file name is wrong

5. You have a full backup taken at '2024-06-01 06:00:00' and binary logs from that time onward. You want to recover the database to '2024-06-01 09:30:00' after accidentally deleting some data at 9:45 AM. Which sequence of commands correctly performs point-in-time recovery?

hard

A. Restore full backup only without using binary logs

B. Run mysqlbinlog --start-datetime='2024-06-01 09:30:00' --stop-datetime='2024-06-01 09:45:00' binlog.* | mysql -u root -p only

C. Restore full backup, then run mysqlbinlog --start-datetime='2024-06-01 06:00:00' --stop-datetime='2024-06-01 09:30:00' binlog.* | mysql -u root -p

D. Run mysqlbinlog --stop-datetime='2024-06-01 09:30:00' binlog.* | mysql -u root -p without restoring backup

Solution

1. Step 1: Restore the full backup first

   Point-in-time recovery requires restoring the last full backup before applying binary logs.

2. Step 2: Replay binary logs up to the desired time

   Use mysqlbinlog with --start-datetime at backup time and --stop-datetime at recovery time to replay changes correctly.

3. Step 3: Verify the recovery time is before the accidental deletion

   Stopping at 9:30 AM avoids replaying the deletion at 9:45 AM.

4. Final Answer:

   Restore full backup, then run mysqlbinlog with start and stop datetime from backup to 9:30 AM -> Option C

5. Quick Check:

   Backup restore + replay logs to recovery time [OK]

Hint: Restore backup first, then replay logs up to recovery time [OK]

Common Mistakes:

• Skipping full backup restore
• Replaying logs after the unwanted change
• Trying to recover without backup