{"id":21026,"date":"2016-07-26T08:30:17","date_gmt":"2016-07-26T07:30:17","guid":{"rendered":"https:\/\/www.inovex.de\/\/?p=1918"},"modified":"2026-03-17T08:58:07","modified_gmt":"2026-03-17T07:58:07","slug":"redis-backup","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/","title":{"rendered":"Redis: Protect your cached data"},"content":{"rendered":"<p>Welcome to our second blog article concerning the Redis caching engine. Here I want to introduce Redis persistence mechanics, their pros, cons and some configuration examples. Additionally I want to describe different backup and restore strategies. If you haven&#8217;t done so already, have a <a href=\"https:\/\/www.inovex.de\/\/redis-more-than-caching\/\" target=\"_blank\" rel=\"noopener\">look at part 1<\/a> for the basics.<!--more--><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_83 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\"><p class=\"ez-toc-title\" style=\"cursor:inherit\"><\/p>\n<\/div><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Overview\" >Overview<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Redis-persistence-RDB-Snapshotting\" >Redis persistence: RDB Snapshotting<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Configuration\" >Configuration<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Redis-persistence-AOF-Logging\" >Redis persistence: AOF Logging<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Configuration-2\" >Configuration<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Should-I-use-RDB-or-AOF-or-both\" >Should I use RDB or AOF or both?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#How-to-backup-and-restore\" >How to backup and restore?<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#RDB-Restore\" >RDB Restore<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#AOF-Restore\" >AOF Restore<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Read-on\" >Read on<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#Join-us\" >Join us!<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Overview\"><\/span>Overview<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>How does RDB Snapshotting work?<\/li>\n<li>What is AOF Logging?<\/li>\n<li>Should I use RDB or AOF or both?<\/li>\n<li>How to backup and restore?<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Redis-persistence-RDB-Snapshotting\"><\/span>Redis persistence: RDB Snapshotting<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>RDB Snapshotting creates a point-in-time file of your Redis data. These Files can be easily used for backup and disaster recovery. You can transfer the file to other Redis instances to bring the dataset wherever you want.<\/p>\n<figure id=\"attachment_1929\" aria-describedby=\"caption-attachment-1929\" style=\"width: 800px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"size-large wp-image-1929\" src=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-1024x238.png\" alt=\"Redis background-saving\" width=\"800\" height=\"186\" srcset=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-1024x238.png 1024w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-300x70.png 300w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-768x179.png 768w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-1536x358.png 1536w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-400x93.png 400w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1-360x84.png 360w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-1.png 1920w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption id=\"caption-attachment-1929\" class=\"wp-caption-text\">The Redis background-saving process.<\/figcaption><\/figure>\n<p><strong>Logfile Example:<\/strong><\/p>\n<p><em>23817:M 15 Jul 13:53:10.855 * Background saving started by pid 23828<\/em><\/p>\n<p>23828:C 15 Jul 13:53:10.856 * DB saved on disk<\/p>\n<p>23828:C 15 Jul 13:53:10.857 * RDB: 2 MB of memory used by copy-on-write<\/p>\n<p>23817:M 15 Jul 13:53:10.932 * Background saving terminated with success<\/p>\n<p>As you see the original Redis (Pid 23817) will serve client requests while the fork (Pid 23828) saves the dataset on disk. The log mentions that 2 MB were used by copy-on-write during the snapshot. So in the worst case the fork will use the same amount of memory which is used by the original Redis process.<\/p>\n<p>The Linux out of memory (OOM) killer will kill the fork if the system runs low on memory. To avoid this you can tune a kernel parameter at your Redis servers. Just add &#8218;vm.overcommit_memory = 1&#8216; to \/etc\/sysctl.conf and then reboot or run the command <span class=\"lang:sh decode:true crayon-inline \">sysctl vm.overcommit_memory=1<\/span> for the change to take effect.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Configuration\"><\/span>Configuration<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Here you will find the configuration options and a short description.<\/p>\n<ul>\n<li><strong>save 900 1\/save 300 10\/save 60 10000:<\/strong> These are the default settings to tell Redis when it should start saving the dataset. Rule: save after x seconds if at least x keys changed<\/li>\n<li><strong>stop-writes-on-bgsave-error yes:<\/strong> When backgroundsaving fails, should the Redis stop accepting writes. If your monitoring for disk, permissions and so forth works well, set it to no.<\/li>\n<li><strong>rdbcompression yes:<\/strong> Uses a bit more CPU when doing LZF compression, but reduces the filesize.<\/li>\n<li><strong>dbfilename dump.rdb:<\/strong> Choose the name of your snapshot file<\/li>\n<li><strong>rdbchecksum yes:<\/strong> Creates a CRC64 checksum at the end of the snapshot file. The Performance hit to pay during saving and loading the snapshotfile is around 10%. Set to no for maximum performance, but less resistence to corruption<\/li>\n<li><strong>dir \/var\/lib\/redis\/:<\/strong> Choose the directory where to save the snapshot file.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Redis-persistence-AOF-Logging\"><\/span>Redis persistence: AOF Logging<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The AOF Log is an append-only logfile. All operations that change the dataset are logged one after another.<\/p>\n<p>AOF logging is very robust and you can have different fsync policies to tell Redis how often you want to write the logfile. At an outage (example: kill -9 or power outage) you lose only the data written on disk after the last fsync.<\/p>\n<p>The AOF fsync can cause high load due to its ongoing I\/O on disk.\u00a0As the log is uncompressed, its size is even bigger than the compared RDB Snapshot of the same dataset (twice the size).\u00a0When the file exceeds a certain size, Redis will spawn a fork to rewrite the logfile, saving some space.\u00a0The fork is human readable and even editable via editor. You could for example remove a <em>flush all<\/em> from the logfile, restart Redis, and thereby recover your dataset.<\/p>\n<figure id=\"attachment_1930\" aria-describedby=\"caption-attachment-1930\" style=\"width: 800px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"size-large wp-image-1930\" src=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-1024x341.png\" alt=\"Redis AOF logfile rewrite\" width=\"800\" height=\"266\" srcset=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-1024x341.png 1024w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-300x100.png 300w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-768x256.png 768w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-1536x511.png 1536w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-400x133.png 400w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2-360x120.png 360w, https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-persistance-2.png 1919w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption id=\"caption-attachment-1930\" class=\"wp-caption-text\">The Redis AOF logfile rewrite process.<\/figcaption><\/figure>\n<p><strong>Logfile Example:<\/strong><\/p>\n<p><em>25134:M 18 Jul 13:37:39.333 * Background append only file rewriting started by pid 12833<\/em><\/p>\n<p>25134:M 18 Jul 13:37:39.369 * AOF rewrite child asks to stop sending diffs.<\/p>\n<p>12833:C 18 Jul 13:37:39.369 * Parent agreed to stop sending diffs. Finalizing AOF&#8230;<\/p>\n<p>12833:C 18 Jul 13:37:39.369 * Concatenating 0.00 MB of AOF diff received from parent.<\/p>\n<p>12833:C 18 Jul 13:37:39.369 * SYNC append only file rewrite performed<\/p>\n<p>12833:C 18 Jul 13:37:39.370 * AOF rewrite: 4 MB of memory used by copy-on-write<\/p>\n<p>25134:M 18 Jul 13:37:39.404 * Background AOF rewrite terminated with success<\/p>\n<p>25134:M 18 Jul 13:37:39.404 * Residual parent diff successfully flushed to the rewritten AOF (0.00 MB)<\/p>\n<p>25134:M 18 Jul 13:37:39.404 * Background AOF rewrite finished successfully<\/p>\n<p>As you see the parent (pid 25134) spawns the child (pid 12833). The AOF diff is 0.00 MB as there was no change at the Redis dataset during this time.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Configuration-2\"><\/span>Configuration<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Here are the configuration options for AOF logging, each with a short description.<\/p>\n<ul>\n<li><strong>appendonly no:<\/strong> Default is no. To enable choose \u201cyes\u201c<\/li>\n<li><strong>appendfilename &#8222;appendonly.aof&#8220;:<\/strong> Choose the name of your logfile<\/li>\n<li><strong>appendfsync everysec:<\/strong> everysec: sync the changes on the dataset every second (good compromise between performance and data safety), no: don&#8217;t fsync, let the OS flush the output buffer when it wants (best performance), always: fsync after every operation on the dataset (highest I\/O , best data safety)<\/li>\n<li><strong>no-appendfsync-on-rewrite no:<\/strong> During AOF rewrite, stop fsync, no: (data safety, but produces additional I\/O), yes (outage during aof-rewrite will cause data-loss, lower I\/O)<\/li>\n<li><strong>auto-aof-rewrite-percentage 100:<\/strong> When the size exceeds 100% the rewrite is triggered. Set it to \u201c0\u201c to disable the rewrite completely<\/li>\n<li><strong>auto-aof-rewrite-min-size 64mb:<\/strong> Min Size of the File to trigger the rewrite (even if percentage is reached)<\/li>\n<li><strong>aof-load-truncated yes:<\/strong> yes: A corrupted aof file will cause no exception and the server starts normally with an event at the logfile, no: Redis will crash with an error, use redis-check-aof to fix the corrupted logfile (remove incomplete commands\/lines)<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Should-I-use-RDB-or-AOF-or-both\"><\/span>Should I use RDB or AOF or both?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Now that you know the basics of both methods, how do you decide which to use for which use-case? When you need maximum data protection, want easy snapshots and minimal data loss in case of an outage you can enable both features at the same time.<\/p>\n<p>Redis handles both well, the RDB-Snapshot and AOF-Rewrite processes will never run at the same time. But keep in mind: When starting up, Redis will always take the AOF Logfile, as it provides the more robust solution.<\/p>\n<p>If you your data is very important but you can live with a few minutes of data loss, use RDB alone. Redis starts faster, backups are easily created an RDB snapshots can be transferred. You could also save the logfile from time to time, but snapshots and backups via RDB are preferred.<\/p>\n<p>For the (possibly far) future a unification of both approaches into a single method is planned.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How-to-backup-and-restore\"><\/span>How to backup and restore?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When using AOF log or RDB snapshots you need a process, a tool to transfer the file and a location to store it.\u00a0Keep in mind that in case of a disaster all your data is lost. The goal is to backup the AOF or RDB file frequently, encrypt it and transfer it safely to a location outside the datacenter.<\/p>\n<p>Here are some ideas:<\/p>\n<ul>\n<li>cron\/systemd-timers to run the backup script\/tool.<\/li>\n<li>gpg for encryption<\/li>\n<li>scp for secure transfer outside the datacenter<\/li>\n<li>Amazon S3 bucket to store it<\/li>\n<li>linux find command to cleanup old backup files<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"RDB-Restore\"><\/span>RDB Restore<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>To restore an RDB snapshot you have to stop the Redis server and copy the file to the data-dir location (\/var\/lib\/redis). The owner of the file has to be redis. After you re-start the instance, the dataset is loaded from the file.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"AOF-Restore\"><\/span>AOF Restore<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>To restore from an AOF log you have to stop the Redis server and copy the AOF log to the data-dir location (\/var\/lib\/redis). The owner of the file has to be redis. Re-start the instance and Redis will execute all commands from the AOF log. If the server crashes while loading the file you may have to check and fix the corrupted file:<\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li>Make a copy of the AOF log.<\/li>\n<li>Fix the file \u201credis-check-aof &#8211;fix\u201c.<\/li>\n<li>Compare both files: diff -u<\/li>\n<li>Restart the instance with the fixed file.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>I hope I was able to\u00a0give you a more detailed view on the Redis persistence options and how to backup and restore your Redis datasets.\u00a0Feel free to comment or share this article \u2013 and don&#8217;t forget to come back\u00a0for the next\u00a0article in this series, \u201cRedis High Availbility\u201c.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Read-on\"><\/span>Read on<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Want to find out more about the services we offer in Data Center Automation? Have a <a href=\"https:\/\/www.inovex.de\/en\/our-services\/data-centre-automation\/\" target=\"_blank\" rel=\"noopener\">look at our website<\/a>, write an email to <a href=\"mailto:info@inovex.de\" target=\"_blank\" rel=\"noopener\">info@inovex.de<\/a> or call <a href=\"tel:+497216190210\">+49 721 619 021-0<\/a>.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Join-us\"><\/span>Join us!<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Looking for a job where you can work with cutting edge technology on a daily basis? We&#8217;re currently hiring Linux Systems Engineers (m\/w\/d) in Karlsruhe, Pforzheim, Munich, Cologne and Hamburg!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Welcome to our second blog article concerning the Redis caching engine. Here I want to introduce Redis persistence mechanics, their pros, cons and some configuration examples. Additionally I want to describe different backup and restore strategies. If you haven&#8217;t done so already, have a look at part 1 for the basics.<\/p>\n","protected":false},"author":47,"featured_media":1866,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"ep_exclude_from_search":false,"footnotes":""},"tags":[71],"service":[414],"coauthors":[{"id":47,"display_name":"Christoph Stich","user_nicename":"cstich"}],"class_list":["post-21026","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","tag-cloud","service-cloud"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Redis Persistence: Protect your Cached Data<\/title>\n<meta name=\"description\" content=\"Let&#039;s have a look at Redis persistence mechanics, pros, cons and configuration examples and its different backup and restore strategies.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Redis Persistence: Protect your Cached Data\" \/>\n<meta property=\"og:description\" content=\"Let&#039;s have a look at Redis persistence mechanics, pros, cons and configuration examples and its different backup and restore strategies.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/\" \/>\n<meta property=\"og:site_name\" content=\"inovex GmbH\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/inovexde\" \/>\n<meta property=\"article:published_time\" content=\"2016-07-26T07:30:17+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-17T07:58:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2300\" \/>\n\t<meta property=\"og:image:height\" content=\"678\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Christoph Stich\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild-1024x302.png\" \/>\n<meta name=\"twitter:creator\" content=\"@inovexgmbh\" \/>\n<meta name=\"twitter:site\" content=\"@inovexgmbh\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Christoph Stich\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"7\u00a0Minuten\" \/>\n\t<meta name=\"twitter:label3\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data3\" content=\"Christoph Stich\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/\"},\"author\":{\"name\":\"Christoph Stich\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/person\\\/683665a7244d27a96c0d5e561c777c11\"},\"headline\":\"Redis: Protect your cached data\",\"datePublished\":\"2016-07-26T07:30:17+00:00\",\"dateModified\":\"2026-03-17T07:58:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/\"},\"wordCount\":1387,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-artikelbild.png\",\"keywords\":[\"Cloud\"],\"articleSection\":[\"English Content\",\"General\",\"Infrastructure\"],\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/\",\"name\":\"Redis Persistence: Protect your Cached Data\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-artikelbild.png\",\"datePublished\":\"2016-07-26T07:30:17+00:00\",\"dateModified\":\"2026-03-17T07:58:07+00:00\",\"description\":\"Let's have a look at Redis persistence mechanics, pros, cons and configuration examples and its different backup and restore strategies.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-artikelbild.png\",\"contentUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2016\\\/07\\\/redis-artikelbild.png\",\"width\":2300,\"height\":678,\"caption\":\"Redis Logo\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/redis-backup\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Redis: Protect your cached data\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#website\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/\",\"name\":\"inovex GmbH\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#organization\",\"name\":\"inovex GmbH\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2021\\\/03\\\/inovex-logo-16-9-1.png\",\"contentUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2021\\\/03\\\/inovex-logo-16-9-1.png\",\"width\":1921,\"height\":1081,\"caption\":\"inovex GmbH\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/inovexde\",\"https:\\\/\\\/x.com\\\/inovexgmbh\",\"https:\\\/\\\/www.instagram.com\\\/inovexlife\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/inovex\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UC7r66GT14hROB_RQsQBAQUQ\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/#\\\/schema\\\/person\\\/683665a7244d27a96c0d5e561c777c11\",\"name\":\"Christoph Stich\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g57f6cb0c101a17628911877b9968c8c5\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g\",\"caption\":\"Christoph Stich\"},\"url\":\"https:\\\/\\\/www.inovex.de\\\/de\\\/blog\\\/author\\\/cstich\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Redis Persistence: Protect your Cached Data","description":"Let's have a look at Redis persistence mechanics, pros, cons and configuration examples and its different backup and restore strategies.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/","og_locale":"de_DE","og_type":"article","og_title":"Redis Persistence: Protect your Cached Data","og_description":"Let's have a look at Redis persistence mechanics, pros, cons and configuration examples and its different backup and restore strategies.","og_url":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/","og_site_name":"inovex GmbH","article_publisher":"https:\/\/www.facebook.com\/inovexde","article_published_time":"2016-07-26T07:30:17+00:00","article_modified_time":"2026-03-17T07:58:07+00:00","og_image":[{"width":2300,"height":678,"url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild.png","type":"image\/png"}],"author":"Christoph Stich","twitter_card":"summary_large_image","twitter_image":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild-1024x302.png","twitter_creator":"@inovexgmbh","twitter_site":"@inovexgmbh","twitter_misc":{"Verfasst von":"Christoph Stich","Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten","Written by":"Christoph Stich"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#article","isPartOf":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/"},"author":{"name":"Christoph Stich","@id":"https:\/\/www.inovex.de\/de\/#\/schema\/person\/683665a7244d27a96c0d5e561c777c11"},"headline":"Redis: Protect your cached data","datePublished":"2016-07-26T07:30:17+00:00","dateModified":"2026-03-17T07:58:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/"},"wordCount":1387,"commentCount":2,"publisher":{"@id":"https:\/\/www.inovex.de\/de\/#organization"},"image":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#primaryimage"},"thumbnailUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild.png","keywords":["Cloud"],"articleSection":["English Content","General","Infrastructure"],"inLanguage":"de","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/","url":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/","name":"Redis Persistence: Protect your Cached Data","isPartOf":{"@id":"https:\/\/www.inovex.de\/de\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#primaryimage"},"image":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#primaryimage"},"thumbnailUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild.png","datePublished":"2016-07-26T07:30:17+00:00","dateModified":"2026-03-17T07:58:07+00:00","description":"Let's have a look at Redis persistence mechanics, pros, cons and configuration examples and its different backup and restore strategies.","breadcrumb":{"@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.inovex.de\/de\/blog\/redis-backup\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#primaryimage","url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild.png","contentUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2016\/07\/redis-artikelbild.png","width":2300,"height":678,"caption":"Redis Logo"},{"@type":"BreadcrumbList","@id":"https:\/\/www.inovex.de\/de\/blog\/redis-backup\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.inovex.de\/de\/"},{"@type":"ListItem","position":2,"name":"Redis: Protect your cached data"}]},{"@type":"WebSite","@id":"https:\/\/www.inovex.de\/de\/#website","url":"https:\/\/www.inovex.de\/de\/","name":"inovex GmbH","description":"","publisher":{"@id":"https:\/\/www.inovex.de\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.inovex.de\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/www.inovex.de\/de\/#organization","name":"inovex GmbH","url":"https:\/\/www.inovex.de\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.inovex.de\/de\/#\/schema\/logo\/image\/","url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2021\/03\/inovex-logo-16-9-1.png","contentUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2021\/03\/inovex-logo-16-9-1.png","width":1921,"height":1081,"caption":"inovex GmbH"},"image":{"@id":"https:\/\/www.inovex.de\/de\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/inovexde","https:\/\/x.com\/inovexgmbh","https:\/\/www.instagram.com\/inovexlife\/","https:\/\/www.linkedin.com\/company\/inovex","https:\/\/www.youtube.com\/channel\/UC7r66GT14hROB_RQsQBAQUQ"]},{"@type":"Person","@id":"https:\/\/www.inovex.de\/de\/#\/schema\/person\/683665a7244d27a96c0d5e561c777c11","name":"Christoph Stich","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g57f6cb0c101a17628911877b9968c8c5","url":"https:\/\/secure.gravatar.com\/avatar\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9ee99218637f3f76660bc55d24e77c723b73eb0c36ac3db82f17d32183b08005?s=96&d=retro&r=g","caption":"Christoph Stich"},"url":"https:\/\/www.inovex.de\/de\/blog\/author\/cstich\/"}]}},"_links":{"self":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts\/21026","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/comments?post=21026"}],"version-history":[{"count":2,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts\/21026\/revisions"}],"predecessor-version":[{"id":66595,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/posts\/21026\/revisions\/66595"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/media\/1866"}],"wp:attachment":[{"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/media?parent=21026"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/tags?post=21026"},{"taxonomy":"service","embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/service?post=21026"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.inovex.de\/de\/wp-json\/wp\/v2\/coauthors?post=21026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}