Skip to content
Aurora
AWS track / Databases & Caching
Entry overview
Sub-page 7 of 8
Operational lifecycle

Deciding on Backtrack at Cluster Creation, Before You Wish You Had It

Decision drivers
  • Engine choice (Backtrack is MySQL-only — see page 1)
  • Whether Backtrack is being decided at cluster-creation time or retrofitted
  • Write volume (drives how fast the actual backtrack window shrinks)
  • Whether snapshot/PITR restore has actually been tested end-to-end

Backtrack (MySQL-compatible only) trades storage cost for change records — billed per million change records per hour — for a fast in-place rewind that avoids a full restore-to-new-instance. It's not a backup; it's a precision undo tool with its own cost and its own limits.

Gated · a free account unlocks the full catalog
Sign in to keep reading

This page is part of the AWS track's gated content. Sign in — free — to keep reading. A free account unlocks the full catalog.

Sign in