Backup Created Success Block for React

Nothing was backed up or restored. The tables, their row counts and the size are typed sample data. What the browser really does is real: the copy buttons write to the clipboard, and Download manifest saves a small JSON file of the new backup, named a sample in its own note. To wire it, fill TABLES, SIZE_MB and RETENTION from your backup job, keep AS_OF to the day it ran, and replace the wait in test with a call that opens the snapshot.

There is one cell per day of the retention, 14 here, worked out from the day of the backup, so the newest is today's and the oldest is the one the next backup removes. Each cell is a native radio button named for its day and for when it is deleted (its day plus 14 days: 1 Oct goes on 15 Oct). Picking a cell, with a click or the arrow keys, rewrites the sentence under the rack, the snapshot id, the deletion day and the restore command, and the page keeps its height.

It runs for the chosen snapshot: the button says Testing… and keeps its size while it waits a moment, then a polite status line says that snapshot opened and the five tables were found, and that nothing was restored. It is local; connect it to a real dry-run restore.

A small JSON file for the new backup: the database, the snapshot id, the day and time it was taken, the day it expires, the retention, the tables with their rows, the size and a note that it is a sample. It is built in the browser from the same typed data the page shows, and the status line says it was downloaded.

The chosen snapshot's id and its restore command, through the browser's clipboard; each says what it copies in its name and is announced when it works.

The rack wraps to two rows of seven, the foot with the two buttons is pinned to the bottom of the screen so Test a restore is always within reach, and the download button reads Download with its full name kept for assistive technology.