Point-in-time recovery in MySQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the MySQL binary log recovery from a specific point in time.

MySQL

mysqlbinlog --start-datetime='[1]' mysql-bin.000001 | mysql -u root -p

Drag options to blanks, or click blank then click option'

A2023/01/01 12:00:00

B2023-01-01

C12:00:00

D2023-01-01 12:00:00

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the date without time.

Using slashes instead of dashes in the date.

Using only the time without the date.

The --start-datetime option requires a full date and time in the format YYYY-MM-DD HH:MM:SS to specify the exact point to start recovery.

2fill in blank

medium

Complete the command to stop the binary log recovery at a specific position.

MySQL

mysqlbinlog --stop-position=[1] mysql-bin.000002 | mysql -u root -p

Drag options to blanks, or click blank then click option'

A1000

Bstart

Cend

Dnow

Attempts:

3 left

💡 Hint

Common Mistakes

Using keywords like 'start' or 'end' instead of a number.

Using non-numeric values.

The --stop-position option requires a numeric position in the binary log to stop applying events.

3fill in blank

hard

Fix the error in the command to recover data up to a specific date and time.

MySQL

mysqlbinlog --stop-datetime='[1]' mysql-bin.000003 | mysql -u root -p

Drag options to blanks, or click blank then click option'

A15:00:00 2023-02-28

B2023/02/28 15:00:00

C2023-02-28 15:00:00

D2023-02-30 15:00:00

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid dates like February 30th.

Swapping date and time order.

Using slashes instead of dashes.

The date must be valid. February 30th does not exist, so use February 28th. The format must be YYYY-MM-DD HH:MM:SS.

4fill in blank

hard

Fill both blanks to create a command that recovers data between two points in time.

MySQL

mysqlbinlog --start-datetime='[1]' --stop-datetime='[2]' mysql-bin.000004 | mysql -u root -p

Drag options to blanks, or click blank then click option'

A2023-03-01 08:00:00

B2023-03-01 18:00:00

C2023-03-02 08:00:00

D2023-02-28 23:59:59

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping start and stop times.

Using stop time earlier than start time.

The --start-datetime should be earlier than --stop-datetime. Here, recovery starts at 8 AM and stops at 6 PM on March 1st, 2023.

5fill in blank

hard

Fill both blanks to create a command that recovers data from a specific position to a specific datetime.

MySQL

mysqlbinlog --start-position=[1] --stop-datetime='[2]' mysql-bin.000005 | mysql -u root -p

Drag options to blanks, or click blank then click option'

A1500

B2023-04-10 14:30:00

C2000

D2023-04-10 12:00:00

Attempts:

3 left

💡 Hint

Common Mistakes

Using a date where a number is expected.

Using an invalid date format.

The --start-position is a numeric log position to begin recovery, and --stop-datetime is the date and time to stop recovery.