{"id":75836,"date":"2025-09-09T11:26:46","date_gmt":"2025-09-09T05:56:46","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=75836"},"modified":"2025-09-09T14:49:14","modified_gmt":"2025-09-09T09:19:14","slug":"redis-cluster-backups-and-restoration","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/redis-cluster-backups-and-restoration\/","title":{"rendered":"Redis Cluster backups and restoration"},"content":{"rendered":"

Redis Cluster backups to Amazon S3 using a single bash script and cron. It\u2019s safe, slot-aware (backs up every node you run it on), and waits for BGSAVE to finish before uploading.<\/span><\/h1>\n

What this setup does<\/h1>\n
    \n
  • Runs on each Redis node, including masters and replicas, so you get a full cluster backup.<\/li>\n
  • It triggers BGSAVE, waits for the snapshot to finish, and then uploads your persistence files to S3:\n
      \n
    • dump.rdb<\/li>\n
    • appendonly.aof (if AOF or RDB+AOF is enabled)<\/li>\n<\/ul>\n<\/li>\n
    • It encrypts the data at rest in S3 using SSE-S3 or SSE-KMS. It also adds retention by using an S3 lifecycle rule and performs basic integrity checks.<\/li>\n<\/ul>\n

      Prerequisites (once per node)<\/h2>\n
        \n
      1. Install tools<\/strong>
        \napt-get update && apt-get install -y awscli jq
        \n# or: yum install -y awscli jq<\/li>\n
      2. AWS credentials on the node<\/strong>
        \nPrefer an EC2 instance profile role; otherwise configure aws configure.<\/li>\n
      3. IAM policy for the instance role<\/strong>
        \nGrant Put\/Get\/List to your chosen bucket, plus (optional) KMS encrypt:<\/li>\n
      4. Decide where Redis stores data<\/strong>\n
        \"Policy\"

        Policy<\/p><\/div>\n

        Check redis.conf:
        \n1. dir \/var\/lib\/redis
        \n2. dbfilename dump.rdb
        \n3. appendonly yes|no and appendfilename appendonly.aof<\/li>\n

      5. S3 bucket & (optional) lifecycle<\/strong>
        \nCreate the bucket s3:\/\/your-redis-backups\/ and add a lifecycle rule. For example, keep the data for 30 days, then move it to Glacier or delete it.<\/li>\n<\/ol>\n

        2) Drop-in backup script<\/h2>\n

        Save as \/usr\/local\/bin\/redis-cluster-backup.sh and make it executable.<\/p>\n

         <\/p>\n

        \"Script\"

        Script page -1<\/p><\/div>\n

        \"Script\"

        Script page – 2<\/p><\/div>\n

        \"Script\"

        Script page – 3<\/p><\/div>\n

        Optional: a small env file for easy overrides:-<\/h2>\n

        Create \/etc\/redis-backup.env (owned & readable by root only):<\/p>\n

        \"env

        env file<\/p><\/div>\n

        Then call the script with:<\/p>\n

        \"Cmd\"

        Cmd<\/p><\/div>\n

        3) Scheduling with Cron<\/strong><\/h2>\n

        Run daily at 02:15 local time or at any specific time as per your need:<\/p>\n

        \"Cron\"

        Cron<\/p><\/div>\n

        5) Restore (node or cluster)<\/h2>\n

        Standalone or single node (lab\/staging)<\/strong><\/p>\n

          \n
        1. Stop Redis.<\/li>\n
        2. Replace files in dir with your backup:\n
            \n
          1. If restoring RDB(Redis Database File)<\/strong>: put the dump.rdb(point-in-time snapshot).<\/li>\n
          2. If AOF(Append Only File)<\/strong> or mixed<\/strong>: put appendonly.aof (and ensure appendonly yes).<\/li>\n<\/ol>\n<\/li>\n
          3. Start Redis \u2014 it loads whichever persistence you\u2019ve enabled.<\/li>\n<\/ol>\n

            Cluster restore (same topology)<\/strong><\/p>\n

              \n
            • Restore each node from its own backup (masters & replicas).<\/li>\n
            • Start nodes; verify with:\n

              \"Redis\"

              Redis<\/p><\/div><\/li>\n

            • Ensure slot ownership and replication match your desired layout.(If you are re-creating a cluster from scratch, use cluster create with the master\/replica mapping and then restore files before opening to traffic.)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

              Redis Cluster backups to Amazon S3 using a single bash script and cron. It\u2019s safe, slot-aware (backs up every node you run it on), and waits for BGSAVE to finish before uploading. What this setup does Runs on each Redis node, including masters and replicas, so you get a full cluster backup. It triggers BGSAVE, […]<\/p>\n","protected":false},"author":2167,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":110},"categories":[5877],"tags":[8104,8105],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/75836"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/2167"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=75836"}],"version-history":[{"count":4,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/75836\/revisions"}],"predecessor-version":[{"id":76128,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/75836\/revisions\/76128"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=75836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=75836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=75836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}