12
15 Comments

Make Backup. Now.

Just a reminder to all of you and myself to create backups of everything.
During the weekend I've crashed my website during an update. Fatal error can't see website type of thing.
Fortunately I had a backup which I've uploaded on server.
In my case cost was few hours of downtime and few gray hairs. Make sure it won't be worse in your case.

Technical note: In my case updating wordpress plugins resulted in all this mess. Obviously it was a bit unexpected.

  1. 4

    I took a minute to think about my own situation there as I never make backups, but i don't think i need to.

    Code: Github
    Database: AWS
    Servers: AWS (via Heroku)

    If my personal computer exploded nothing would be lost.

    Is this right? can anyone see where I've missed something?

    1. 2

      Datacenters catch fire (see: OVH in past ~month). You should have database backups regardless. Code you'll have locally and in GH, so you should be fine.

    2. 1

      Same here. And my locally working directories for my projects are in a combination of Google Drive + Dropbox, so even if my computer exploded + Github disappeared, they'd be backed up secondarily too.

    3. 1

      Cloud providers don't always give guarantees for data recovery. It's usually a shared responsibility (same for security & other things). Better safe than sorry.

      1. 2

        I think the chances of GitHub losing my code the same day my local machine dies are pretty slim.

        Now wait and watch as that happens just because I said that.

    4. 1

      Makes sense to backup if you're storing the data yourself (db, files, other content) but code should be hosted in services like Github imo.

      Best setup is to dockerize your app so you can deploy anywhere/anytime.

    5. 0

      you can push a change that accidentally deletes stuff in your db, so you should have backups for sure even if aws itself won't lose your data doesn't mean that you don't mess up^^.

      1. 1

        If you’re using a production-tier database on Heroku you can roll back to any point in time. The more expensive the plan the longer you can roll back to. But this is a great safety net for the situation you mention and a huge reason why Heroku Postgres is my only database choice.

        1. 1

          I use heroku MySQL. Can’t beat it.

        2. 0

          yea it's pretty normal feature for a managed db, rds and digital ocean have it as well

  2. 2

    Don't just make backups, test them, see if you know how to recover from backup.
    I've been using borg for that, great incremental tool.

  3. 1

    As well as backups it's useful to do occasional "firedrills".
    As in what steps you take to do a full recovery if such an event happens, so that you have planned and are prepared for such an event.
    Might require an extra server and costs....but potentially very worthwhile for the time when a shitstorm happens.

  4. 1

    Good advice Zdanovi

  5. 1

    I also make regular backups

Trending on Indie Hackers
Designjoy crosses $70k MRR! Someone pinch me...😱 28 comments I quit my 1+m$/year job to work full-time on my own project 21 comments How I grew my Twitter (+9K) and Newsletter (+6k) in 3-4 months. AMA. 15 comments RocketList - a collection of cloud actions for your site 10 comments How a Twitter API suspension nearly killed my startup 5 comments Show IH: 16 Year Old Builds ₿itcoinForecast To Celebrate Currency Adoption 5 comments