Backup future-proof

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

FF-Admin/ff-admin-server#150

jkeffects commented

2025-10-31 07:34:00 +00:00

Owner

Update:

Update all Tables to Use UUID primary key
transform old backups by mapping nested to plain content not by loading with old mechanism
send info of started / running restore to all clients
block all interactions (API) while running backup restore
create packup (point before restore) before every restore to easily roll back
maybe demo run restore and show the effects (inserted / updated / deleted count)

backup functionality:

auto-discover all tables and store to json with each table having top level key
map backup content to table columns existing in schema with defaults to reduce failing the restore process of older backup on significantly newer database
add hash to backup to detect manipulation
force load manipulated data via explicit confirm
generic restore via auto-detected primary key (used for inerst or update on duplicate)
load full backup or only partial table (never clear table and fill afterwards -> prevent foreign key cascade)
load backup by overwriting existing data and then deleting ids not inside backup
allow partial backup load via table select (mind missing foreign data that needs to be added / base-tables of tree are auto-restored if foreign are selected)
allow reset to old data with keeping newer data

Update: - [ ] Update all Tables to Use UUID primary key - [ ] transform old backups by mapping nested to plain content not by loading with old mechanism - [ ] send info of started / running restore to all clients - [ ] block all interactions (API) while running backup restore - [ ] create packup (point before restore) before every restore to easily roll back - [ ] maybe demo run restore and show the effects (inserted / updated / deleted count) backup functionality: - [ ] auto-discover all tables and store to json with each table having top level key - [ ] map backup content to table columns existing in schema with defaults to reduce failing the restore process of older backup on significantly newer database - [ ] add hash to backup to detect manipulation - [ ] force load manipulated data via explicit confirm - [ ] generic restore via auto-detected primary key (used for inerst or update on duplicate) - [ ] load full backup or only partial table (never clear table and fill afterwards -> prevent foreign key cascade) - [ ] load backup by overwriting existing data and then deleting ids not inside backup - [ ] allow partial backup load via table select (mind missing foreign data that needs to be added / base-tables of tree are auto-restored if foreign are selected) - [ ] allow reset to old data with keeping newer data

jkeffects added this to the FF Admin Next milestone

jkeffects added the

labels

jkeffects self-assigned this

jkeffects added this to the (deleted) project

2025-10-31 07:47:16 +00:00

Rows
Columns

Backup future-proof #150