The reliable default for an edtech backup is a streamed pg_dump compressed with gzip, uploaded as a private object, and retained by a policy that can be replayed from metadata. Large-file throughput is the deciding constraint: keep the web process out of the byte path, make each archive addressable, and test restore rather than treating an upload receipt as proof.
Short answer: run the dump in a worker, stream compression into multipart object storage, write an immutable manifest beside it, and issue a signed restore URL only after a successful integrity check. A retention rule should be data, not a cron comment.
A training platform has awkward artifacts: recorded lessons, generated transcripts, and assessment exports can be large, while the Postgres rows describe who owns each artifact and when it may be deleted.…