MySQL snapshots. Start with a checked baseline.

What is a MySQL snapshot in Cupcake?

A snapshot is a one-time baseline copy. It gives a target its starting dataset before ongoing replication or a later comparison. Use it to populate a new target, refresh a test environment, or establish the baseline for MySQL change data capture.

The operation uses your selected source, target, and table scope. Review the proposed schema and data actions before confirming: a baseline operation can replace existing target data. For a PostgreSQL target, follow the MySQL-to-PostgreSQL mapping workflow.

Schema export, data copy, and backup answer different questions.

A DDL export records database structure. It does not contain the rows unless data is exported separately. A snapshot baseline copies data into a target for a working workflow. An independent backup needs its own retention and restore process.

Replication targets can receive unwanted changes along with intended changes. Keep independent backups and restore testing in place. Read the guide to MySQL schema exports and data backups for the distinction.

Run a snapshot with an explicit scope.

1. Check the endpoints. Confirm which database you will read and which target may be changed.
2. Review tables and mappings. Choose the intended table scope and check primary keys, column rules, and any filters in the saved plan.
3. Confirm the proposed target actions. Review replacement or destructive options before starting. Use a test target for a new workflow.
4. Inspect the result. Wait for the completed job, review errors, and compare the copied data through the same scope.

Plan the handoff from initial copy to CDC.

A busy source may change while data is being copied. The handoff between a baseline and ongoing capture therefore matters: review how your selected workflow establishes its starting position and handles activity during the copy.

MySQL’s snapshot documentation explains why a replica needs an initial dataset and why consistency depends on the copy method. A completed copy alone should not be treated as proof of an atomic snapshot across every table.

After verifying the baseline, follow the MySQL CDC setup guide. For the Linux console’s DDL and bulk-copy workflow, see Enterprise MySQL snapshots.