▲ | sahilagarwal 5 days ago | ||||||||||||||||
I guess my non-management / non-business side is show here, but how can it be that much?? I still remember I designed a fairly simple cron job that took database backups when I was a junior developer. It gets even easier now that you have cheap s3 - just upload the dump to s3 every day and set the s3 deletion policy to whatever is feasible for you. | |||||||||||||||||
▲ | alemanek 5 days ago | parent | next [-] | ||||||||||||||||
I am not an expert here but I am currently researching for a planned project. For backups, including Postgres, I was planning on paying Veeam ~$500 a year for a software license to backup the active node and Postgres database to s3/r2. Standby node would be getting streaming updates via logical replication. There are free options as well but I didn’t want to cheap out on the backups. It looks pretty turnkey. I am a software engineer not a sysadmin though. Still just theory as well as I haven’t built it out yet | |||||||||||||||||
▲ | nine_k 5 days ago | parent | prev | next [-] | ||||||||||||||||
Taking database backups is relatively simple. What differentiates a good solution is the ease of restoring from a backup. This includes the certainty that the restored state would be a correct point-in-time state from the past, not an amalgamation of several such states. | |||||||||||||||||
▲ | fragmede 5 days ago | parent | prev [-] | ||||||||||||||||
How much were you paid as a jr developer, and how long did it take you to set up? Then round up to mid-level developer, and add in hardware and software costs. | |||||||||||||||||
|