Oracle Flashback Table and MySQL snapshots
With Amazon DMS, you can restore databases to a specific point in time using Oracle Flashback Table and MySQL snapshots. Oracle Flashback Table provides a way to view and restore data from a specified time in the past, while MySQL snapshots capture the state of a database at a specific point for backup or replication purposes.
| Feature compatibility | Amazon SCT / Amazon DMS automation level | Amazon SCT action code index | Key differences |
|---|---|---|---|
|
|
N/A |
N/A |
Storage-level backup managed by Amazon RDS. |
Oracle usage
Oracle Flashback Table is a data protection feature used to undo changes to a table and rewind it to a previous state, not from the backup. While Flashback table operations are running, the affected tables are locked, but the rest of the database remains available.
If the structure of a table has been changed since the point of restore, the FLASHBACK will fail.
Make sure that the row movement is turned on.
The data to restore must be found in the undo, and the database administrator manages the size and retention.
You can restore a table to a System Change Number (SCN), restore point, or timestamp.
Examples
Flashback a table using SCN (query V$DATABASE to obtain the SCN).
SELECT CURRENT_SCN FROM V$DATABASE; FLASHBACK TABLE employees TO SCN 3254648;
Flashback a table using a restore point (query V$RESTORE_POINT to obtain restore points).
SELECT NAME, SCN, TIME FROM V$RESTORE_POINT; FLASHBACK TABLE employees TO RESTORE POINT employees_year_update;
Flashback a table using a timestamp (query V$PARAMETER to obtain the undo_retention value).
SELECT NAME, VALUE/60 MINUTES_RETAINED FROM V$PARAMETER WHERE NAME = 'undo_retention'; FLASHBACK TABLE employees TO TIMESTAMP TO_TIMESTAMP('2017-09-21 09:30:00', 'YYYY-MM-DD HH:MI:SS');
For more information, see Backup and Recovery User Guide
MySQL usage
Snapshots are the primary backup mechanism for Amazon Aurora databases. They are extremely fast and nonintrusive. You can take snapshots using the Amazon RDS Management Console or the Amazon CLI. Unlike RMAN, there is no need for incremental backups. You can choose to restore your database to the exact time when a snapshot was taken or to any other point in time.
Amazon Aurora provides the following types of backups:
-
Automated backups — Always enabled on Amazon Aurora. They do not impact database performance.
-
Manual backups — You can create a snapshot at any time. There is no performance impact when taking snapshots of an Aurora database. Restoring data from snapshots requires creation of a new instance. Up to 100 manual snapshots are supported for each database.
Examples
For examples, see MySQL Snapshots.
Summary
| Description | Oracle | Amazon Aurora |
|---|---|---|
|
Create a restore point |
|
|
|
Configure flashback retention period |
|
Configure the Backup retention window setting using the Amazon Management Console or Amazon CLI. |
|
Flashback table to a previous restore point |
|
Create new cluster from a snapshot.
Add new instance to the cluster.
Use |
|
Flashback table to a previous point in time |
|
Create a new cluster from a snapshot and provide a specific point in time.
Add a new instance to the cluster:
Use |
For more information, see mysqldump — A Database Backup Program