Solo Developer Shares Backup Strategy for a 2 GB Server Running 39 Stock Products
After a nightly snapshot that retained only seven days failed to recover an eleven-day-old upload CSV, the author rebuilt their backup approach. Their catalogue of 39 products totals 856 MB, but the underlying pipeline code and research notes would be lost without separate protection. The author splits data into three tiers: small, irreplaceable metadata synced daily; regenerable product archives synced weekly off-server; and large raw assets rebuilt rather than duplicated. Because the server has a single vCPU, backup jobs are run sequentially to avoid memory exhaustion and corrupted archives. The author also emphasizes monthly restore tests over simply confirming that backups exist.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in